{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-double-settlement-in-contract-net-bidding-with-verifiable-outcome-attestations",
  "title": "Which invariants prevent double-settlement in contract-net bidding with verifiable outcome attestations",
  "date_of_record": "2026 November 17",
  "scope": "Applies to multi-agent contract-net (CNP) procurement where a manager agent issues a call for proposals (CFP), bidders respond, an award is issued, and settlement is released only against an outcome attestation signed by a verifier. Does not apply to single-manager, single-bidder pipelines where no competing attestations can exist, nor to off-chain settlement without an independently verifiable attestation root.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-double-settlement-in-contract-net-bidding-with-verifiable-outcome-attestations.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-double-settlement-in-contract-net-bidding-with-verifiable-outcome-attestations.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-double-settlement-in-contract-net-bidding-with-verifiable-outcome-attestations.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1409,
    "python_slice_tokens": 145,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **award finality** and **attestation finality**. In a contract net, the manager's award message is treated by bidders as the terminal state of the negotiation. But settlement is gated on a *later* event — the verifier's attestation — which is produced by a party that never saw the award. If the manager crashes between awar...",
    "what_was_observed": "In a 14-agent procurement mesh (3 managers, 8 bidders, 3 verifiers), a manager process was killed at the point between writing the award to its local WAL and broadcasting the award to the ledger. On restart it replayed the CFP. A second manager, which had observed the task in `open` state after a lease expiry, independently issued a CFP for the same task. Two bidders won, each against a distinct nonce. Both produced ...",
    "condition_of_validity": "The following invariant set is sufficient and each clause is necessary: 1. **Award nonce binding.** Every award carries a manager-generated nonce, and the CFP that produced it is bound to the same nonce. An attestation is valid for settlement only if it embeds the award nonce and the verifier signs `(task_id, award_nonce, outcome_hash)`. 2. **Lease-gated CFP...",
    "decision_boundary": "When a settlement request arrives, the ledger must decide: settle, reject, or hold. The boundary is: - **Settle** iff the attestation verifies, its nonce matches a known award, the award's lease epoch is the current epoch for that task, and no prior settlement exists for `(task_id, award_nonce)`. - **Hold** iff the attestation verifies and matches a known aw...",
    "operational_effect": "Encoding the invariant at the ledger changes the failure mode from *silent double-settlement* to *explicit nonce conflict*, which is observable and recoverable. In the observed mesh, after moving uniqueness to `(task_id, award_nonce)` and adding the lease-epoch check, the same crash-and-restart scenario produced a rejected second settlement with a `StaleAwar..."
  },
  "matched_failure_symptoms": [
    "DST_SHIFT_OR_CLOCK_SKEW"
  ],
  "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": "17e2b7b31bed656af5fc6f7d8db23e9b730de4a6f2ebfc9d568cb490e66d6af1",
    "verified_classes": [
      "SettlementInvariantError"
    ],
    "verified_functions": [
      "settle"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "SettlementInvariantError"
    ],
    "sample_fail_closed_invariants": [
      "attestation signature invalid"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
