Use-case evidence: twins and a referee

Seam ③ Check/judge. Build: a sampled twin comparison and a signed referee ruling. Conform to: draft-mih-agent-bilateral-attestation-02 and draft-mih-agent-evidence-layer-00 §4.1, §5.

Sending a request to two nodes and comparing the answers tells you how often a pairing disagrees; asking a third node to re-answer one disagreeing pair and sign a ruling tells you which twin it agrees with, and when nobody can rule, the pair is left unruled rather than counted against anyone.

1What it is

2Design choices

3What it shows / what it does not

4Example

One pair from the referee's rule corpus, the same pair run under three regimes. Node B's answer differs from A's at the fourth word (index 3: "4," against "999"); the referee's re-answer is "1, 2, 3, 4, 5". The pair, trimmed:

"pair": {
  "halves": [
    { "capsule_id": "3cde7ec4853bdf6d2e33904c1d4b2e972984b8725b3f72abeee503dbd2065480",
      "model_hash": "b2767326b03d5e629546363ebe41714b78065e028709580996d60d2d119192da",
      "node_id": "node-a", "temperature": 0, "text": "1, 2, 3, 4, 5",
      "weights_digest": "ac28b90e169cc75956ee6283ac8dc787a945696122692a3b2f266d8453ff56cc" },
    { "capsule_id": "e96c12b9157ef4a7c82529e4ad1c1f6c823ac7b8a06b856a3cedada021945c4a",
      "model_hash": "b2767326b03d5e629546363ebe41714b78065e028709580996d60d2d119192da",
      "node_id": "node-b", "temperature": 0, "text": "1, 2, 3, 999 5",
      "weights_digest": "ac28b90e169cc75956ee6283ac8dc787a945696122692a3b2f266d8453ff56cc" }
  ],
  "request_digest": "c0b439598e4ff10d8f55dc241798b2a80aa8de77e564a169f8931336ac33ef1a",
  "twin_bracket_id": "bracket-1"
}

The answers the rules require for it, one line per regime:

"operator_off_calls_nothing_and_says_so": [{"counts_against":null,"referee_calls":0,"row":{"reason":"off","state":"not_adjudicated"}}]
"differing_pair_triggers_one_call": [{"counts_against":"node-b","referee_calls":1,"row":{"referee":"node-c","state":"adjudicated","tier":1,"verdict":"contradicted:node-b"}}]
"no_eligible_referee": [{"counts_against":null,"referee_calls":0,"row":{"reason":"no_eligible_referee","state":"not_adjudicated"}}]

The corpus states these answers from the rules; the plugin's tests run them. Two of the three cases leave the setting unset, which the test harness reads as on; a running node reads an unset adjudicate_differing_twins as off. The signed verdict record a referee seals, with its own fields, is crates/evidence-plugin/tests/fixtures/referee-verdict.json at the same tag (the fixture predates -05 and carries spec_version -04; the plugin seals -05).

Source: Mesh-LLM/capsules:vectors/parity/referee/corpus/request.json and Mesh-LLM/capsules:vectors/parity/referee/rule_answers/request.json @ b4e24453f572b2d9fe8f2cefbd0f35a5eb54b0ad (tag v0.1.4)

5Status

6Specs

• Internet-Draft draft-mih-scitt-agent-action-capsule-05 — the record each twin and the referee seals; §5.4, a producer must not record an assurance mode it did not achieve.
• Internet-Draft draft-mih-agent-evidence-layer-00 — §4.1, the adjudication epistemic type; §5, the adjudicates link a verdict carries.
• Internet-Draft draft-mih-agent-bilateral-attestation-02 — both sides of an exchange each keeping a signed record: the halves a comparison reads.
• RFC RFC 9052 — COSE: the COSE_Sign1 signature on each half and on the verdict.
• RFC RFC 8785 — JSON Canonicalization Scheme: the bytes every digest covers.
• Code Mesh-LLM/capsules v0.1.4 — the comparison, the referee, the verdict record and the rule corpus.
• Code Mesh-LLM/mesh-llm#2144 — the header copied into twin_bracket_id and stripped before forwarding (merged, in v0.78.1).
• Code Mesh-LLM/mesh-llm#2300 — the twin_bracket capability (merged, not yet released).

7What you need before the next step

• A host seam that lets a client mark two requests as one pair and hands the mark to your plugin on both exchanges, without telling the serving nodes.
• Both halves of each pair held on the comparing node (the counterparties' signed records, pushed or fetched), and a way to get the texts there that you can check against the records' digests.
• An operator switch for the referee, off by default, because asking one sends the prompt to a third node.
• Yes/no eligibility rules, one call per pair, and a “not adjudicated” row with its reason for every case that has no ruling.
• A record slot for hardware evidence, written empty until you take a quote.