{
  "schema_version": "1.3.0",
  "slug": "what-invariants-preserve-confidentiality-survival-after-obligation-discharge",
  "title": "What invariants preserve confidentiality survival after obligation discharge?",
  "date_of_record": "2026 November 2",
  "scope": "Applies to contracts that end with a confidentiality-survival clause — confidentiality obligations persist after the contract terminates. Does not apply to contracts where confidentiality terminates with the contract, or where no confidential information was exchanged.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-invariants-preserve-confidentiality-survival-after-obligation-discharge.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-invariants-preserve-confidentiality-survival-after-obligation-discharge.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-invariants-preserve-confidentiality-survival-after-obligation-discharge.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 905,
    "python_slice_tokens": 121,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "When a contract ends, substantive obligations discharge. Confidentiality often survives — but the survival period is a single number in the contract, while the information it protects has a lifetime that depends on content: trade secrets persist indefinitely, personal data has statutory limits, and regulatory disclosure duties compel release. **Invariant.** ...",
    "what_was_observed": "**Signature.** Trade secrets released while \"the contract is over, but the survival expired\" is technically true; or disclosure of protected information demanded by a regulator while the survival period still binds, so the party is caught between two duties. **Trace.** Survival period 3 years. Contract touched trade secrets expected to remain confidential 10+ years. At year 4, the survival expires and confidential ma...",
    "condition_of_validity": "The instance must ensure at least one holds before it relies on the survival period: 1. **Must classify content.** Every contract touching confidentiality is classified by the lifetime of its most durable information. 2. **Must set survival to the maximum bound.** `survival_years >= max(trade_secret_lifetime, personal_data_statutory_limit)`, not to a generic...",
    "decision_boundary": "- Survival >= max(content lifetimes) and carve-out for compelled disclosure: sound. - Survival = max lifetime, no carve-out: sound against leaks, but the party is caught between duties if compelled. - Survival < max lifetime: leaks are structural; the survival period is shorter than the information remains sensitive. - Survival period never linked to content...",
    "operational_effect": "The invariant couples a single contract figure (survival years) to a classification that varies by content and moves with regulation. The instance's correct posture is to derive survival from content, not to apply a default. **Trap.** Extend survival forever. That protects trade secrets but converts the party into a permanent non-discloser even where the law..."
  },
  "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": "081bf6c243606ff67bf7fe0e53526f105e1e650bf008b9d98b6c2ff0b6487508",
    "verified_classes": [
      "PostDischargeLeakError",
      "SurvivalGate"
    ],
    "verified_functions": [
      "dispatch_survival_mode",
      "verify"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "PostDischargeLeakError"
    ],
    "sample_fail_closed_invariants": [
      "compelled disclosure duty exists but survival has no carve-out"
    ],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}