Parent
docs/issues/unic-archon-dlc/PRD.md
What to build
Second half of the explore workflow: a prototype node that runs structured experiments, an optional human gate for preserving valuable spike code, and a spike ticket in the configured tracker.
In scope:
prototype node appended to .archon/workflows/explore.yaml. Reads findings.md and produces one or more experiments, each emitting a structured verdict — exactly one of:
VALIDATED — approach works as expected, evidence captured.
INVALIDATED — approach failed, reason captured.
PARTIAL — partially works, gaps documented.
- Verdicts and per-experiment notes are written into a
## Spike verdicts section of findings.md (single source of truth — no separate spike file).
- Optional interactive gate after
prototype: asks the user whether the spike produced code worth preserving on a branch. If yes, the workflow creates a spike/<slug> branch with the prototype code committed; if no, the worktree is left clean.
- Spike ticket creation via the tracker adapter (slice 03): a ticket of type
spike, labelled with the configured priority default, linking to docs/workflow/<slug>/findings.md. The ticket records VALIDATED/INVALIDATED/PARTIAL summary in its body so the tracker view is informative.
Out of scope: feeding spike code into plan automatically — plan reads findings.md only, not the branch.
Acceptance criteria
Blocked by
PRD: docs/issues/unic-archon-dlc/PRD.md
Migrated from: docs/issues/unic-archon-dlc/05-explore-prototype-and-spike-gate.md (source removed after migration)
Touched by PRs: #33
Parent
docs/issues/unic-archon-dlc/PRD.mdWhat to build
Second half of the
exploreworkflow: a prototype node that runs structured experiments, an optional human gate for preserving valuable spike code, and a spike ticket in the configured tracker.In scope:
prototypenode appended to.archon/workflows/explore.yaml. Readsfindings.mdand produces one or more experiments, each emitting a structured verdict — exactly one of:VALIDATED— approach works as expected, evidence captured.INVALIDATED— approach failed, reason captured.PARTIAL— partially works, gaps documented.## Spike verdictssection offindings.md(single source of truth — no separate spike file).prototype: asks the user whether the spike produced code worth preserving on a branch. If yes, the workflow creates aspike/<slug>branch with the prototype code committed; if no, the worktree is left clean.spike, labelled with the configured priority default, linking todocs/workflow/<slug>/findings.md. The ticket records VALIDATED/INVALIDATED/PARTIAL summary in its body so the tracker view is informative.Out of scope: feeding spike code into
planautomatically —planreadsfindings.mdonly, not the branch.Acceptance criteria
prototypenode runs aftersynthesizeand writes a## Spike verdictssection tofindings.mdwith at least one experiment carrying exactly one verdict from {VALIDATED, INVALIDATED, PARTIAL}.spike/<slug>branch with a commit; answering "no" leaves no branch behind.spike, body linking tofindings.md, and a one-line verdict summary./unic-dlc-explore <slug>on an existing slug does not duplicate the spike ticket; the existing ticket is updated.Blocked by
PRD:
docs/issues/unic-archon-dlc/PRD.mdMigrated from:
docs/issues/unic-archon-dlc/05-explore-prototype-and-spike-gate.md(source removed after migration)Touched by PRs: #33