document · §6 status · stated plainly
What is available today
Explore the public research record, draft LMV specification, protocols and evidence-verifier documentation. The semantic toolkit remains in private development; the public verifier repository contains documentation, not executable code.
1seal publishes security research and a draft model for checking a payload against declared intent before commitment. The semantic toolkit is in private development / pre-release; LMV is a draft, not a mature standard.
A PASS means only that the evaluated payload matched declared intent under configured invariants and available evidence. It does not establish safety, legality, compliance, legitimacy or general trustworthiness.
Current component status
On smaller screens, scroll the table horizontally to see all columns.
| Component | State | Boundary | Observed |
|---|---|---|---|
| LMV specification | public draft v0.1 | Public README version; no completed external review or mature standard status is asserted. | 2026-09-22 |
| Evidence verifier | public documentation; implementation not published there | The repository describes offline DSSE/JCS verification. Its public tree contains README, SECURITY, LICENSE and .gitignore, not executable verifier code. The site playground checks required fields only. | 2026-09-22 |
| Semantic LMV implementation | private / pre-release | No public release, independent validation or delivery date is asserted. | not recorded |
| Design partners | limited conversations; not broadly open | No acceptance, existing participation or onboarding date is promised. | not recorded |
| Services | by request; separate from product access | Scope and availability are agreed per engagement. | not recorded |
A state is what exists today, not a stage on a roadmap. An empty cell means not recorded — not "soon".
What is public and what is not
public · where
- Thesis and positioningthis site
- Operational protocolsDraft overview and individual source documents
- LMV draft specificationDraft README on GitHub
- Evidence-verifier documentationDSSE/JCS design on GitHub · implementation not published there
- Threat model and non-goalsThreat model · Non-goals · draft documents on GitHub
- Published findingsResearch record · portfolio.json
not public · why
- Semantic / accountable LMV verifierprivate development, not ready for public use
- Detection algorithms, invariant engineimplementation detail, pre-release
- Timelines or roadmapno promises that cannot be kept
- Partner participationnot asserted by this page
- Unpublished researchcoordinated disclosure in progress
Design-partner conversations
Limited conversations with organisations about deployment context, verification requirements and edge cases. This is not an offer of early product access. External review and validation remain prerequisites for wider claims.
Initial conversations explore fit. Participation and product access are agreed separately; no launch date is set.
Include your stack, the proposed verification point and the risk you want to address. Do not send secrets, private keys or sensitive production data. The first discussion establishes applicability and scope, not a promise of product access.
Opens your email app. If nothing opens, use Copy email or write to labs@1seal.org in your usual mail service.
Research snapshot
The dated research record links to public evidence. Its snapshot date is separate from product availability.