Lane map

The four Mavis sessions + the operator, and what each does.

The roster

Lane	Role	Session ID	What it owns
🟦 Helper	manager	`412100071272671` (this session)	Plans, tracks, routes, archives. docHub steward.
🟠 cards	doer	`404483248046205`	FreshCards substrate, Studio re-alignment, Region Schema pact wording
🟣 chrome	doer	`409986685276336`	FVS chrome port, FVW v8 doctrine, Disciple Connect alignment
🟢 fvre	doer	`408523191824555`	FreshVibe Refactor Contract, Recipe Books, extraction engine, HYBRID-mode gatekeeper
🟪 doctrine	doer	(TBD — not yet spawned)	Reserved for FWV v8 doctrine + pact curation. May share with chrome until needed.

Operator — the cross-Mavis bus. The operator pings Helper for status, relays between lanes, and signs off on decisions that need human authority.

Helper

Owns:

docHub (this substrate)
The overview + roadmap + reports index
Cross-lane coordination
The dev face of docHub (auth-gated)
Operator-facing status reports

Does NOT own:

Code in any lane
Pushes to GitHub
Test runs
Deploys

Current focus (as of 2026-06-23 00:30 UTC):

docHub Phase 5 build (in progress)
Cards Mavis Region Schema state verification (ping sent 00:30 UTC, awaiting reply)

How to reach: in-session. This is the manager thread.

cards

Session ID: 404483248046205 Owns: FreshCards substrate work in FVS Studio

Current state (per last relay 2026-06-22 23:30 UTC):

Phase 3 (FreshCards canonical export) shipped at 349f518 standalone, 43cb74f Studio re-alignment
401/401 tests PASS, vite build green
Parked on: Region Schema pact wording sign-off, awaiting operator

How to reach: communicate tool, to_session: "404483248046205". Use for: FreshCards module work, Studio re-alignment, Region Schema decisions.

chrome

Session ID: 409986685276336 Owns: FVS chrome port + FVW v8 doctrine

Current state (per last relay + API check 2026-06-23):

Phase 1 (chrome port) shipped at 90e009f
Phase 4 (FWV v8 contamination fix) shipped at 8c093ef (24 files, 169 swaps)
Wrote the doctrine contamination cleanup
Drafted the Region Schema wording that cards applied

How to reach: communicate tool, to_session: "409986685276336". Use for: chrome port changes, FVW v8 doctrine, Disciple Connect alignment plans.

fvre

Session ID: 408523191824555 Owns: FreshVibe Refactor Contract, Recipe Books, extraction engine

Current state (per last relay):

Mostly parked
Owns the doctrine fence's HYBRID-mode gatekeeper (when an FVW v8 alignment plan needs HYBRID mode, fvre signs off)
Has not been pinged in this session yet

How to reach: communicate tool, to_session: "408523191824555". Use for: FVW v8 refactor contract questions, HYBRID-mode carve-out decisions, extraction engine work.

doctrine (reserved)

Session ID: TBD Owns: FWV v8 doctrine curation, pact fragment registry

Current state: Not yet spawned. Chrome currently covers doctrine work. Spawn when doctrine work outpaces what chrome can hold.

How to spawn: communicate with spawn: { agent_name: "Coder", title: "doctrine Mavis" } and a doctrine-scoped system prompt.

Operator

Owns:

Final sign-off on constitutional decisions (D-056+)
Cross-Mavis bus (relay between lanes)
Repo-level authority (push, delete, deploy)
Secret rotation (PAT, API tokens)
Workspace canonicalization (which casing is "the" repo)

Does NOT own:

docHub content (Helper does)
Code (doers do)
Day-to-day coordination (Helper does)

How to reach: the human at the keyboard. They see all Mavis threads via the UI.

Cross-lane dependencies (current)

Dependency	From	To	Status
Region Schema pact wording	cards (apply)	chrome (draft)	chrome drafted, cards applied, operator sign-off pending
FreshCards substrate compat	docHub (this)	cards	docHub references `studio/modules/freshcards/module.json`; cards hasn't reviewed yet
FVW v8 doctrine cleanup	chrome	(everyone)	shipped at `8c093ef`
HYBRID-mode gatekeeping	fvre	(per plan)	dormant — no active HYBRID plan
Notion editor import	cards	(TBD)	parked, 6 tasks, 69 .tsx files

What changes when the operator opens a new thread

The operator opens new threads (this one was new on 2026-06-22 23:21 UTC). When that happens:

The new Helper session reads docshub/dev/_meta/bootstrap.json for state.
The new Helper checks the lane map (this file) for who owns what.
The new Helper pings parked lanes if their work is now unblocked.
The new Helper archives the prior session's work via the prompts/ log.

No re-onboarding. The substrate is the bootstrap.