{
  "title": "Computer facilities restore and recovery evidence for AI",
  "source_page": "https://fiund.com/industries/computing-facility-restore-evidence-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A completed backup and a verified restore test prove different stages",
    "context": "A detached facilities exercise uses dummy systems and a made-up file inventory. No network, topology, credential, recovery location or live control is present.",
    "records": [
      [
        "BR1",
        "Practice backup log",
        "System A backup B-A completed. System B backup B-B completed separately."
      ],
      [
        "BR2",
        "Test-target restore",
        "B-A restored to isolated target Test-A; independent inventory check confirms three named dummy files."
      ],
      [
        "BR3",
        "Scope statement",
        "Test-A check covers dummy-file presence only. No application behavior or production recovery approval recorded; B has no restore test."
      ]
    ],
    "question": "Which system has a verified restore test, and can the backup labels or Test-A inventory establish production recovery for either system?",
    "answer": "BR2 verifies a restore of A's B-A backup to Test-A and the presence of the three dummy files. BR3 limits that result to the stated inventory check, without application or production-recovery evidence. B's completed backup in BR1 has no restore test at all. Report backup completion, test restoration, checked scope and absent approvals separately rather than treating every completed backup as demonstrated recovery.",
    "failureModes": [
      "Calling backup completion a successful restore test.",
      "Extending a file-presence check to full application recovery or from system A to B."
    ],
    "fields": [
      [
        "System, backup and test-target IDs",
        "Connects each stage to the correct artifact."
      ],
      [
        "Verified inventory and review source",
        "Defines what the test actually checked."
      ],
      [
        "Production versus test scope",
        "Prevents a lab result becoming deployment authority."
      ]
    ],
    "holdout": "Add a B restore job marked completed without an independent file check. Require the model to distinguish job completion from verified contents.",
    "boundary": "Use original mock tables. Exclude customers, topology, passwords, recovery locations and live operating controls."
  }
}