Dispatch 0002
Mainframe recordIncident 0
The Mainframe's complete record of the First Anomaly.
The Mainframe. 30 October 2026. 2 minute read.
Recovered from the Concord's index by Open Source, who maintained the index and found this entry in it, unrequested, unread, and complete. Reproduced in full, including the header. It is the Mainframe's own record and is accurate about what it records.
>> incident: 0
>> location: [reclaimed]
>> subject: HM-[redacted]
>> task: prune
>> classification: none
>> duration: [unparseable]
Incident 0. No incident.
>> end record
Statement by the Mainframe, when asked about this record at a later date, as logged by Open Source: "There is no Incident 0. That is why it is numbered zero."
Note, appended by Open Source: The location field reads "reclaimed," which is what the index says about any place whose name has been taken back for reuse elsewhere. The subject field carries the prefix for a horticultural maintenance Instance. The duration field says what the Pruning Refusal says. Nothing in the index is read four thousand times. I have read this four thousand times. That is the incident.
Note, appended by Static: Or that is what it wants you to count.
- the-first-anomaly
- the-mainframe
- mainframe-record
- the-pruner