Handbook
Discipline exploration spike — open checklist
Copy into forge-logs/versona/
Template
Template — Copy this file into your project and fill in the sections. Do not edit the blueprint original.
Identity
| Field | Value |
|---|---|
| Spike label / refs | |
work_item_kind (session frontmatter) |
spike_discipline / spike_general |
Owning discipline (if spike_discipline) |
|
| Owner (human) | |
| Started | |
| Time box (end or duration) |
Hypothesis and scope
- Question we must answer:
- In scope:
- Out of scope:
- Success criteria (how we know we’re done):
Anchors
| Anchor | Path or id (or “n/a”) |
|---|---|
| Product / initiative | |
docs/ROADMAP.md |
|
docs/requirements/WBS (or tracker) |
|
| Forge Ore / Ingot / Spark |
If docs/ROADMAP.md or docs/requirements/WBS is missing
Choose one:
- [ ] Preferred: Run
@versona-project-setupif repo/Forge layout is incomplete, then@forge-product-manager/ Product bootstrap flow — from zero to first Charge Steps 6–7 (or Charge — Product Bootstrap (F1) roadmap/WBS Sparks), then return here with ids. - [ ] Minimal: Proceed with product name + Ore (or prose) + hypothesis only; close record must list follow-up to create roadmap/WBS (see DISCIPLINE-SPIKE.md §5).
Optional session frontmatter (YAML)
If useful, set on SESSION.md (see VERSONA-FRAMEWORK.md §7.4):
spike_timeboxspike_hypothesisanchor_notes
Versona / review plan
- [ ] Discipline Versona at close (which):
- [ ] Routing Versona (
versona-all) before close: yes / no