Layer 3

Episodic: Dated events

What happened, when, and what evidence proves it?

Canonical path	`episodic/YYYY/MM/`
Trigger	Meetings, observations, incidents, corrections, dated decisions before ADRs.
Stores	Append-only event records with dates, participants, and source context.
Avoid	Timeless facts without dates and instructions meant to be reused.
Lifecycle	Append corrections; do not silently rewrite the original record.

Dated evidence layer

Episodic is the ground truth for what happened. The Janitor uses it to detect drift, reconcile current facts, and justify updates to semantic, procedural, identity, and decision records.

Path shape	`episodic/YYYY/MM/` keeps chronology easy to scan without inventing topic folders.
Correction rule	Append a correction note with date and reason. Do not silently rewrite the old event.
Janitor role	When facts drift, episodic records provide the evidence trail for consolidation.

Janitor consolidation walkthrough from stale facts to corrected records. — A drift audit starts from contradiction and ends with a linked correction.

Event record

---
type: episodic
date: 2026-05-05
source: implementation-review
---
The benchmark charts were identified as synthesized and must
not be used for performance claims until a harness exists.

Correction record

---
type: episodic
date: 2026-05-06
corrects: 2026-05-05-benchmark-note
---
The harness now measures all seven trigger classes. Replace
the synthesized SVG charts with generated benchmark output.