Skip to content

Event Chronicle Standard

Why this chapter matters

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.

Return to the Book of Memory when the record needs its principles of context, privacy, and correction.

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, minimisation, 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

Reviewers should distinguish event time from discovery, 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.

Operating model and interpretation cases

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 minimisation.

Design evidence

Chronicle review 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 authorises no live event collection or historical publication. It does not permit retroactive alteration, unnecessary personal-data retention, or disclosure outside the applicable access purpose.