# Meridian case chronology

An application projection over existing canonical observations, entity assertions,
claim evaluation times and case membership. No source record or date is changed.
All people, dates and activity are fictional. This does not add a standard contract.

Each entry retains its document identity, exact JSON pointer, temporal declaration,
SHA-256 and length. Entity dates require exactly one assertion: the builder refuses
to choose among multiple assertions or unsupported temporal precision. Unknown
and redacted dates remain unplaced. Day-only values never become midnight UTC.
The field interval and review instants use their declared UTC times. Grouping by
date does not impose a within-day order on day-only records.

From this folder with Node 22, rebuild the projection against the adjacent retained
packets and source library:

```sh
node --input-type=module -e 'import { build } from "./build.mjs"; await build("..");'
```

The builder checks input bytes against the library before projecting. Run each
source packet's own pinned verifier to repeat canonical validation. The timeline
is not a second validator or an authenticity check. Its display labels and links
are editorial navigation; case membership comes from the retained case document.

The original sourcebook chronology remains available at
`../reader-r2/sources/chronology.csv`. This view reads canonical date fields so
account creation, report issue, specimen work and later reviews stay distinct.
It is a selected case chronology, not an inventory of every bench capture or
every timestamp found anywhere in the collection. Separate instrument captures
retain their own clocks and are not assigned to the field window.
