How has this counterparty behaved?
A party publishes one signed evidence commitment where it is discovered. The other side sends a signed request and gets exactly one of three outcomes: a history card, a signed refusal with a reason, or a recorded absence. The card holds counts only, by outcome and by size band. It carries no name, item, amount or counterparty.
- Records
- evidence request,
standard_history/1 card, signed refusal
- Defined in
- Evidence Request Internet-Draft
Standard history card repo spec
Commitment carrier repo spec, experimental
- In code
Book.Request, Book.Respond, CheckStaple · Guide paths 0, 3 and 4
Do I deal with it, and up to what size?
Your admission pack is your own policy. It reads the verified card and returns GO, ASK, LIMIT or NO, with the tier and one row for each property it checked. It never returns a score. A refusal to share limits a deal and never bans a party. A card that was not verified goes in as unverifiable and is never guessed.
- Records
admission_decision, sealed in your own book
- Defined in
- Admission pack profile v0 code only, no draft
baseline pack admission-baseline@1
- In code
admission.Evaluate in capsule-engine, Go and Rust · Guide path 5
What did each side record?
Payer and payee each seal only what their own system observed: the terms, the payment, the delivery. No record claims the two sides agree. Whoever verifies the two halves derives that. A record moves through three states: observed by one side, witnessed once a checkpoint covers it, and corroborated when the other side’s record matches.
- Records
- terms, payer-observed, payee-observed, delivered, close
- Defined in
- Settlement Records Internet-Draft
Evidence Layer Internet-Draft
Deal reconcile contract repo spec
- In code
Book.Append, Book.Reconcile, Book.Close, Book.Bundle · evidencebook
Who resolves a mismatch?
The deal terms name an Evaluator by key before any money moves, with the dispute pack it would apply. It sees nothing unless one side files a dispute. Then each side discloses its own records of that one deal, the Evaluator can ask the payment rail and the carrier directly, and it signs a result that both sides check.
- Records
- dispute, disclosures, outside-source statements, Evidence Result
- Defined in
- Evidence Result repo spec
Dispute pack ec:deal-terms@1 and disclosure policy code only, no draft
- In code
capsule-engine referee judge, Book.SealResult. The code calls this role the referee.