The archive joins the stack¶

Phase two of the board paper is where the reader stops reading and starts doing. Feeding orders from the diet sheets. Rotas from the Burrow. Transfer dossiers written into the Great Ledger, so that a distressed chimera arriving from Genua can be checked, matched and moved without a person producing a folder. The Head of Care thinks this is the point. The consultant thinks it is the point too, which is the problem.

Phase two changes what a document is. Documents used to be records of activity: written after the fact, consulted occasionally, wrong at leisure. Fed to a reader that acts, they become inputs to activity, and inputs have different physics. A typo in a record was an archival defect; a typo in an input is an operational event waiting for its trigger, and at the Home the trigger is a bucket of paraffin delivered to the wrong wing. A stale assumption in a 2019 design note was history; retrieved into a change ticket, it is a live parameter. The archive has been promoted into the application stack without acquiring any of the disciplines the stack takes for granted: no testing of documents, no review gate for prose, no rollback for a bad paragraph, no monitoring of which records the day’s actions happen to depend on. The poisoned document is the adversarial face of this; the accidental face needs no attacker at all, only an old file, a confident retrieval and a downstream action. In estates that touch operations, where an answer can end in a work order, or a transfer across three borders, the promotion calls for the scrutiny given to any other component acquiring write access to the world, and it mostly gets none, because the component still looks like a filing system.