Implementation status
This page separates preview, candidate, private preview and sandbox surfaces from what must not be inferred. The labels describe release readiness, not capability: something can work today and still be labelled candidate because it is not published. Where our written materials mark a capability as implemented, that is the claim about what it does; the label here is the claim about how you can get it.
Loquitur is a verifiable-record protocol for evidence about real-world and financial assets. Production registry availability, live chain anchoring, stable SDK/API status, public package availability, external audit, SOC 2, SLA, valuation correctness and compliance approval each remain outside the current scope.
Surface ledger
Protocol preview for private evidence bundles, verification receipts, reason-coded policy outcomes, lineage and minimal registry commitments.
Not a tokenization platform, valuation engine, generic oracle, compliance/KYC substitute or production registry.
Candidate schema surfaces for bundle, receipt, summary, registry-entry and trust-registry shapes.
Not an externally ratified standard or stable public contract.
Verifies a bundle offline through four levels: structure (L0), file and manifest integrity (L1), the cryptographic link between a bundle and its registry entry (L2), and issuer authorization against a trust registry (L3), which distinguishes revoked, suspended, expired, not-yet-effective and out-of-scope keys.
No registry inclusion proof (L4) and no anchor finality (L5). The trust-registry root signature is computed and reported; what is missing is a pinned production root, so by default an unpinned root is refused rather than assumed valid. A root obtained out of band can be supplied at verification time.
An executed gate runs 36 adversarial vectors through 4 verifiers, and 7 bundles through the Python and TypeScript implementations, and fails on any disagreement. It currently reports none.
The corpus is our own and has not been externally ratified. Agreement between two implementations is evidence that the specification is unambiguous, not that it is correct.
Reviewable implementation-preview artifact for API-first discussion and internal contract alignment.
Not a hosted production API, stable public API or SLA-backed endpoint.
Private preview wrapper and generation proof used for integration narrative and future hardening.
No published stable npm package or partner-ready public SDK claim.
Public-readonly sandbox for minimal commitment projections.
No production public registry, live chain anchoring, public raw evidence or public valuation data.
Release gates
Candidate surfaces can be reviewed as contract material.
Public package release discipline, compatibility gates and generated documentation must close before standard-like language.
L0 to L3 are implemented and tested. The cross-implementation gate compares the two implementations on structure and integrity (L0, L1) and on schema contract agreement; it does not yet exercise the link (L2) or authorization (L3) checks, because its bundle cases carry no registry entry and no trust registry.
Inclusion proof (L4) and anchor finality (L5) require a running transparency log and a live anchor before either can be claimed. Trust-root verification requires a pinned production root; today none is pinned and verification refuses rather than passes.
The offline verifier, the schema package and the conformance corpus are what support technical review: a reviewer runs them, rather than being shown ours.
Stable public API/SDK language requires package publishing posture, auth clarity, compatibility checks and partner-handoff docs.
Sandbox commitment projection is public-readonly.
Production registry, operator trust, live anchoring and finality claims require dedicated runtime and assurance gates.
Not inferred
No production registry claim.
No live chain anchoring or finality proof claim.
No stable public API or SDK claim.
No audit, SOC 2, SLA, ISO certification or bug bounty claim.
No valuation correctness, investment approval or compliance approval claim.
No partnership, customer or endorsement claim.