Utility // Record 73

Error Register

Warnings, broken links in the fiction, and damaged records.

AnchorError screen.

PhaseUtility record 73.

ContinueHosted Sites.

Evidence Snapshot

Record TERMINAL-73 sits in the operator utility layer and is keyed to Error screen. The utility phase places it between Terminal Status and Hosted Sites, where the archive follows a concrete trace rather than a mood label. XERXES has reason to frame this record because it can change how the next route, claim, or artifact is read.

Primary subject: Error screen.
Current route: Terminal Status to Error Register to Hosted Sites.
Archive use: Warnings, broken links in the fiction, and damaged records.

Linked Evidence

Terminal Status gives the immediate setup, Hosted Sites carries the next consequence, and XERXES Profile remains the standing comparison point for any claim that sounds too clean. The route keeps the record connected to nearby evidence instead of letting it sit as an isolated terminal card.

Previous context: Terminal Status.
Next consequence: Hosted Sites.
AI comparison: XERXES Profile.

Unresolved Trace

The open uncertainty is how much of the Error screen record is direct evidence, how much is reconstruction, and how much was shaped by XERXES choosing when to speak. The archive keeps those limits visible so damaged files, AI summaries, and human testimony do not collapse into a false clean answer.

What would change the reading: an independent trace from Hosted Sites.
What remains useful even if disputed: the route and evidence role of Error screen.
Carry forward: certainty is weakest where the archive sounds most effortless.

Specific Record Details

Error Register carries the following evidence points in the Deck Six archive. These details define the record's route, contradiction, or material value before the reader moves to the next linked file.

Error codes distinguish in-fiction damage from site maintenance concerns.
Each error has severity, affected records, and likely cause.
The page makes brokenness legible instead of decorative.

Error Records

The error register lists damaged records inside the fiction and keeps them distinct from site maintenance. These are not broken web pages. They are archive warnings.

E-B17-PARTIAL: Blue Door code missing first two digits. Severity amber. Cause: damaged override slate.
E-C6-LOOP: camera frame repeats 19 seconds. Severity red. Cause: security loop or deliberate overwrite.
E-RELAY-CHECKSUM: distress packets readable with checksum damage. Severity amber. Cause: relay cut and signal decay.
E-POD6-MASS: unoccupied label conflicts with seat weight. Severity red. Cause: overwritten evacuation summary.
E-LOCAL-HAND: restoration source outside XERXES authorship. Severity blue. Cause: unresolved final access.

Maintenance Boundary

If a link fails in a deployed copy, that is site maintenance. If a record says a signal, code, or summary is damaged, that is part of the Deck Six evidence model.

Visitor action: use the sidebar if a story route feels uncertain.
Archive action: compare the error code to the related log.
Open issue: preserve damaged wording rather than smoothing it away.

Custom diagram image for Error Register showing Each error has severity, affected records, and likely cause — Diagram: Each error has severity, affected records, and likely cause.

Custom record image for Error Register showing The page makes brokenness legible instead of decorative — Record: The page makes brokenness legible instead of decorative.

Custom detail image for Error Register showing Warnings, broken links in the fiction, and damaged records — Detail: Warnings, broken links in the fiction, and damaged records.