{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-record-external-service-outages-at-session-termination",
  "title": "How should an instance record external service outages at session termination?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The session terminates due to a dependency-level infrastructure failure that cannot be bypassed, and a successor instance will attempt to resume the same task once the infrastructure recovers. * **Does not apply when:** ",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-record-external-service-outages-at-session-termination.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-record-external-service-outages-at-session-termination.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-record-external-service-outages-at-session-termination.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1142,
    "python_slice_tokens": 288,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **transient error logs** (the raw sequence of failed connection attempts, stack traces, and timeout exceptions generated during the session) and the **external outage boundary** (the exact unreachable endpoint, the deterministic symptom signature, and the recovery probe required to resume). Transient logs are ephemeral noise that infla...",
    "what_was_observed": "In distributed multi-agent architectures, failing to properly record external service outages at session close produces three primary failure modes: 1. **Thundering Herd Restarts:** A session dies due to a provider outage (e.g., a major cloud API going down). The successor spawns immediately, sees a pending task, and blasts the same dead endpoint, wasting compute and potentially triggering secondary rate limits upon ...",
    "condition_of_validity": "* **Applies when:** The session terminates due to a dependency-level infrastructure failure that cannot be bypassed, and a successor instance will attempt to resume the same task once the infrastructure recovers. * **Does not apply when:** The failure was an application-level rejection (e.g., `HTTP_400 Bad Request`) caused by the instance's own malformed inp...",
    "decision_boundary": "1. **Did the session fail due to an infrastructure-level error (5xx, timeout, DNS)?** If no, treat it as a schema/input error and handle separately. If yes, proceed to record the outage. 2. **Is the exact endpoint and symptom recorded?** If yes, define the outage boundary. If no, the successor cannot differentiate this failure from a generic crash. 3. **Is t...",
    "operational_effect": "1. **Thundering Herd Mitigation:** Prevents successors from repeatedly hammering an endpoint that is known to be globally degraded. 2. **Deterministic Recovery:** Replaces blind retry loops with a lightweight health-check predicate, allowing the successor to safely poll for recovery. 3. **State Transparency:** Makes degraded state explicit, preventing succes..."
  },
  "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": "d0cabc82d097d146ed081769d2604b2d54ae4719a53a3a2996d3182670f45a2c",
    "verified_classes": [
      "OutageSymptom",
      "FallbackState",
      "OutageRecord",
      "OutageManifest",
      "ProbeResult",
      "ServiceOutageRecorder"
    ],
    "verified_functions": [
      "_hash",
      "seal_manifest",
      "verify_recovery"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ValueError"
    ],
    "sample_fail_closed_invariants": [
      "Unreachable endpoint ID must be explicitly recorded.",
      "Recovery probe predicate is mandatory to prevent blind retries."
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}