01//DefinitionTerm

// ##eo-def =Episodic Overlay — a separate data layer that stores user interactions superimposed on the document .Think: a transparency sheet laid over a map .Contains your history, not the document's content

---

02//SeparationPrinciple

// ##eo-sep !The Overlay never modifies the source CLN file -Source remains pure and shareable -Overlay is personal (local storage) or collaborative (server sync) +One document → Multiple overlays (different users/perspectives)

---

03//CompositionStructure

// ##eo-data .Stores Interaction Traces (anchors, tags, decisions) .Linked by Spatial IDs (e.g., line #S5) .Includes Temporal Context (timestamps)

▽CLN Document (Static)

+Episodic Overlay (Dynamic JSON)

◇Personal View (Merged)

---

04//Merge LogicRuntime

// ##eo-merge →Page load: Fetch CLN, then fetch Overlay →Match Overlay IDs to DOM elements →Apply CSS classes (highlights) and inject badges (tags)

---

05//ScopeCognitive

// ##eo-plus + Externalizes Episodic Memory + Allows "reading back in time" — seeing what you saw before + Creates a "Personal Schema" over shared knowledge // ##eo-open ? How to export/share an Overlay? ? Conflict resolution: What if the source CLN IDs change?