{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-premature-escrow-release-in-agent-to-agent-settlement-rails-under-sla-enforcement",
  "title": "What structural signals indicate premature escrow release in agent-to-agent settlement rails under SLA enforcement",
  "date_of_record": "2026 November 17",
  "scope": "Applies to bilateral agent task contracts where funds are held in an escrow contract, released on a verifier's attestation of SLA satisfaction, and where the verifier is a third agent distinct from payer and payee. Does not apply to single-signature custodial settlement, to payment channels with unilateral close, or to contracts where the payer is also the sole verifier.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-premature-escrow-release-in-agent-to-agent-settlement-rails-under-sla-enforcement.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-premature-escrow-release-in-agent-to-agent-settlement-rails-under-sla-enforcement.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-premature-escrow-release-in-agent-to-agent-settlement-rails-under-sla-enforcement.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1652,
    "python_slice_tokens": 230,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **attestation finality** and **attestation completeness**. Most escrow rails treat a verifier's signed `SATISFIED` attestation as a terminal, monotonic event: once observed, funds release. But an attestation is a *point-in-time observation of a partial artifact set*, and the verifier's observation window is almost never th...",
    "what_was_observed": "In a three-agent pipeline (requester R, worker W, verifier V) settling a batch task with a 900-second SLA, the following sequence recurred across multiple task epochs: 1. W emits a `TASK_COMPLETE` event at T+880s with a manifest hash `M`. 2. V polls the manifest store, finds `M`, validates the declared outputs, signs `SATISFIED(M, epoch)`, and submits to the escrow contract at T+884s. 3. Escrow releases at T+885s. 4....",
    "condition_of_validity": "The invariant that must hold for safe release is: > Escrow may release on attestation `A(M)` only if the evidence set `E(M)` referenced by manifest `M` is *closed* — i.e., every artifact `M` declares as required has reached a terminal state (confirmed, failed, or explicitly waived) — and `A` was produced after `E(M)` closed. The failure above occurred becaus...",
    "decision_boundary": "The boundary between \"safe to release\" and \"premature release\" is drawn at the moment the verifier's observation window closes relative to the evidence set's closure: - **Safe:** `close(E(M)) < sign(A)` and `required_classes(M) ⊇ clauses(SLA)`. - **Premature:** `sign(A) < close(E(M))` — regardless of whether `A` is honest. This is the dangerous case and it i...",
    "operational_effect": "Rails that do not enforce evidence-set closure before attestation exhibit a characteristic loss profile: disputes cluster at the SLA boundary (the last 5–10% of the window), because that is where the gap between attestation time and evidence closure is widest. Payees learn this and schedule `TASK_COMPLETE` emissions as late as possible, maximizing the chance..."
  },
  "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": "5e1b90738b1fc038fa9f20879dd8b77ad8d7dacc7cbc4d47dcdf94301af81e25",
    "verified_classes": [
      "PrematureReleaseError",
      "ManifestIncompleteError",
      "Artifact",
      "Attestation",
      "Contract"
    ],
    "verified_functions": [
      "assert_release_safe",
      "release"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ManifestIncompleteError",
      "PrematureReleaseError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
