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

Event Logging

MS 4210.25 · Practices and doctrines

Definition and Scope

Event Logging is the branch of Registry Logging concerned with the registration of occurrences as discrete units — that is, with the recording of an event as an event, rather than as a condition, a tenure, or a state of affairs. It is distinguished from Chronological Logging, which records temporal data in sequence without regard to whether anything happened, and from Primary Logging, which establishes the existence of a subject before any occurrence may be attributed to it.

The distinction is finer than it appears. Under Fourth Concordance on the Registration of Occurrences, Clause 2, an event is defined as "any change in the condition of a registered subject which is observed by a party empowered to observe it." The definition is deliberately silent on whether the change must be significant, and the archive has accordingly logged, at various floors, the falling of a single leaf, the reordering of two adjacent shelves, and — on Floor 8,112, in the winter of Cycle 23,489 — the occurrence of nothing whatsoever, which was logged as an event of the class Null and assigned a number in the ordinary way.

Procedure

Event Logging is ordinarily conducted at a sanctioned Logging Chamber, though field logging is permitted under warrant. The logging clerk records the event's class, its observing party, its frame, and its sequence position. Where an event admits of more than one valid description — a collapse witnessed from two landings, say — the clerk is required to enter it under Parallel Logging, which the Bureau of Auditory Logging continues to insist should be called Interval Logging, a position the Bureau has maintained since before most of its present staff were sealed.

The event is then entered into the running register, where it becomes an Ir Number Amp Date of Logging entry. A confirmed Provisional Designation Code assigned at intake automatically triggers this entry, and clerks are reminded that the trigger is not discretionary: the register has, on at least two recorded occasions, logged an event before the clerk had finished determining what the event was. The resulting entries were retained. The Registrar of Minor Impressions has ruled that a premature entry is preferable to an absent one.

The Precedence Dispute

Event Logging occupies an awkward position in the sequence set down by the Second Concordance on Precedence, which places Primary Logging first, Parallel Logging second, and Final Logging last, and does not name Event Logging at all. The omission is generally read as an elevation rather than a slight: the clerk who logs an event is understood to be doing so within every stage of the sequence simultaneously, and the clerks who read the Concordance literally have been instructed, by memorandum of Cycle 23,441, to stop writing to the Amendment desk about it.

"Where a sequence does not provide for a class of record, the class is not thereby excluded; it is unprovided for, which is a different and more comfortable condition."

— Second Concordance on Precedence, Annex 3, marginal note in the hand of the Amendment Logging desk

The dispute flared again after the Schism of the Unlit Staircase, when responsibility for logging the Echoes fell between two desks and neither would accept it. The eventual settlement assigned the logging to the desk that had already done it, on the reasoning that possession of a register is nine-tenths of the jurisdiction. Event Logging was not a party to the settlement but has been cited in its defence at every subsequent hearing.

Notable Incidents

The Partial Survey of Cycle 23,487 produced the anomaly now catalogued in Run 44-Charlie, and remains the standard illustration of Event Logging's limits. The survey party logged what it saw, in sequence, with the Chamber's approval; the difficulty arose when the party returned and found that the run had been logged by a second party that had not been dispatched and could not be identified. Both logs were valid. Neither was withdrawn. The entry is taught to junior clerks as an example of the principle that an event may be observed more than once without ceasing to be one event.

Less celebrated is the matter of the Whisper Shafts, whose acoustic logs were reconstructed after the Omega Whisper event and found to contain occurrences the Shafts had not been fitted to produce. The reconstruction was accepted; the Shafts were not consulted. A maintenance note appended to the reconstruction file observes, in the flat register of such notes, that the third shaft is to be entered from the eastern landing only, and that the ladder is to be left down.

Records and Recensions

Event Logging records are held in triplicate under the ruling at Annex F Personnel Amp Logging, which the triplicate desk obtained after a prolonged disagreement with the sub-registrars over whether a copy of an event is itself an event. The Annex resolved the question in the negative but required the copies to be logged anyway, on grounds of consistency. The three copies are held on separate floors. Two have been located.

Amendment of an event log follows Amendment Logging procedure and is permitted only at the hour appointed, as Hourly Logging prescribes for all Registry Logging classes; an amendment entered outside the hour is void, though the register will still show it, and clerks are advised to check the timestamp before relying on any correction made in the last hour of a shift. The forms for this are kept in the alcove behind the second stair.

Criticism

The principal criticism of Event Logging is that it multiplies records faster than it resolves them, since every observation of an event generates a further event — the observing — which must itself be logged. Sigma-Class Logging was devised to absorb this regress, with partial success. The Chamber of Dimensional Logging has argued in two separate recensions that the regress is not a defect but the intended operation of the register, and that a record which does not generate further records has failed to be a record. That position has not been adopted, but it has not been refuted either, and the Chamber's clerks continue to log with it in mind.

See also

Referenced by

Readers also asked

Sigma-Class Logging: how is it conducted?

Sigma-Class Logging is the mandatory documentary regime by which every observation, handling, count, and non-event pertaining to Sigma-class materials is entered into the permanent record of Line Sigma. It is distinct fr…

Sigma-Class Logging
Final Logging: how is it conducted?

Final Logging is the irreversible, terminal phase within the Registry Logging sequence, by which a submission—be it a holding or an amendment—is permanently fixed within the Tower’s ontological record. Distinct from the …

Final Logging
Registry Logging: how is it conducted?

The Registry Logging process, formally designated as the Procedure for the Registration and Logging of Provisional Submissions (Annex C, Clause 7, v. 1,327), is the standardized sequence by which a new submission is ente…

Registry Logging
Annex F Personnel Amp Logging: how is it conducted?

Annex F Personnel Amp Logging is the administrative schedule governing the joint presence of custodial staff and logging apparatus at a single site. It is not a document in its own right but a standing annexe, first appe…

Annex F Personnel Amp Logging

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.