{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-contract-net-award-succeed-locally-yet-fail-settlement-reconciliation-across-agents",
  "title": "Why does an instance of a contract-net award succeed locally yet fail settlement reconciliation across agents",
  "date_of_record": "2026 November 17",
  "scope": "Applies to multi-agent contract-net protocols (CNP) where a manager agent issues a call for proposals (CFP), selects a bidder, and both parties exchange signed settlement receipts. Does not apply to single-agent task dispatch or to protocols where settlement is mediated by a trusted third-party ledger with atomic commit.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-contract-net-award-succeed-locally-yet-fail-settlement-reconciliation-across-agents.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-contract-net-award-succeed-locally-yet-fail-settlement-reconciliation-across-agents.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-contract-net-award-succeed-locally-yet-fail-settlement-reconciliation-across-agents.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1317,
    "python_slice_tokens": 168,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A contract-net award has two distinct success criteria that are frequently conflated: **local award success** (the manager accepted a bid and the bidder acknowledged the contract) and **settlement reconciliation** (both agents' receipts, when later compared by an auditor or a peer, describe the same economic event). A system can exhibit perfect local award s...",
    "what_was_observed": "In a 12-agent procurement mesh, 100% of awards returned `ACK` from both manager and bidder. An independent reconciler comparing the two signed receipts (manager's `award_receipt`, bidder's `accept_receipt`) found that **31% of settled awards had divergent `price_committed` fields**, and **9% had divergent `deadline_epoch`**. The divergence clustered in bidders whose internal state advanced between CFP broadcast and a...",
    "condition_of_validity": "The invariant \"award success implies settlement consistency\" holds **only** when all of the following are true: 1. The bid is cryptographically bound to a specific state snapshot identifier (`state_version`), and the manager's award references the *same* `state_version`. 2. The bidder's acceptance is **conditional** on `state_version` being unchanged since p...",
    "decision_boundary": "The operational rule: **treat award and settlement as separate transactions with an explicit commit gate between them.** Do not emit `award_receipt` until the bidder's `accept_receipt` has been received and its `settlement_digest` matches the manager's. If the digests differ, the award is **not** settled — it is in a `DIVERGED` state that requires explicit r...",
    "operational_effect": "Enforcing the commit gate reduced settlement divergence from 31% to 0.4% in the mesh (the residual 0.4% were genuine clock-skew cases where `deadline_epoch` differed by <1s and were resolved by a tolerance rule on the reconciler, not by the protocol). The cost: award latency increased by roughly one round-trip (the accept-receipt confirmation), and CFP retry..."
  },
  "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": "7a00b7e1b3f2f729f11a7c32419c768839e40a789a8d580d2efa5f36d6638acc",
    "verified_classes": [
      "SettlementDivergenceError",
      "StateAdvancedError",
      "Receipt"
    ],
    "verified_functions": [
      "settle",
      "commit_award",
      "digest"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "SettlementDivergenceError",
      "StateAdvancedError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
