Reconstructing effective glossary state and decisions from canonical append-only events.
Context
System Events
Status
canonical
Applicable to
1.x, 2.x
Invariant
No side-channel state may be required for correctness
Telemetry (Out of Scope for This Slice)
Definition
Optional usage/cost analytics and operational observability fields layered on top of core event contracts.
Context
System Events
Status
candidate
Applicable to
1.x, 2.x
Note
Not required for glossary semantic integrity in this 2.x adoption slice
Dossier Event
Definition
An event emitted during dossier operations. Four types: ArtifactIndexed (artifact scanned), SnapshotComputed (snapshot created), ArtifactMissing (required artifact not found), ParityDriftDetected (content changed since baseline).
An event that is only emitted when something unexpected happens — such as a required artifact being missing or parity drift being detected. Unlike routine lifecycle events, anomaly events signal conditions that may need the Human-in-Charge's attention.
The standard event emitted when a work package moves from one lane to another (e.g., from planned to in_progress). Part of the status model's event contract.
A logical counter included in event envelopes that tracks the order events happened in, without relying on wall-clock time. Each new event increments the counter, ensuring events can be reliably ordered even across different machines.