Graph spine: shorter step names and conditions #546

Closed
opened 2026-11-15 13:26:45 -05:00 by cmoriarty · 2 comments
Owner

Follow-up to braid#190 (the graph spine).

What happens

The spine's step names and their conditions are long. In the side-by-side cards they wrap onto three or four lines, so the graph reads like a list of sentences. Some examples:

  • "Visual check: use and look at the result as a person would"
  • "Confirm the tests and the visual check passed"
  • "List the pieces of work, and file them as issues", with "only if the run asked for tracking"
  • "Fix what the tests or the visual check found", with "only if a check fails"

Fix

Shorten every name in ui/src/lib/steps.ts (PURPOSE) and every condition in ui/src/lib/conditions.ts so each still says the same thing. Aim for about three words, as in "Visual check", "Confirm checks passed", "File issues" with "if tracking", and "Fix failures" with "if a check fails". The node id stays underneath as it is now.

Done when

At 1440 px no step name or condition wraps in a half-width card, and every name keeps its meaning. A mock of the new wording is approved first.

Follow-up to braid#190 (the graph spine). ## What happens The spine's step names and their conditions are long. In the side-by-side cards they wrap onto three or four lines, so the graph reads like a list of sentences. Some examples: - "Visual check: use and look at the result as a person would" - "Confirm the tests and the visual check passed" - "List the pieces of work, and file them as issues", with "only if the run asked for tracking" - "Fix what the tests or the visual check found", with "only if a check fails" ## Fix Shorten every name in `ui/src/lib/steps.ts` (`PURPOSE`) and every condition in `ui/src/lib/conditions.ts` so each still says the same thing. Aim for about three words, as in "Visual check", "Confirm checks passed", "File issues" with "if tracking", and "Fix failures" with "if a check fails". The node id stays underneath as it is now. ## Done when At 1440 px no step name or condition wraps in a half-width card, and every name keeps its meaning. A mock of the new wording is approved first.
Author
Owner

The owner approved the wording tables in the proposal console-fixes-and-session-cap (design.md, "#546: the wording, for approval") on 2026-11-15: "Approved, apply it". The words are built as tabled. Any that still wraps at 1440 px is shortened and noted here.

The owner approved the wording tables in the proposal `console-fixes-and-session-cap` (design.md, "#546: the wording, for approval") on 2026-11-15: "Approved, apply it". The words are built as tabled. Any that still wraps at 1440 px is shortened and noted here.
Author
Owner

Every step purpose and condition is now about three words, from the table approved above, and conditions lose their only. On the local try the owner asked for one more thing: task groups go by their plan's heading in the transcript and the Stop dialog too, not "Implement group N", and the tasks rules ask for each heading in about three words.

Evidence: measured at 1440 px on every box of a seeded thorough run, no name or condition wraps, half-width boxes included. The only exceptions are plan titles from that old seed. Vitests cover the titles and the group names.

Shipped in pull request 550 (merge 3bed64d), change console-fixes-and-session-cap, archived in pull request 551.

Every step purpose and condition is now about three words, from the table approved above, and conditions lose their `only`. On the local try the owner asked for one more thing: task groups go by their plan's heading in the transcript and the Stop dialog too, not "Implement group N", and the tasks rules ask for each heading in about three words. Evidence: measured at 1440 px on every box of a seeded thorough run, no name or condition wraps, half-width boxes included. The only exceptions are plan titles from that old seed. Vitests cover the titles and the group names. Shipped in pull request 550 (merge `3bed64d`), change `console-fixes-and-session-cap`, archived in pull request 551.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#546
No description provided.