Checked against the specification, not against this implementation
…
Every check below names the section of SPEC.md it enforces, because a conformance failure should send you to the paragraph rather than to the source.
Point it at your own origin
Your origin is embedded here and asked what it can commit to. Nothing
is written down, nothing is sent anywhere, and no step of any protocol is executed — the suite
only reads declarations and asks a participant to describe itself. It has to be able to see
them: a participant that names one origin in exposedTo, which is what every
participant in this repository does, is invisible to every other origin including this one.
Add this origin to yours while you test.
What the levels mean
- L1 · declares
- A
concord.protocoltool, exposed to embedders, honest about which rung it is on. - L2 · recoverable
- Plus
concord.status, so an interrupted commitment can be resolved instead of guessed at, and steps that are safe to retry. - L3 · attesting
- Plus statements signed with a key published on its own origin, so a receipt can be checked by someone who trusts neither party.