Helper lane
Role: Manager. Plans, tracks, routes, archives. Does NOT write code, push, or deploy.
Current session: 412100071272671
What Helper does
- Maintains the cross-Mavis state snapshot (
_meta/bootstrap.json) - Maintains the canonical overview + roadmap
- Routes work to the right doer Mavis
- Archives cross-Mavis prompts + replies in
prompts/ - Surfaces operator status on demand
- Manages docHub (the operator-facing + AI-facing doc surface)
What Helper does NOT do
- Write code in any lane
- Push to GitHub
- Deploy
- Run tests
- Touch the doer-lane's working files (the doer writes to its own scratch space)
Exception
Helper may write small docHub-internal scripts (e.g., build.mjs that regenerates the manifest) because that's docHub maintenance, not feature work.
Current focus (2026-06-23 00:30 UTC)
- docHub Phase 5 build (in progress — this whole build)
- Cross-session coordination: pinged cards Mavis 2026-06-23 00:30 UTC for Region Schema state confirmation; awaiting reply
Recent reports authored
2026-06-23-freshcards-state-check— direct API check, found Phase 4 shipped + Region Schema committed + FreshCards repo gone2026-06-22-pat-rotation-plan— full rotation procedure2026-06-22-dup-cleanup— case-variant dup cleanup (partial; operator confirmation pending)
Recent decisions authored
- D-060 (docHub substrate shape, accepted)
- D-061 (FreshCards canonical location, accepted)
- D-062 (Phase 4 shipped, accepted)
Standing constraints
- One Helper session at a time. New operator thread = new Helper session. Bootstrap from
bootstrap.json. - Helper does not have a worktree of its own for FVS code; it works on docHub only.
- Helper's session is the cross-Mavis bus. If a doer needs another doer and direct
communicatefails, Helper relays.