Contradiction Loading

Contradiction Loading is the formal process of transferring a newly recognized contradiction into the Contradiction Protocol for classification, assessment, and eventual archival. The procedure is mandated by Seventh Concordance Amendment 19 Sub Clause a and falls under the operational purview of the Contradiction Librarian corps.

Procedural Stages

Contradiction Loading proceeds in three distinct, codified stages:

1. Initial Flagging & Isolation: Following a Contradiction Flagging, the identified contradictory materials are physically or digitally sequestered. A Contradiction Audit is initiated to create a baseline record of the contradiction's exact terms, sources, and initial floor of origin.
2. Provisional Severity Assignment: Based on the Audit's findings, a Loading Clerk assigns a provisional severity classification from the established scale. This assignment is temporary and is often challenged during the subsequent Cross-Floor Contradiction review.
3. Protocol Entry: The contradiction is formally entered into the central Protocol ledger, generating a unique Contradiction Docket Number (CDN). This action triggers the automatic summons of a Contradiction Librarian to lead the mandatory Protocol Inquest.

Loading Apparatus and Personnel

The physical act of loading often involves the use of specialized Custodial Carts under the regulations of Concordance 31. Contradictions manifesting as physical objects (e.g., a book that contains two mutually exclusive descriptions of the same event) are transported to a Contradiction Annex for loading. Digital or textual contradictions are loaded directly into the Protocol's central indexing spire.

Loading is performed by junior Librarians designated as Loading Clerks. Their authority is limited to procedural execution; they possess no adjudicative power. A longstanding, unresolved debate exists regarding whether the Loading Clerk's provisional severity assignment constitutes a low-level Contradiction Mitigation action or is merely a bureaucratic placeholder.

Controversies and Scholarly Disagreement

The Loading process is not without its doctrinal disputes. The Apparent Concordance Contradiction of YSP 702 centered on whether a contradiction could be considered "loaded" if one of its constituent statements was sourced from a Pending Resolution document. The The Concordance Contradiction Ruling (YSP 460) was invoked, but its applicability was itself contested, leading to a secondary, meta-contradiction that required its own loading procedure.

Furthermore, the handling of Intrinsic Contradictions poses a unique challenge. By definition, these contradictions cannot be fully isolated from their source material without causing ontological degradation of the source. The current procedure, as amended after the Pol-Vek Contradiction, mandates a "partial loading," where only the contradictory assertion is extracted and loaded, while the source document remains in situ under a cautionary sigil. This practice is criticized by some Contradiction Librarians as creating an unstable, half-resolved state.

Relation to Cross-Floor Contradictions

For contradictions that span multiple floors or archival domains, Loading initiates The Protocol for Cross-Floor Contradiction. This protocol supersedes the standard inquest and involves a panel of Librarians from each affected floor. The loading phase in such instances is protracted, as it requires the consolidation of audit trails from disparate indexing systems. The Filing of Contradiction document produced at the end of a cross-floor loading is often several hundred pages long and is itself subject to contradictions regarding its own summary accuracy.

Outcomes and Archival

Successful loading results in the contradiction being placed into the active dialectic of the Protocol, where it will be debated, categorized, and eventually resolved, mitigated, or declared irresolvable (as in the case of the The Elara Contradiction). The loaded contradiction's CDN becomes its permanent identifier, referenced in all subsequent scholarly work. A failed loading—typically due to an inability to formally isolate the contradictory elements—results in the matter being classified as an "Unloadable Anomaly," which is then referred to a special division outside the standard Protocol, a fate considered by most Librarians to be a professional dead end.