Certification is the moat, not the gate.
The public kit describes conformance at a named version. Commercial certificate issuance and audit-linked certification are not available in this beta. You can register interest; no payment is taken and no certification is promised.
Value Core
WOS-2 §§1–4- Integer minor units only — floating point amounts are rejected outright
- One uniform state machine across every rail
- Idempotent lock under a repeated idempotency key
- Wrong-asset refusal at lock time, never a silent conversion
- Double-release rejection
- Refund only by arbiter or expiry
- Deadline expiry triggerable permissionlessly, or refused at lock if the rail cannot express it
- Status consistency across queries
- Value conservation under randomised sequences
Agency
WOS-2 §5 and WOS-3- Funds lock from a registered principal, not an anonymous node
- Charter spending caps enforced at open
- Human-threshold co-signature hook present and enforced
- Refunds land on the principal, never on an intermediary
Cross-rail
WOS-2 §7- Two-phase commit coordinator interface
- Abort-bond accounting
- Bonded eventual convergence under partition
And, precisely, what it does not.
A certification records that an implementation reproduced the published vectors on a stated date, at a stated commit, under a stated attestation type. Self-attested and audit-linked certifications are displayed differently and are never conflated.
The implementer ran the public kit and signed the result. We record it. We did not witness it.
The same vectors, bound to an external audit report from a named firm. Displayed differently, and never conflated with self-attestation.
A rail that cannot express a state must refuse it, never approximate it. Those vectors are recorded as refusals — not as passes, and not as failures.
Our published self-attestation matrix includes a failed level. This is not independent certification. See the public matrix.