Charge — YYYY-MM-DD
Dual profile. This template is for teams under the Epic execution profile — Charge lists Epics, not Forge Sparks. Core Forge teams may keep the Active Sparks table variant (Spark ID, phase, intent); see Epic execution…
Guide · Updated · Source
Template
Template — Copy this file into your project and fill in the sections. Do not edit the blueprint original.
Dual profile. This template is for teams under the Epic execution profile — Charge lists Epics, not Forge Sparks. Core Forge teams may keep the Active Sparks table variant (Spark ID, phase, intent); see Epic execution profile.
Dual wiki (documentation). Under the Epic profile, an Epic is Ready on the Spec Flow board only when OpenSpec validate is green and declared handbook surfaces have fresh local derived HTML (wiki_stale overlay clear). Loopback refresh rebuilds handbooks; Archive ≠ deployed — see Spec Flow board.
Active Epics
| # | id | OpenSpec change | status | actor |
|---|---|---|---|---|
| 1 | planned / in-progress / done / blocked / banked |
|||
| 2 | ||||
| 3 |
Blockers
| Epic | Blocker | Action |
|---|---|---|
Banking decisions
| Epic | Reason banked | Restart context |
|---|---|---|