Handbook
M2-lite — Lenses control plane (Self-Host overlap)
Scope split with SELFHOST-ALPHA
- M2-lite (this sprint): Studio read surfaces for ForgeRun / EvidencePacket / approval / placeholders, consistent IA and copy (
docs/product-boundaries.md). - SELFHOST-ALPHA (
sprints/selfhost-alpha/):.forge/runs/store, allowlisted local runner, EvidencePacket importer, andforge-runsJSON API implemented in forge-lenses.
Active stories (M2-lite)
- ForgeRun detail IA for file-backed runs (shared route with Self-Host).
- Evidence + approval panels using fixtures from
sprints/selfhost-alpha/samples/. - Decision state transitions documented; optional POST behind the same loopback gates as other Lenses mutating APIs.
Active Sparks
- SPARK-LENSES-SELFHOST-HANDOFF (shared with Self-Host epic).
- UX copy review for “local runner” vs “Fleet placeholder” labels.
Human gates
- No implication that Hermes or chat approves execution.
- Lenses remains system-of-record visibility; Blueprints remain policy, not runtime state.
Evidence links
../selfhost-alpha/evidence/lenses-selfhost-handoff.md