status
current state of 1seal
honest status. no vaporware.
1seal is in private development with selected design partners. not yet available as a generally available product.
what's public
- thesis and positioning — the semantic gap, trust stack position, design principles (where: this website)
- operational protocols — Degraded Mode Policy, Appeal and Resolution, Invariant Lifecycle, Error Cost Framework (where: github.com/1seal/lmv-spec/docs/protocols)
- canonical spec — Last-Mile Verification (LMV) spec artifacts (where: github.com/1seal/lmv-spec)
- published advisories — CVEs in trust infrastructure with credit attribution (where: github.com/1seal/.github#published-advisories)
- threat model and non-goals — explicit scope boundaries (where: THREAT_MODEL.md and NON_GOALS.md)
what's not public
- implementation code — in development, not ready for public use
- detection algorithms — implementation details, may change
- timelines or roadmap — no promises that can't be kept
- customer or partner names — confidential unless they choose to share
- unpublished security research — coordinated vulnerability disclosure
design partner program
what it is: early access for organizations willing to provide feedback and help shape the product.
what you get:
- early access to implementation
- direct feedback channel
- input on protocol evolution
what's needed:
- real-world deployment context
- feedback on false positives and edge cases
- patience with rough edges
how to apply: email hello@1seal.org with your context.
timeline or acceptance can't be guaranteed.
recent updates
- 2026-02-02: GHSA-gx3x-vq4p-mhhv published (cert-manager)
- 2026-02-01: website published with thesis, protocols, and published advisories
- 2026-01-29: CVE-2026-24846, CVE-2026-24845 published (malcontent)
- 2026-01-22: CVE-2026-24137, CVE-2026-24117, CVE-2026-23831 published (sigstore)
see /research for the complete advisory list.
contact
- general: hello@1seal.org
- security: security@1seal.org
- design partner interest: design partner program