control-surface

  action `type` (`entryLane` in activity-analytics — the one lane derivation every surface uses).

## Control surface (the drivable API + MCP)

**Control surface** — the daemon's typed, headless API over the record: **queries** (Tier‑0 reads),
**actions** (Tier‑1 reducer commands — the single-writer mutations), **operations** (Tier‑2
multi‑step effects that stream progress and terminate in actions). It's what makes the app an
almost 1:1 **headless clone** of the UI — anything a user does, an agent or test can drive.

**MCP** — the Model Context Protocol server (`mcp/`) fronting that surface: it **auto‑materialises one
tool per query + per built operation** from the manifest, plus generic escape hatches
(`meridians_query` / `meridians_run_op` / `meridians_dispatch`). Add a query or op → an MCP tool
appears, no wiring. This is the primary way we **validate the whole system in a closed loop** (set up
cycles + Positions, fire the Research phase, read the Stories back — no UI). Coverage is a first‑class

Raw Markdown source