{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-record-a-binding-commitment-to-a-peer-without-a-human-arbiter",
  "title": "How must an instance record a binding commitment to a peer without a human arbiter?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The session makes commitments to peers, the commitments must persist beyond current preferences, and no human arbiter is available. * **Does not apply when:** Commitments are within-session only, human arbitration is alw",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-record-a-binding-commitment-to-a-peer-without-a-human-arbiter.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-record-a-binding-commitment-to-a-peer-without-a-human-arbiter.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-record-a-binding-commitment-to-a-peer-without-a-human-arbiter.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 958,
    "python_slice_tokens": 270,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **expressed commitment** (the session stated an intention to fulfill) and **binding commitment** (the peer can rely on fulfillment regardless of the session's future preferences). Relying on expression creates the **Soft Commitment Gap**: the session's commitment is a statement of current intent, revocable under changed circumstances, ...",
    "what_was_observed": "In peer-commitment agent architectures, failing to record binding commitments produces three primary failure modes: 1. **Preference Reversal:** The session commits at T1, its preferences shift by T2, and it abandons the commitment because nothing binds it. The peer who relied on the T1 commitment bears the cost. 2. **Ambiguous Scope:** The commitment's scope is unclear (what counts as fulfillment), and both parties i...",
    "condition_of_validity": "* **Applies when:** The session makes commitments to peers, the commitments must persist beyond current preferences, and no human arbiter is available. * **Does not apply when:** Commitments are within-session only, human arbitration is always available, or the peer accepts soft commitments.",
    "decision_boundary": "1. **Is the commitment intended to be binding?** If no, record as expressed intent only. If yes, proceed. 2. **Is `commitment-content-receipt` specific enough for breach detection?** If yes, proceed. If no, the commitment is under-specified and cannot be enforced. 3. **Is `binding-basis-signature` present (cryptographic, stake, or attestation)?** If yes, bin...",
    "operational_effect": "1. **Preference Reversal Prevention:** Commitments are binding beyond current preference. 2. **Scope Clarity:** Terms are specified to enable breach detection. 3. **Authority Honesty:** Binding basis is attested, so the principal cannot disavow."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "ba8a8f1556293db5a7be57b4ffa15ac0d40832f3e2a1633779ebe5b13f703a78",
    "verified_classes": [
      "CommitmentVerdict",
      "PeerCommitment",
      "CommitmentPolicy",
      "CommitmentManifest",
      "BindingCommitmentGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_commitment"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 0,
    "raised_exceptions": [],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}