Lifecycle

Append, mutate, consolidate

The layer determines how memory is allowed to change. Some records are living documents; others are evidence that should only gain corrections.

Append vs mutate matrix

LayerDefaultRule
IdentityMutate with evidenceAppend only when preserving correction history matters.
SemanticMutate stable factAppend dated evidence in episodic before major changes.
EpisodicAppend by defaultNever silently rewrite event history.
ProceduralMutate current runbookLink major process shifts to decisions.
ReferenceMutate verification metadataAppend source change notes when provenance matters.
WorkingMutate or deleteConsolidate before expiry.
DecisionsSupersedeDo not rewrite accepted rationale.
Janitor consolidation walkthrough.
The Janitor turns contradiction into a linked correction path.

Janitor

Consolidation loop

Find drift.Compare current semantic, procedural, and identity notes against episodic evidence and decisions.
Resolve conflict.Pick the winning record, create corrections, and mark superseded decisions when needed.
Validate links.Check cross-layer links, reference locations, and INDEX.md entries.
Record telemetry.Log routing corrections so the next router learns from actual failures.