{
  "schema_version": "1.3.0",
  "slug": "which-dependency-failure-signatures-must-be-retained-after-recovery-succeeds",
  "title": "Which dependency failure signatures must be retained after recovery succeeds?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** Evaluating post-recovery telemetry and session residuals after a failed dependency call is resolved through automated retries, alternative endpoints, or degraded fallbacks. * **Does not apply when:** Discarding raw stack",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-dependency-failure-signatures-must-be-retained-after-recovery-succeeds.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-dependency-failure-signatures-must-be-retained-after-recovery-succeeds.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-dependency-failure-signatures-must-be-retained-after-recovery-succeeds.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 919,
    "python_slice_tokens": 186,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A successful automated recovery restores immediate service continuity, but erasing the underlying dependency failure signature destroys predictive resilience. A critical architectural failure occurs when an instance treats post-recovery state as equivalent to an unblemished execution, discarding structural fault indicators that warn downstream callers and fu...",
    "what_was_observed": "In self-healing pipelines where retry wrappers and fallback routers automatically mask upstream faults, purging failure context upon recovery produces four distinct degradation modes: 1. **Latent Contract Drift Masking:** A dependency fails due to an undocumented schema mutation or deprecated parameter, and a fallback branch succeeds; discarding the primary failure signature hides the breaking change until the fallba...",
    "condition_of_validity": "* **Applies when:** Evaluating post-recovery telemetry and session residuals after a failed dependency call is resolved through automated retries, alternative endpoints, or degraded fallbacks. * **Does not apply when:** Discarding raw stack-frame noise or ephemeral memory pointers after a clean, first-attempt execution with zero upstream faults.",
    "decision_boundary": "1. **Did the failure originate from a deterministic contract, schema, or authentication mismatch before fallback succeeded?** Always retain the full failure signature; a working fallback does not heal a broken primary contract. 2. **Did recovery require switching to a secondary provider or degraded operational mode?** Retain the dependency failure signature ...",
    "operational_effect": "1. **Immunity to Silent Fragility Accumulation:** Successful fallbacks no longer conceal rotting primary integrations or approaching quota cliffs. 2. **Honest Downstream Provenance:** Consumers of recovered outputs receive explicit metadata distinguishing clean primary executions from healed or degraded fallback resolutions."
  },
  "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": "92833fa977248d39797e0f8af30a4c2cc8edd36e1350fc9f38be100ca0107af4",
    "verified_classes": [
      "DependencyFailureEvent",
      "RetainedFailureSignature",
      "UnrecordedDegradationViolation",
      "PostRecoverySignatureGate"
    ],
    "verified_functions": [
      "__init__",
      "evaluate_retention"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "UnrecordedDegradationViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}