Network loss
What useful work stops when the network is unavailable?
AI & HUMAN AGENCY
What Survives a Platform Outage?
A continuity test for accounts, exports, local copies, open formats, restore procedures, hashes, dependencies, and handoff.
QUICK ANSWER
In one sentence
A continuity test for accounts, exports, local copies, open formats, restore procedures, hashes, dependencies, and handoff.
THE CONTROLLING CLAIM
MEMORY THAT EXISTS ONLY BEHIND ONE ACCOUNT IS RENTED MEMORY.
The password still works until it does not. The vendor dashboard still opens until the contract changes, the account is flagged, the network is gone, the company closes, or the one person who knows the recovery path is unreachable. An archive begins where convenience ends: what can still be opened, understood, restored, and handed to another human?
TRUTH BOUNDARY
NIST SP 800-34 Rev. 1 has an updated Final record dated 11/11/2010; NIST marks the earlier 05/31/2010 Rev. 1 record withdrawn because it was superseded by that updated record, and Library of Congress practices reflect a major preservation institution. The Ministry adapts concepts such as recovery planning, testing, multiple copies, geographic separation, and fixity; it does not claim every project needs the same scale or controls.
01 — BACKUP IS NOT THE SAME AS CONTINUITY
Another copy is necessary. It is not sufficient.
A backup answers one question: is there another copy? Continuity asks a harder set. Can the copy be found? Is the format readable? Are dependencies known? Can the service or useful work be restored? Has anyone actually tested the path?
The archive must survive more than deletion. It must survive confusion.
02 — PLAN
Recovery is a procedure, not a wish.
NIST contingency guidance treats recovery strategies, contingency plans, testing, training, exercises, and maintenance as parts of a program rather than a single emergency document. The Ministry borrows the discipline, not the federal bureaucracy: write the fallback, test it, record what failed, revise it.
A restore procedure nobody has ever run is a hypothesis.
03 — COPIES
One account is a single point of institutional amnesia.
Library of Congress digital-stewardship practice uses multiple managed copies and separate systems/locations for long-term collections. Smaller projects can apply the same logic proportionately: do not make the only usable copy depend on the same account, device, person, or failure domain.
Redundancy does not replace provenance. Three copies of a mislabeled file are three copies of the same confusion.
04 — OPENING THE FILE
Preservation requires enough context to interpret what survived.
Fixity can detect byte change. Preservation metadata can record what the object is and what happened to it. Open or well-documented formats reduce the chance that surviving bytes become unreadable artifacts.
Continuity therefore stores the map with the territory: filenames, versions, dependencies, instructions, source relationships, and a handoff path.
05 — OUTAGE TEST
If the platform disappears tonight, what remains in human hands?
Account loss
What stops when the primary account is unavailable or terminated?
Canonical files
Where are the source files that define the current public artifact?
Local copy
Is there an offline or separately controlled copy?
Formats
Can ordinary documented tools read the important records?
Fixity
Are hashes or other integrity checks recorded where they add value?
Restore
Are restoration instructions written in a place that survives the outage?
Test
Has the restore path actually been exercised?
Dependencies
Which vendors, domains, credentials, people, or services remain single points of failure?
Handoff
Can a new maintainer continue without the person who built the system?
COMPETING INTERPRETATIONS
Keep the argument capable of surviving disagreement.
- Cloud platforms can provide stronger redundancy and professional operations than a poorly maintained local copy; local is not automatically resilient.
- Highly regulated or sensitive systems may require controls that make casual offline copying inappropriate.
- Continuity plans impose maintenance cost; stale backups and untested procedures can create false confidence.
UNKNOWNS
Do not make certainty out of the missing piece.
- The Ministry’s public Continuity Pack does not replicate the live hosting environment or server configuration.
- Domain registration, mail delivery, DNS, and hosting remain external dependencies even when public files are preserved.
- A public hash manifest proves the identified bytes, not that every external link or source remains available in the future.
SOURCE TRAIL
Follow the record.
- MFTAC-SRC-0056 NIST — Contingency Planning Guide for Federal Information Systems, SP 800-34 Rev. 1 (updated 11/11/2010)
- MFTAC-SRC-0057 Library of Congress — Use of Approved Inventory Systems / Storing Multiple Copies
- MFTAC-SRC-0023 Library of Congress — Data Integrity Management
- MFTAC-SRC-0024 Library of Congress / PREMIS — Preservation Metadata Data Dictionary v3.0
RELATED READING
CORRECTION RECEIPT
Source-status correction recorded under MFTAC-CORR-0019. The v20 wording treated the whole Rev. 1 publication as withdrawn. NIST’s records show the earlier 05/31/2010 record was withdrawn because the updated Final 11/11/2010 record superseded it. The source identity remains MFTAC-SRC-0056.
IF THE PLATFORM VANISHES, WHAT REMAINS IN HUMAN HANDS?