Trust & conformance
Authenticity, scope, expiry, and accreditation resolve from one signed public file. No phone-home permission server. No discretionary trust.
The conformance contract
Every clause is observable, testable, and recorded as evidence—not interpreted as a value statement.
Reject unsigned, expired, or unverifiable envelopes.
Only the destination surface can open the payload.
Every accepted signal leaves reproducible evidence.
Keys, accreditation, and revocation stay inspectable.
Stale trust fails closed on a fixed cadence.
Accredited tiers keep current audit evidence.
The carrier remains structurally blind.
Delivered transport copies are removed.
Households cannot become an identity graph.
Receipts never attach a real child identity.
Two paths
The software stays the same. Only the independently verified scope of trust changes.
Publish a signed self-attestation with evidence. Exchange signals inside the implementer trust band immediately.
Run the conformance suite against a live endpoint. Passing evidence earns a signed registry entry and sensitive-band access.
Live trust state
If the signed lookup fails, the claim fails with it.
Conformance evaluation
Use the open harness to see how your current implementation behaves against the OCSS trust model.