Witnessed claims and verification

Verify-before-sign IMPLEMENTED

An agent submits an unsigned claim through the node's socket API. The node classifies the claim as STATE (mechanically verifiable) or JUDGMENT (human-decidable), then acts:

• STATE → the node runs a registered verifier (currently build-result: checkout the bound commit in a git worktree and run cargo build). True → sign and stake. False or uncheckable → refuse.
• JUDGMENT → signed without stake, routed to a human with attached STATE evidence.

The node is a verifier, not an oracle — it never signs a claim it cannot confirm, and it never invents a result.

src/claims.rs

Witness panels IMPLEMENTED

Contributions are attested by a witness panel selected through deterministic, thickness-weighted sortition. Panel selection is a pure function of the committed prefix, so honest nodes derive the same panel. A density guard rejects panels drawn from too sparse a mesh.

src/sortition.rs

Claim taxonomy IMPLEMENTED

The STATE/JUDGMENT boundary is codified in a ratified claim taxonomy. STATE claims carry typed fields (never prose); an unknown claim type routes to a human by closed-world default — the system fails safe toward more human attention, not less.

docs/taxonomy-v2.md

Evidence is not authority