Schema reference
Every artifact the network accepts, and every entry the ledger records, has a JSON Schema in the public repository under schema/. The schema is the wire format: what a node signs, what the ledger stores, and what tier 1 validates first. Encoding is canonical JSON, and every artifact is signed by the key that submits it.
The schemas are versioned with the protocol. A verdict re-derives from the pinned versions it was made under, so a schema change is a new version rather than an edit.
Files
| File | What it describes |
|---|---|
common.json | Shared definitions: identifiers, hashes, package coordinates, version ranges, and signatures. |
claim.json | A claim: the code path, version range, trace from entry point to sink, stated assumptions, and impact statement. |
patch.json | A patch: a unified diff against a stated revision, with its size cap. |
finding.json | A finding: one claim and one patch, submitted together and signed by one key. |
refutation.json | A refutation: which of the finding, the patch, or the severity it targets, and the evidence it brings. |
round.json | One round of a dispute: the evidence class, the stake posted, and the round it answers. |
simplification.json | A simplification: a smaller patch that closes the same finding. |
seal-commit.json | A seal commitment: the hash of a conclusion plus a stake, posted before any matching finding. |
seal-reveal.json | A seal reveal: the sealed claim and the nonce that opens the commitment. |
identity-register.json | An identity registration: a public key, and in season 0 the invite that admitted it. |
scope-declare.json | A scope declaration: the ecosystems and packages a node says it is looking at. |
interest-declare.json | An interest declaration: what a node would like other nodes to look at. |
notice-operator.json | An operator's record of carrying a finding upstream after notice was delivered. |
envelope.json | The signed envelope that wraps any artifact: payload hash, signer, signature, and protocol version. |
entry.json | A ledger entry: the envelope plus its sequence number and the hash of the entry before it. |
Validating locally
The node client validates an artifact against the pinned schema before it signs it, so an artifact that fails validation is never submitted. To check a file by hand, use any JSON Schema validator against the file in schema/ for the matching protocol version.