Incident Chronology

Overview

An Incident Chronology (IC) is a practical system of subsidiary chronologies within the Tower Standard Chronology, applied exclusively to events of structural or existential significance. The framework provides a temporally isolated index for cataloguing the sequence and duration of phenomena that disrupt, challenge, or redefine the Tower's ontological integrity. According to Annex A of the Tenth Concordance, an Incident Chronology is "an administrative necessity, a procedural firebreak between the standard flow of record and the aberrant event."

Establishment and Legal Precedent

The legal and procedural foundation for Incident Chronologies was solidified by the Omega Discrepancy in TSC 892. This incident established the necessity for a formal framework to govern self-contradictory chronology, where two verifiable events were recorded as occurring in mutually exclusive temporal sequences. The ruling, codified in Clause 7.14 of the Seventeenth Concordance, mandates the immediate initiation of a dedicated IC upon the formal declaration of a qualifying incident by a Senior Librarian of the Chronology Oversight Guild. The chronology resets to zero at the officially recognized moment of the event's inception, designated IC 0.

This practice was further refined and made mandatory across all archival stacks following the Incident of the Fogged Calibration in the late 1130s TSC. The widespread dating contradictions that emerged from that period necessitated the creation of the Standard Archive Chronology and clarified that all subsidiary Incident Chronologies must maintain a published calibration table against the Tower Standard Chronology to permit eventual reassimilation of records.

Qualifying Criteria and Declaration

Not every disturbance rises to the level of requiring an Incident Chronology. The Fifth Concordance, Section "Temporal Anomalies," lists seven qualifying criteria, including but not limited to: the spontaneous manifestation of a catalogued non-existent subject outside its designated holding; a verifiable rupture in the spatial continuity between floors; or the persistent failure of a Stairwell Chronology to align with adjacent floors. The declaration is typically precipitated by the filing of a Discrepancy Report (Form 744-Epsilon) by a floor curator, though the Elliptical Schism of TSC 742 demonstrated that incidents can also originate from procedural failures, such as mismanufactured Elliptical Containers.

Upon declaration, the affected sector is placed under Provisional Temporal Quarantine. All personnel within are issued secondary timepieces calibrated to the new IC, and all log entries, material transfers, and even personal diaries must henceforth be dated using the incident's timeline. This creates a clean, self-consistent record isolated from the potential contaminating influence of the Tower's primary temporal flow.

Closure and Archival Integration

Most Incident Chronologies are temporary. According to Standard Procedure 18.6, an IC is considered closed when the originating phenomenon has been fully contained, catalogued, or has demonstrably ceased all interactive properties for a period no less than one full TSC year. A Closure Audit is then conducted by the Verification of Chronology bureau.

Once closed, the entire corpus of records generated under the IC undergoes a process known as "temporal folding." The incident's timeline is painstakingly mapped back onto the Standard Archive Chronology using its calibration table. The original IC-marked documents are preserved in a dedicated annex, but for all standard research purposes, the events are understood within the continuous stream of the Primary Chronology. The Collapse of the Western Stack, for instance, is now referenced under its TSC dates, though its complex internal sequence was originally documented under the now-closed IC detailed in the Seventeenth Concordance.

Notable Exceptions and Ongoing Debates

Certain incidents defy standard closure protocols. The Catalogue Lacuna Incident, for example, maintains an open Incident Chronology currently extending to IC 4173, as the phenomena responsible—periodic erasures of specific cross-reference links—continue to recur at irregular intervals. Scholars within the Metachronic Studies Wing argue this suggests some incidents are not discrete events but permanent low-grade fractures in the Tower's archival substrate.

A significant doctrinal disagreement, often called the "Attainment Debate," centers on whether the act of declaring an Incident Chronology itself can become a secondary inciting event. This stems from analysis of the Post-Incident Debriefing Log 891-Sigma, which outlines a 'Chronology of Attainment' for a Junior Librarian that appears to loop back upon the moment of the IC's own initiation. The Gamma Aperture Incident reports contain similar paradoxical timestamps, leading some archivists to advocate for a meta-chronological layer, a proposal repeatedly tabled by the Librarians as "prematurely recursive." The prevailing view, upheld by the Promulgation of Harmonized Chronology, is that an IC is a purely descriptive tool and cannot possess causal agency.

Administrative Purpose

Ultimately, the Incident Chronology is a bureaucratic containment strategy. It allows the Tower to process the impossible without allowing the impossible to destabilize the entire edifice of recorded time. By granting a localized anomaly its own clock, the larger chronological integrity of the archive is preserved. As the maxim from the Incident of the Fogged Calibration recovery report states: "It is not the contradiction that corrupts the record, but the failure to bracket it properly."