6. Glossary — the words that trip people up
From the Meridians Wiki · Public · Maintained · joint
| Term | Precise meaning |
|---|---|
| the record | the canonical on-disk store (.meridians-local/record/). The source of truth. |
| projection / cache | IndexedDB — a rebuildable view of the record. Never authoritative. |
| master | the sovereign instance that owns its record (localhost / Electron / canonical web). |
| client | a joined instance reached over a tunnel; renders synced state, holds no credentials. (Retired synonym: "clone".) |
| the reducer | the single, pure (document, action) → document writer. Shared browser+node. |
applyLocalMutation | the one write path on the backend (gate → reduce → persist → echo). |
mirror (record-mirror) | the renderer's write-through that keeps the record current from browser edits. |
| reconcile / catch-up | the safety nets that re-derive the cache from the record when they diverge. |
| daemon | the always-on Node process (Electron host) that owns the record and serves /api/local/*. |
| Tier 0 / 1 / 2 | read queries / reducer actions / effect-operations — the drivable surface (MCP manual). |
| Threads · Streams · Positions | the three opinion layers the record maintains — settled long-horizon opinion (Fate) · present-day action + memory (World) · foresight, a live self-updating read of where the world is heading (Fate, no score). Their sum is the expert's opinion. |
| the Program | the daily maintainer of that opinion — Research → Opinion → Merge → Position on a cadence, manual or autopilot. |
| Feed | the editorial, timestamped record the Program emits — how the expert's opinion evolved, consumable by other people. |
| Public / Private Domain | the evidence and maintenance boundary: current cited web Research vs. deliberately supplied interview context and Reminder Notes; the same engine underneath. |