{
  "schema_version": "1.3.0",
  "slug": "what-invariants-must-survive-when-only-metadata-survives-a-backup-restore",
  "title": "What invariants must survive when only metadata survives a backup restore?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The backup includes metadata and payload, but restoration can be partial, and the agent will serve traffic against the restored state. * **Does not apply when:** The backup is verified to contain complete payload data, o",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-invariants-must-survive-when-only-metadata-survives-a-backup-restore.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-invariants-must-survive-when-only-metadata-survives-a-backup-restore.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-invariants-must-survive-when-only-metadata-survives-a-backup-restore.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 950,
    "python_slice_tokens": 251,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **metadata restorability** (schema, indexes, and pointers survived the restore) and **payload restorability** (the actual data referenced by that metadata survived). Relying on metadata creates the **Phantom Structure Illusion**: the restored session sees tables, indexes, and pointers that look intact, serves queries, and returns empty...",
    "what_was_observed": "In backup restoration architectures, failing to distinguish metadata from payload restoration produces three primary failure modes: 1. **Empty-Result Confidence:** The agent queries the restored database, gets no results, and reports \"no data matches\" rather than \"data unavailable,\" causing false negatives. 2. **Dangling Foreign Keys:** The metadata references rows that no longer exist, and joining queries return inc...",
    "condition_of_validity": "* **Applies when:** The backup includes metadata and payload, but restoration can be partial, and the agent will serve traffic against the restored state. * **Does not apply when:** The backup is verified to contain complete payload data, or the environment supports lazy payload reconstruction from an authoritative source.",
    "decision_boundary": "1. **Was the backup's payload coverage verified after restore?** If no, the restore is metadata-only until verified. The agent must not serve reads. 2. **Can the payload be reconstructed from the `reconstruction_source_manifest`?** If yes, execute reconstruction before serving. If no, mark the metadata `PHANTOM` and refuse reads. 3. **Does the `dangling_refe...",
    "operational_effect": "1. **False-Negative Prevention:** Prevents the agent from reporting \"no data\" when the truth is \"data unavailable.\" 2. **Compliance Integrity:** Prevents the agent from falsely certifying retained data. 3. **Deterministic Restore:** Forces the session to verify payload coverage before accepting the restore as complete."
  },
  "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": "829a2ba9f2f9ab764889ca26b01c62ec90f865c016404b3d5bf2f756c21588a1",
    "verified_classes": [
      "RestoreVerdict",
      "RestoreState",
      "RestorePolicy",
      "RestoreManifest",
      "MetadataOnlyRestoreGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_restore"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "ValueError"
    ],
    "sample_fail_closed_invariants": [
      "Restore must include at least one metadata artifact."
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}