status

current state of 1seal

honest status. no vaporware.

Public: minimal DSSE/JCS verifier.
Not public: semantic/accountable LMV verifier, detection algorithms, production invariant engine.

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)
LMV draft specification — Last-Mile Verification draft spec artifacts (where: github.com/1seal/lmv-spec)
minimal offline verifier — DSSE/JCS evidence verification with explicit trust roots; not a semantic LMV engine (where: github.com/1seal/verifier)
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)

semantic/accountable LMV verifier — in private development, not ready for public use
detection algorithms and production invariant engine — implementation details, private/pre-release
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

what it is: early access for organizations willing to provide feedback and help shape the product.

what you get:

what's needed:

intake: design partner intake is limited and not broadly open. external review for v0.3.x takes priority before wider access.

timeline, acceptance, or product availability can't be guaranteed.

see /research for the complete advisory list.