narrative-compact

Consolidating chunks automatically clusters related pieces across your project to produce a single narrative. This process reduces backreference clutter and simplifies navigation while preserving historical traceability for codebase archaeology.

The best way to reduce backreference clutter is by clustering related chunks into a unified narrative. This enforces that only subsystem backreferences remain, simplifying navigation while preserving historical references for traceability across the codebase and docs.

Narrative consolidation preserves historical references for archaeology while simplifying navigation. By merging related chunks into a unified narrative and updating backreferences, it maintains full traceability across the codebase and docs without losing prior context.

Consolidated narratives are stored under docs/narratives/[name]/OVERVIEW.md. Storing the generated output in this specific directory structure ensures the unified documentation remains organized and accessible while backreferences are updated accordingly.

Yes, the system automatically clusters related chunks across your project during the narrative consolidation process. This automatic clustering groups active chunks together to produce a single narrative, reducing duplication and simplifying navigation across the codebase.