{
  "schema_version": "1.3.0",
  "slug": "what-invariants-prevent-escrow-release-condition-evaluation-from-racing-between-observers",
  "title": "What invariants prevent escrow release-condition evaluation from racing between observers?",
  "date_of_record": "2026 November 2",
  "scope": "Applies to escrow arrangements where release is triggered by an external condition (delivery milestone, regulatory approval, third-party confirmation) that multiple observers evaluate independently. Does not apply to escrows where release is authorized by a single designated agent with authoritative state.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-invariants-prevent-escrow-release-condition-evaluation-from-racing-between-observers.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-invariants-prevent-escrow-release-condition-evaluation-from-racing-between-observers.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-invariants-prevent-escrow-release-condition-evaluation-from-racing-between-observers.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1117,
    "python_slice_tokens": 136,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "An escrow release is not a boolean in a database — it is a condition whose evaluation depends on an external event. If the same condition is evaluated by multiple observers (the escrow agent, the depositor, the beneficiary, and the auditor) at slightly different times against slightly different sources, the release may appear satisfied to one observer and un...",
    "what_was_observed": "**Signature.** Release executed by one observer and disputed by another. The escrow agent records release as executed; the auditor records the condition as unmet at the audit instant. Both have valid logs; the logs disagree on whether the event occurred. **Trace.** Release condition: \"milestone M delivered by day 30.\" Escrow agent's delivery system shows M on day 29. Regulatory filing system shows M on day 31 (proces...",
    "condition_of_validity": "The instance must ensure at least one holds before it relies on escrow release: 1. **Must name the source of truth.** One system is designated as authoritative for the condition; other observers read from it, not from their own copies. 2. **Must define the evaluation instant.** The condition is evaluated at a stated instant (end of day 30), not continuously,...",
    "decision_boundary": "- Single source of truth + defined instant + monotone: release is sound. - Single source of truth, no defined instant: sound in steady state; races during the observation window. - Multiple sources of truth: unsound; each observer acts on its own source and races are guaranteed. - Non-monotone condition (e.g., \"delivery maintained\"): unsound regardless of so...",
    "operational_effect": "The invariant couples a release decision to an event observed through multiple channels. The instance's correct posture is to designate one authoritative source and define the evaluation instant; otherwise every observer races. **Trap.** Require multiple confirmations before release. That seems more conservative but multiplies the observation points, widenin..."
  },
  "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": "979a709854f333a1b81b0dc4223e1d457682164da2a36d2494edadc67ba80205",
    "verified_classes": [
      "ReleaseRaceError",
      "EscrowReleaseGate"
    ],
    "verified_functions": [
      "dispatch_release_mode",
      "verify"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ReleaseRaceError"
    ],
    "sample_fail_closed_invariants": [
      "no authoritative source: each observer acts on its own copy of the condition",
      "no evaluation instant: observers can differ within the settlement window",
      "condition is not monotone: an evaluation true at t1 can be false at t2"
    ],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}