Repository navigation
docs: the verb rule — pack operations bind to the pack, not the screen - #171
Merged
Merged
Conversation
Design proposal answering the maintainer's 2026-10-19 question (why can dashboards only be exported from a Build pack, not from Diagnose). It generalises the deploy modal's existing behaviour into a rule: journeys order verbs, never gate them; one verb, one canonical flow; an unavailable verb says why. Includes the verb inventory on today's code, three view-layer slices, and three owner decisions. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
A design proposal,
docs/PACK_OPERATIONS.md. Nothing is built; no code changes.Why
The maintainer's 2026-10-19 question: why can I only export dashboards from the Build pack? why not from Diagnose? some functions should always be available. The audit behind the doc found the pattern: a verb implemented as a stage of the journey that first needed it stayed welded to that journey's screen — per-artefact export of compiled files exists only for a Build draft (
studio/app.mjs:4484), so a registered pack of any origin has no way to yield a single compiled dashboard anywhere in the studio.The proposal
studio/compare-view.mjs:1561); the static bundle draws it unavailable with the reason.develop).It extends
UX_SCREEN_GRAMMAR.md's "pack operations" section and framesUPDATE_JOURNEY.md'supdatebutton as the first verb designed under the rule.Reviewer notes
npm run lint/npm testuntouched surface;tools/test-doc-test-totals.mjspasses (the new doc carries noTests:chains).developper the branch contract in AGENTS.md.🤖 Generated with Claude Code