Skip to content

prose(experiment): the phase joins discovery, research, discussion, and the epic flow - #1062

Closed
leeovery wants to merge 7 commits into
feat/experiment-phase-skillsfrom
feat/experiment-phase-integration
Closed

prose(experiment): the phase joins discovery, research, discussion, and the epic flow#1062
leeovery wants to merge 7 commits into
feat/experiment-phase-skillsfrom
feat/experiment-phase-integration

Conversation

@leeovery

Copy link
Copy Markdown
Owner

PR4 of the experiment-phase stack (design: #1057, stacks on #1061).

  • Discovery: routing is genuinely three-way — "do we answer this by reading, by talking, or by measuring?" — across the shaping flow, curation, map operations, and the cue lists (with the collected-hands-on-numbers cue). The feature/cross-cutting first-phase choice is the engine-rendered first-phase-gate.
  • Research: the conclude gate gains e/experiment — the needs-measuring arm. Research concludes normally (completed, indexed, committed), then routes straight into /workflow-experiment-entry with context hot.
  • Discussion: J. The Empirical Wall — the engine-rendered experiment-exit-gate asks; on yes the point is documented as waiting, the discussion commits, and the session exits into the experiment design. The walk's first conceive records the engine-side wait (createawait → one commit; the unrecorded window is one tool call, and the pre-await crash state is benign). Re-entry surfaces evidence via reconcile-advisory.md's new experiment branch (register + reports read in full, abandonments with reasons); the conclude flow checks the wait first and the engine refusal backstops.
  • Epic menu: x/experiment (new_experiment) joins the command rows; cancel flow names the wait-release confirm and reads released_wait.
  • Bridge + sweep: continuation phase lines, triage-landing three-way landing judgment, entry-skill pipeline tables, roadmap pull enum. complexity-check's promotion menu migrated to the engine (complexity-gate) under the touch-adopts-menus rule.
  • Requeue deliberately stays a research↔discussion pair — no flow produces an experiment requeue; the landing judgment aims concerns up front and the experiment fold absorbs mis-landings.

Gates: npm test 2676/2676 · npm run test:cli 5/5 · npm run typecheck clean · simulation extended (conclude-spawn, exit ordering, epic x-row); no snapshot goldens moved.

🤖 Generated with Claude Code

leeovery and others added 7 commits August 30, 2026 19:59
…ow, exit gate, first-phase gate, epic menu command

The research conclude gate carries e/experiment always — conclude, then
route into the same-topic experiments. The discussion's empirical wall
gets its consent gate (experiment-exit-gate), the single-phase first-
phase choice becomes an engine menu (first-phase-gate, three-way), and
the epic menu gains x/experiment beside d/discuss and r/research
(new_experiment rides the soft-gate action list). Simulation covers the
research-conclude spawn, the exit's create+await commit ordering, and
the menu-born experiment topic.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…r measure

Routing inference, first-phase routing, topic synthesis, map operations,
the session-loop and harvest enums, brief propagation, and the detection
core all speak the three-way vocabulary; the first-phase choice (and the
quick-fix promotion's twin in scoping) render through the new engine
gates, adopting complexity-check's prose menus on the way.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…o the same-topic experiments

Topic-completion judges the hypothesis question and the new gate row
carries it: research concludes normally (completed, indexed, committed)
then routes straight into /workflow-experiment-entry with context hot —
no bridge, no context clear. Guidelines name the exploratory-sighting
boundary; the research and discussion entry tables gain the Experiment
slot.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… into the design, evidence at re-entry

The session gains J. The Empirical Wall (engine-gated, the user's call):
the waiting point is documented and committed, then the session exits
straight into /workflow-experiment-entry with the point riding the
handoff's Spawned from line; the walk's first conceive records the
evidence wait, create and await landing in one commit. G checks the
live wait before the ceremony and states plainly what still waits; the
conclude flow surfaces the engine's refusal verbatim. The reconcile
advisory gains the experiment branch — register rendered, concluded
reports read in full, abandonments surfaced with their reasons.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…way triage landing, roadmap pull enum

The epic menu's cancel flow names the wait-release path beside the spec
collapse and reads released_wait on the receipt; the feature and
cross-cutting continuations carry the (Experiment) slot; triage-landing
judges a measurable question experiment-side and reactivates across all
three phases; the roadmap pull-forward enum widens. topic requeue stays
the research↔discussion pair — no flow here produces a requeue into or
out of experiment.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@leeovery

Copy link
Copy Markdown
Owner Author

Closed: this stack implements a superseded model of the experiment phase. The corrected design is PR #1057 (design/experiment-phase.md) — experiment as an umbrella tool spawned from research/discussion, not a peer pipeline phase. A fresh stack built against that design replaces this one. The branch is kept for salvage until the replacement lands.

@leeovery leeovery closed this Aug 31, 2026
@leeovery
leeovery deleted the feat/experiment-phase-integration branch September 1, 2026 17:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant