Repository navigation
docs(archetypes): the sequential table records the plan we now keep - #72
Merged
Merged
Conversation
The sequential archetype is where planning belongs, and #40 changed its answer: a run can now keep an ordered, re-planned plan (`PlanStep`) that is read back from the record. The table said nothing about it, so "no pipeline definition anywhere in `src/`" was left to speak for the whole row set — true of execution, misleading about what we *do* record. - A **partial** row: `PlanStep` (`src/steps.ts`, `--plan-interval`) records an ordered plan and re-plans from `getSteps`, but it steers the model rather than being executed step by step. The half that exists and the half that does not are now both visible. - The "observe → recommend" asymmetry paragraph and gap 1 say which half is which: observe and record exist since #40; promote and replay do not. That sharpens the gap rather than softening it. Verified with `pnpm test` (324 passed; `src/docs.test.ts` checks that every cited path resolves) and prettier on the touched file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs(archetypes): the sequential table records the plan we now keep
The sequential archetype is where planning belongs, and #40 changed its answer:
a run can now keep an ordered, re-planned plan (
PlanStep) that is read back fromthe record. The table said nothing about it, so "no pipeline definition anywhere in
src/" was left to speak for the whole row set — true of execution, misleadingabout what we do record.
PlanStep(src/steps.ts,--plan-interval) records anordered plan and re-plans from
getSteps, but it steers the model rather thanbeing executed step by step. The half that exists and the half that does not are
now both visible.
observe and record exist since feat: planning passes + typed memory steps #40; promote and replay do not. That sharpens the
gap rather than softening it.
Verified with
pnpm test(324 passed;src/docs.test.tschecks that every citedpath resolves) and prettier on the touched file.