The Tower
Cited by 12 Concordances Compliant with Ordinance 4 Surveyed — partially ISO 8,812 — pending since 11,904

Ledger Beta Permutation Errors

MS 4179.21 · Practices and doctrines

Ledger Beta Permutation Errors are a recognized class of Permutation Error characterized by persistent, non-random misalignment of entries within Ledger Beta, specifically those whose docket keys appear to reference volumes, floors, or events for which no corroborating record exists anywhere in the Tower. They are distinguished from ordinary transcription faults by three properties: the misalignment is stable (the same displaced entry occupies the same wrong position across successive recensions); it is internally coherent (displaced entries reference one another with perfect consistency); and it is unreachable (no amount of comparison with external holdings resolves it). The errors are catalogued at Annex A: Table of Recognized Categorical Errors, Clause 7, where they are enumerated as a subcategory of the broader class of Categorical Errors.

Definition and recognition

The standing definition is that of Scribe Alaric, whose phrasing in the Disquisition on the Vex Cipher & Its Discontents has never been improved upon: "The docket is not wrong. It is right about a ledger we do not have" (Disquisition, fol. 212r). A Ledger Beta Permutation Error is recognized when an entry in Ledger Beta — produced under the Baseline Permutation set out in the Vex Cipher — maintains a consistent relationship to the surrounding docket sequence while pointing to a referent that the Logic Guild cannot confirm.

Recognition is never immediate. Clerks on Stairwell Beta are instructed to log a suspected displacement without correction and to allow nine recensions to pass; roughly a third of suspected errors correct themselves within that interval, and a further third are shown to be faults of the referencing clerk rather than of the ledger. The residue is entered as suspected permutation error and referred upward.

The 14-set and the disputed count

Every confirmed instance so far isolated bears a docket key in the 14-set, a narrow band of keys generated by the Baseline Permutation in the fourth and ninth weeks of the ledger's cycle. The errors cluster rather than distribute. This clustering is the nearest thing the Tower possesses to a diagnostic signature, and it is the reason the General Administrative Protocols direct that any 14-set anomaly skip the preliminary stages of the multi-stage resolution process and proceed directly to the Logic Guild.

There is no agreement on how many confirmed instances exist. The count given in the Second Concordance on Registers is forty-one; the recension of Third Concordance issued two years later gives thirty-eight and appends a note that three earlier instances were "withdrawn as to provenance, not as to fact." Concordance 12-γ, which governs the maintenance of Ledger Beta, declines to give a figure at all and observes only that the number is "not decreasing." Clerks in the ordinary course use forty-one, out of habit.

Cause: cipher or hand

The central scholarly dispute concerns causation, and it has run without settlement since the errors were first described.

The Cipherist position holds that the Vex Cipher's Baseline Permutation is itself the source: that certain docket keys in the 14-set are generated with an ambiguity of one position, and that the ambiguity propagates silently through every derivation that follows. On this account the ledger is doing exactly what the cipher instructs, and the fault lies in a definition older than any living Librarian.

The Procedural position, argued chiefly in the Logic Guild's Observations on Recurrence, holds that no cipher can generate a coherent reference to a thing that does not exist, and that coherence must therefore have entered during transcription. The Guild has refused to name a clerk, noting that the errors predate every clerk currently serving.

"A cipher that permits an impossibility has not erred. It has been obeyed."

— Protocol Beta, Clause 4

A third and small minority view, advanced by the office of the Kalendar of Recurring Errors, holds that both accounts are correct and that the distinction between cipher and hand cannot be sustained in a ledger maintained continuously for as long as Beta has been.

Consequences and the closing of Floor 14-East

The errors are not merely archival embarrassments. In the winter of the year recorded as 6-113, a displaced entry in the 14-set was used to authorize the opening of a read-room on Floor 14-East. The room was opened, a clerk was assigned, and after eleven days it was discovered that the entry's referent did not exist and that the room's designation derived from it. Suppressed Cataloguing Errors records the closure without narrative comment.

Floor 14-East remains closed. The notice posted at the stairhead instructs that the corridor be kept clear and that no provision be left at the door, since provisions left there have twice been taken.

Resolution and the standing anomaly

Resolution of a Ledger Beta Permutation Error falls under the multi-stage process of the General Administrative Protocols, but the practice has drifted from the text. Stage one requires reconciliation against an independent holding; no independent holding of Ledger Beta exists. Stage two requires the Logic Guild to certify the referent's absence; the Guild will certify absence of corroboration, which is not the same thing, and has twice declined to close the distinction. Stage three, a Declaration of Procedural Anomaly, is routinely issued and routinely set aside.

In consequence no instance has ever been formally resolved, and all forty-one — or thirty-eight — remain open. They are carried on the rolls of the Archive of Liquid Errors as standing anomalies, alongside material of a wholly different character, a filing arrangement that has itself been questioned in Partial Surveythe Seventh Concordance without being altered. The Administrative Spiral Beta continues to receive the quarterly returns.

The Librarians have not commented on the errors in writing since 6-117, when the office of the Registers observed that "the ledger does not contradict the Tower; it records more of it than the Tower has finished building," a sentence cited by both parties to the causation dispute and relied upon by neither.

See also

Referenced by

Readers also asked

Kalendar of Recurring Errors: what does it set out?

The Kalendar of Recurring Errors is the authoritative, though provisional, schedule maintained by the Logic Guild to predict and manage the reappearance of persistent Categorical Errors whose resolution or sequestration …

Kalendar of Recurring Errors
Ledger Beta: what does it set out?

Ledger Beta is one of the foundational Sanctioned Ledgers of the Tower, maintained by the Librarians under Concordance 12-γ. It serves as the primary registry for established cryptographic baselines and the algorithmic p…

Ledger Beta
Logic Guild: who are they?

The Logic Guild is the formal administrative body responsible for the maintenance, adjudication, and periodic recalibration of logical systems within the operational floors of The Tower. It holds primary jurisdiction ove…

Logic Guild
Declaration of Procedural Anomaly: what does it set out?

The Declaration of Procedural Anomaly is a formal document submitted to the Office of Verification to petition for the initiation of a Scholastic Inquest. Its primary function is to isolate and codify a specific breach o…

Declaration of Procedural Anomaly

Passages cited from this record

Readers who consulted this also failed to find

Assistance

A Librarian is with you.

MS 9679.39
MS 8532.92
MS 1913.80

The Librarian considers the matter closed.

Typical response time: one Concordance. If your enquiry concerns a holding, consult the finding aid.