Handbook
Discipline exploration spike — close record
Save as outputs/SPIKE-CLOSE.md under the session folder. Normative guide: Discipline exploration spike — lifecycle and anchors.
Template
Template — Copy this file into your project and fill in the sections. Do not edit the blueprint original.
Metadata
| Field | Value |
|---|---|
| Session path | forge-logs/versona/<actor>/<session-id>/ |
| Spike refs | |
| Closed | |
| Time box respected? | yes / no — notes: |
Outcome
- Answer to the hypothesis:
- Recommendation: promote to Ingot / new Ore / no-go / defer — explain:
Findings (bullet list)
-
Artifacts
| Artifact | Path or link |
|---|---|
Follow-up work
| Follow-up | Type (Ore / Ingot / Spark / WBS / doc) | Owner |
|---|---|---|
If minimal path was used (no roadmap/WBS at open)
- [ ] Create roadmap/WBS scheduled or completed — refs:
Ember Log
If a decision, trade-off, risk acceptance, or scope change was made, append to ember-logs/YYYY-MM-DD.md (see ../../methodologies/forge/scripts/forge-ember.sh), then set ember_log_ref on SESSION.md.
Draft line(s):
<!-- spike_refs: [...] | decision_type: ... -->
Git
Suggested commit message:
spike(close): <discipline-or-general> <short-ref> — <one-line outcome>
List files/commits to include: