docs(promise-map): promise IDs and the plan for promise-linked work - #250
Merged
Conversation
… a promise Signed-off-by: Jared Scott <jared.scott@variable.team>
Signed-off-by: Jared Scott <jared.scott@variable.team>
Signed-off-by: Jared Scott <jared.scott@variable.team>
Contributor
CoverageThreshold: |
5 tasks
gcko
force-pushed
the
docs/promise-linked-work-plan
branch
from
September 2, 2026 06:19
4e3e1f1 to
4791594
Compare
This was referenced Sep 2, 2026
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
The spec and implementation plan for linking every unit of roadmap work to one of the five promises in
docs/promise-map.md, plus the first work package: each promise heading now carries an ID (P1toP5) and the map gains a section, "How work links to a promise", that defines the ID table and the move taxonomy (keep,sharpen,extend,new,none). Every later change links to that section rather than restating it.Background: CL's ask on the 0.20 release thread for the journey map to describe user value reached the publishing surfaces but not the machinery that selects and accepts work. The spec (
docs/plans/promise-linked-work.md) says why and what changes; the plan (docs/plans/promise-linked-work-implementation.md) carries the eight tasks. Both are transient plan docs and are deleted when the work ships.Verification
python3 scripts/validate_plugins.pypasses on every commit. The diff is prose only, so per AGENTS.md that is the check that matters, and it resolves the new heading anchors.Notes
Tasks 2 to 6 follow as one stacked PR based on this branch. Tasks 7 and 8 are Linear-only.
🤖 Generated with Claude Code