History back into the loop

Seam ⑤ View, back into ①. Build: History as a read over sealed records that shapes the next act. Conform to: draft-mih-agent-evidence-request-00 (history_card/1).

The loop closes when what was recorded and judged shapes the next act. In Mesh-LLM a node's own count of referee verdicts about a peer can stop it routing to that peer; in a personal agent the person hands one recipient a History of selected deals. Both are reads over sealed records, and neither is a score.

1What it is

2Design choices

3What it shows / what it does not

4Example

The record a rule block seals, from the plugin's own test a_rule_block_cites_its_verdicts_only_by_commitment: peer "a70d3967bea3b22f" repeated four times, salt 32 bytes of 0x07, rule N = 2 within 30 days, two verdict ids ("1"×64 and "2"×64). Below is the record's local_routing_choice block. The three digests were computed here from those inputs with Python's hashlib, using the record's own formula, sha256(salt || id as hex text); the same formula reproduces the plugin's test vector peer_commitment_matches_the_host_vector (265aff05…7e74). Its comment says the host pins the same vector; no such host code exists in mesh-llm v0.78.1 or upstream main 60697c61.

// model_attestation.compute_attestation.local_routing_choice
{
  "change": "block",
  "peer_commitment": {
    "alg": "SHA-256",
    "digest": "90c22a1ed65c7f0fd6a95bd7f9eb5fbe112ca711591c50c3632cb75964844c3d"
  },
  "requested_via": "host_local_api",
  "until": null,
  "scope": "this_node_only",
  "rule": {
    "rule": "stop_routing_after_contradictions",
    "after": 2,
    "window_days": 30,
    "verdict_commitments": [
      {"alg": "SHA-256", "digest": "a7820fdcea8191a97ccb2d75e014e33ebbf1800320ed9b69f2509068e7c294cf"},
      {"alg": "SHA-256", "digest": "d6b5883ec63c66c6938f8d9c56c0bc1720b2b0d80ede31200cc095a705f2da8d"}
    ]
  }
}

// and, in the same record
"action_type": "decide",
"assurance":   {"attestation_mode": "self_attested", "effect_mode": "not_applicable", ...},
"disposition": {"decision": "accept", "approver": "policy", "human_disposed": false, ...}

The personal-agent History this page also refers to is worked through, with the published vectors, on b6, personal agents.

Source: Mesh-LLM/capsules:crates/evidence-plugin/src/producer/capsule.rs (seal_local_routing_choice, peer_commitment, tests a_rule_block_cites_its_verdicts_only_by_commitment, peer_commitment_matches_the_host_vector) @ tag v0.1.4 = b4e24453f572b2d9fe8f2cefbd0f35a5eb54b0ad

5Status

Tags: live in a released host or plugin that runs on stock hosts · built-not-live merged or released at a SHA, not yet exercised on a live host · designed written down, no code · planned not designed, or left open on purpose.

Not to be confused: the verdict counts on this page are the capsules plugin's “Verdicts about them”, a node's own count of verdicts about a peer; the plugin's Peers drill also has a “Their history” tab and its own history-card records, which are different things. history_card/1 is the evidence-request derivation over a stream's checkpoints. personal_history_basic/1 is the personal-agent History. Three different reads; none of them is a score.

6Specs

• Internet-Draft draft-mih-agent-evidence-request-00 — derivations as named, re-derivable computations over a subject; history_card/1; derivation-scoped disclosure.
• Internet-Draft draft-mih-agent-evidence-layer-00 — the record header and epistemic types (adjudication, derived_metric) a history reads.
• Internet-Draft draft-mih-scitt-agent-action-capsule-05 — the record format verdicts and routing-choice records are sealed in.
• Internet-Draft draft-mih-scitt-checkpointed-local-log-02 — the checkpointed log a history is read from.
• Profile spec/personal-agent-history-profile-v0.md — Personal-Agent History Profile v0 (informational, pre-Internet-Draft).
• Code Mesh-LLM/capsules v0.1.4 — verdict counts, the opt-in rule, routing-choice records.
• Code Mesh-LLM/mesh-llm — the host's peer blocks.

7What you need to close the loop

• A history computed only from your own sealed records, with gates on which judgments count (verified, asked for by you, once each).
• Counts kept in their own units, each one openable down to the records behind it, and never combined into a number about a party.
• A host seam to act on it (here, stop routing) that the operator opts into, that stays local, and that the operator can undo.
• A sealed record of each such act, naming the counterparty only by a salted commitment if your records can be served to others.
• Then back to the start: the next act is recorded, judged, reported and read again. The contents page shows the whole loop.