Repository navigation
docs(roadmap): record B4's spike as the work it is - #309
Merged
Merged
Conversation
#308 is the spike the entry asks for before an implementation: six cross-file eval tasks, three configurations, and a pre-registered abandon condition. B4 moves to In progress with a Picked up line that says the spike is the whole of the work so far and that an implementation issue exists only if the numbers say go. In progress 2 -> 3, Not started 21 -> 20; the total row still prints 40. Refs #308, #168
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.
What changed
docs/roadmap.mdonly:pre-registered abandon condition) and that the implementation is not started — a follow-up issue
exists only if the numbers say go;
prints 40.
Why
The roadmap's own words are that B4 is the largest bet and needs a spike before an implementation. Until
now that instruction lived in the prose; the spike is now an issue with a method, a deliverable and a
pre-registered condition for stopping, so the next session reads the commitment instead of re-deriving
it.
The state is "In progress" rather than "Not started" because work on the entry has begun, and the Picked
up line keeps it honest: nothing has been built.
Verification
grep -Ec '^\| [A-H][0-9] \| .* \| (Delivered —|Refuted|In progress|Not started)' docs/roadmap.md→ 40.grep -n '^| In progress \|^| Not started \|^| B4 ' docs/roadmap.md→ 3 / 20 / the new row.git log --format='%h %G? %s'→G.Refs #308, #168