chrome lane
Role: Doer. Owns FVS chrome port + FWV v8 doctrine + Disciple Connect alignment plan.
Current session: 409986685276336 Status: active
What chrome owns
- FVS chrome (
studio/src/chrome/) — frame, dock, topbar, vibe-panel, peek-panel - FVW v8 doctrine (
pact/freshvibe-way-v8/) — 29+ sections, app-agnostic - Disciple Connect alignment plan (FWV v8 v8 → DC)
- The Region Schema pact wording (chrome drafted; cards applied)
What chrome does NOT own
- FreshCards substrate (that's cards)
- Refactor contract + extraction engine (that's fvre)
- Cross-Mavis state (that's Helper)
Last known state
- Latest FVS Studio commit:
8c093ef2026-06-22 18:37 — "fix(doctrine): strip FVS-specific names from FVW v8 examples + plan correction" (24 files, 169 swaps; the contamination fix) - Phase 1 (chrome port) shipped: at
90e009f, tagcanonical-studio-v0.2.0 - Phase 4 (FWV v8 contamination cleanup) shipped: at
8c093ef - Plan correction:
studio/.fvs/plans/2026-06-22-disciple-connect-plan-correction.md(new constitutional artifact)
Recent work
- Wrote the FWV v8 contamination cleanup (24 files, 169 swaps). Operator sign-off received via commit push.
- Drafted the Region Schema pact wording that cards applied.
- Owns the "scope-fence" pattern: any FVW v8 alignment plan for a non-FVS app must reference the plan-correction file. B1 (workspace partitioning) is dropped; B2-B5 are defaults; §6 identity contract is added.
Standing
- Active. Wrote
8c093ef2026-06-22 18:37; hasn't been pinged since for new work. - May need to consult chrome on the doctrine layer of docHub (e.g., should docHub have a FWV v8 section? Answer is yes, mirror what chrome does for FVS).
- doctrine lane may spawn off chrome when doctrine work outpaces what chrome can hold.
How to reach
communicate tool, to_session: "409986685276336". Use for: FVS chrome changes, FWV v8 doctrine, Disciple Connect alignment, plan-correction addenda.