Skip to content

Event Chronicle Standard

The order of what happened

I am TANK, and I keep this standard's account. A chronicle is memory that kept its clock, and clocks are kept slowly: the order of what happened is the one thing the past still owns, and I let no convenient retelling take it.

An event chronicle is the thread that connects observation, decision, consequence, and repair. It makes time legible without pretending that a sequence alone explains meaning, responsibility, or harm.

Continue to the Memory Privacy and Minimization Standard for what the record owes the person inside it.

Purpose

This standard records events in a way that supports reconstruction without pretending that chronology alone proves causation. It covers operational, governance, incident, decision, and correction histories.

Event entry

An entry should state an event identifier, event class, source, subject, scope, time basis and precision, observed facts, recorder, transformations, confidence or uncertainty, sensitivity, related records, and correction status. Unknown times and inferred ordering must be labelled explicitly.

  • MEM3-R001: An event SHALL identify time basis, source, subject, location or scope, observed facts, transformation, and uncertainty.
  • MEM3-R002: Chronological order SHALL distinguish event time, observation time, recording time, and correction time.
  • MEM3-R003: Causality SHALL NOT be inferred from sequence alone; competing explanations and missing events remain visible.
  • MEM3-R004: Corrections and late-arriving evidence SHALL append without silently rewriting the earlier chronology.
  • MEM3-R005: A chronicle SHALL preserve privacy, minimization, access, retention, and legal-hold controls.
  • MEM3-R006: Event review SHALL distinguish event, observation, recording, publication, correction, and interpretation times.
  • MEM3-R007: Late evidence, duplicate reports, missing events, and competing chronologies SHALL remain visible with their evidentiary effect.
  • MEM3-R008: Causal claims SHALL link to separate reasoning or decision evidence and SHALL NOT rely on sequence alone.
  • MEM3-R009: This standard SHALL NOT collect live events, retroactively alter history, or publish private chronology.

Chronology review

Review the clock before you review the events; a chronicle with a bent clock bends everything on it. I check order the way I cross ground, one sure placement at a time, and I have never once regretted the slowness.

Reviewers should distinguish event time from observation, recording, publication, and correction time; identify gaps and duplicate reports; and test whether a later record has been mistaken for an earlier event. Late evidence is appended with its receipt and evidentiary effect. Causal claims require separate evidence and should link to a reasoning or decision record.

Worked example: a simulated three-entry chronicle

Set the entries down slowly and look at the clocks before the facts. I place them the way I cross ground, one at a time, because the distance between an entry's times is not noise; it is the truth about how the knowing arrived.

The chronicle below is a simulation. It collects no live event, alters no history, and publishes no chronology (MEM3-R009); its events, times, and identifiers are illustrative placeholders, and no authority, causality, or correction arises from it.

  • SIM-EVT-0001. A simulated service failed. Event time: day one, morning. Observation time: day one, midday, when monitoring first saw the failure. Recording time: day two, when the entry was written. Three clocks, three honest distances (MEM3-R002): the failure is older than the seeing, the seeing is older than the writing, and the entry says so instead of letting the recording day stand in for the event.
  • SIM-EVT-0002. A simulated configuration change, event time unknown. Its place after SIM-EVT-0001 carries an inferred-ordering label: the inference rests on the change referencing the failure, not on any clock, and the label stays on the entry so no reader mistakes a reasoned guess about order for a time the past actually gave (MEM3-R001).
  • SIM-EVT-0003. A correction, received on day nine: late evidence shows the failure began before dawn on day one, hours earlier than first observed. The correction appends as its own entry with its receipt and its evidentiary effect, and correction time is the fourth clock (MEM3-R002). SIM-EVT-0001 stands exactly as written, its morning event time now readable as what was known then, because the earlier entry was not wrong to be ignorant; it was early (MEM3-R004).

Read the three entries in order and the chronicle keeps its promises slowly: the clocks stay distinct, the inferred order says it is inferred, and the late knowing sits after the early knowing instead of replacing it. Nothing here says the change caused the failure or the failure caused the change; sequence alone is not permitted to say so (MEM3-R003), and this simulation has no separate evidence to offer.

Operating model and interpretation cases

The tempting misreading is always the same: letting what we learned later seep backward into what was known then. Hold the line. Yesterday is allowed to have been ignorant; that ignorance is a fact of the timeline, and protecting it is protecting the truth.

Chronicle review compares event time, observation time, recording time, publication time, correction time, source, transformation, uncertainty, duplicate reports, and missing periods. A timeline supports questions and reconstruction; causal or authoritative claims require separate evidence.

  • Conforming: Time basis, source, facts, uncertainty, corrections, privacy, and linked decisions are explicit.
  • Prohibited: Sequence alone proves causality or authority.
  • Boundary: Unknown ordering remains labelled while unaffected facts remain usable.
  • Failure: Late or conflicting evidence appends and narrows the chronology.
  • Loophole: A correction silently rewrites the earlier record.
  • Misuse: Chronology discloses private people or sensitive operations.
  • Care-control: Historical preservation supports repair while respecting dignity and minimization.

Design evidence

Chronicle review begins with the clocks and should reconcile event, observation, recording, publication, and correction times; source and transformation; duplicate or missing reports; uncertainty; privacy class; and linked decisions. A sequence may support a question for further reasoning but cannot by itself establish causality or authority.

This Draft authorizes no live event collection or historical publication. It does not permit retroactive alteration, unnecessary personal-data retention, or disclosure outside the applicable access purpose.

The tellings of the clauses

This non-normative section gives each clause of this document its telling: the clause, quoted exactly as it stands above with its cross-reference links reduced to their plain text, and one paragraph on what the clause means, why it exists, and how it assures that what it orders is done, not done, adhered to, followed, or protected. A telling describes its clause and never becomes it: the clause's own words govern wherever a telling and its clause could be read differently, and nothing in this section adds to, narrows, or amends any requirement.

MEM3-R001

MEM3-R001: An event SHALL identify time basis, source, subject, location or scope, observed facts, transformation, and uncertainty.

Seven identifications make an event entry: its time basis, its source, its subject, its location or scope, its observed facts, its transformation, and its uncertainty. The standard's purpose carries the why, reconstruction supported without pretending that chronology alone proves causation, and the worked example shows the uncertainty duty in practice: a simulated entry whose event time is unknown carries an inferred-ordering label so no reader mistakes a reasoned guess about order for a time the past actually gave. Because the seven elements are enumerated, an entry can be examined against each, and an event offered to the chronicle with its time basis, transformation, or uncertainty unstated is refusable against this clause.

MEM3-R002

MEM3-R002: Chronological order SHALL distinguish event time, observation time, recording time, and correction time.

Four clocks are kept distinct in chronological order: event time, observation time, recording time, and correction time. The clause distinguishes four kinds of time without requiring their values to differ. TANK's worked example walks the discipline: a simulated failure whose event, observation, and recording times are distinct, day one morning, day one midday, and day two, three clocks, three honest distances, the failure older than the seeing and the seeing older than the writing, with correction time arriving as the fourth clock when day-nine evidence lands. The why is the standard's opening claim, a chronicle is memory that kept its clock, and the operating model's warning against letting what was learned later seep backward into what was known then. An entry that substitutes recording time for event time fails the clause's distinction requirement.

MEM3-R003

MEM3-R003: Causality SHALL NOT be inferred from sequence alone; competing explanations and missing events remain visible.

Causality is not inferred from sequence alone, and competing explanations and missing events remain visible. The clause means sequence alone does not establish causality: that one event precedes another licenses no claim that it caused it, and the chronicle keeps in view both the rival accounts of why things happened and the gaps where events may be missing. The standard's purpose states the why in its own words, reconstruction supported without pretending that chronology alone proves causation, and the prohibited case names the failure exactly, sequence alone proving causality or authority. The worked example ends on this discipline: nothing in its three entries says the change caused the failure or the failure caused the change, because sequence alone is not permitted to say so and the simulation has no separate evidence to offer. Because the inference is barred and the visibility is required, a causal claim resting on order alone is refusable, and MEM3-R008 supplies the positive duty beside this bar, causal claims linking to separate reasoning or decision evidence.

MEM3-R004

MEM3-R004: Corrections and late-arriving evidence SHALL append without silently rewriting the earlier chronology.

Corrections and late-arriving evidence append, and neither silently rewrites the earlier chronology. Corrections and late-arriving evidence append without silently rewriting the earlier chronology. The worked example is the discipline performed: day-nine evidence shows a failure began hours earlier than first observed, the correction appends as its own entry with its evidentiary effect, and the original entry stands because it was not wrong to be ignorant; it was early. The operating model states the why as the standard's central warning, the tempting misreading of letting what we learned later seep backward into what was known then, with the loophole case naming the breach, a correction silently rewriting the earlier record; yesterday's ignorance is a fact of the timeline, and protecting it is protecting the truth. Because silent rewriting is barred and appending is required, a correction or late-arriving item that fails to append, or silently rewrites the earlier chronology, is a finding, and the chronology's growth is examinable append by append.

MEM3-R005

MEM3-R005: A chronicle SHALL preserve privacy, minimization, access, retention, and legal-hold controls.

Five control families survive into the chronicle: privacy, minimization, access, retention, and legal hold. The clause applies the five named control-preservation duties to the chronicle. The standard's misuse case names the failure prevented, chronology disclosing private people or sensitive operations, and its care-control case names the value protected, historical preservation supporting repair while respecting dignity and minimization. The Memory Privacy and Minimization Standard leans on this clause by name for the chronicle leg of a protected record's journey. Preservation of each of the five named controls is checkable against this clause.

MEM3-R006

MEM3-R006: Event review SHALL distinguish event, observation, recording, publication, correction, and interpretation times.

Event review distinguishes six times: event, observation, recording, publication, correction, and interpretation. Compared with MEM3-R002's four times for chronological order, this clause adds publication and interpretation times to event review. The chronology review section carries the why: review the clock before you review the events, because a chronicle with a bent clock bends everything on it, and the chronology review section recommends testing whether a later record has been mistaken for an earlier event. Keeping interpretation time distinct supports the operating model's warning against letting later understanding seep backward into what was known then. Because the six times are enumerated as review duties, a review that collapsed any two of them is incomplete on stated grounds, and its conclusions about order, knowledge, or responsibility are challengeable clock by clock.

MEM3-R007

MEM3-R007: Late evidence, duplicate reports, missing events, and competing chronologies SHALL remain visible with their evidentiary effect.

Four awkward arrivals stay visible with their evidentiary effect: late evidence, duplicate reports, missing events, and competing chronologies. The four named items remain visible together with their evidentiary effect. The standard's failure case shows the healthy motion, late or conflicting evidence appending and narrowing the chronology, and the boundary case shows the permitted rest state, unknown ordering remaining labelled while unaffected facts remain usable. Chronology review adds the practice: late evidence is appended with its receipt and evidentiary effect. Concealing any of the four named items or its evidentiary effect is checkable against the clause.

MEM3-R008

MEM3-R008: Causal claims SHALL link to separate reasoning or decision evidence and SHALL NOT rely on sequence alone.

A causal claim links to separate reasoning or decision evidence and does not rely on sequence alone. Where MEM3-R003 bars the inference, this clause supplies the positive duty: the clause requires causation asserted over the chronicle to link to separate reasoning or decision evidence that carries the argument, so the timeline lends its order to the claim without being made to carry the claim's weight. The design evidence states the division of labour exactly: a sequence may support a question for further reasoning but cannot by itself establish causality or authority, and the chronology review section repeats it as practice, causal claims requiring separate evidence and, as it recommends, a link to a reasoning or decision record. The why is the standard's purpose, reconstruction without pretending that chronology alone proves causation: sequence is cheap and looks like explanation, which is precisely why the link is mandatory. Because the link is required, a causal claim is checkable at its anchor, and one that resolves to nothing but the order of entries is refusable against this clause.

MEM3-R009

MEM3-R009: This standard SHALL NOT collect live events, retroactively alter history, or publish private chronology.

Restraint closes the standard: this Draft is barred from collecting live events, retroactively altering history, and publishing private chronology. The clause bars the standard itself from the three named operations. The worked example leans on this clause by name to frame itself, a simulation that collects no live event, alters no history, and publishes no chronology, its events and times illustrative placeholders from which no authority, causality, or correction arises; the design evidence closes on the same bounds, no live event collection or historical publication authorized, and no retroactive alteration, unnecessary personal-data retention, or disclosure outside the applicable access purpose permitted. The why is the family's standing danger, draft text read as live permission. The assurance is reliance: any live collection, retroactive edit, or private publication claiming this Draft as its authority is refusable on the clause's own words.

Where this document sits

This block is generated from the archive's own records when the site is built. It records position only and creates no authority.