Toilville/toilville-design
Watch
5
1
Fork
You've already forked toilville-design
 0
Code Issues 21 Pull requests Projects Releases Packages Wiki Activity Actions

SPELWork dashboards: assign the six pipeline step colours (spec §4) #172

New issue
Closed
opened 2026-09-28 20:29:23 +00:00 by forge-ci · 4 comments
forge-ci commented 2026-09-28 20:29:23 +00:00
Member
Copy link

Section 4 of spelwork-dashboard-design-part1.md was blocked because the six pipeline step names weren't available.

The repo already has them. 08-primary-execution-pipeline-vertical.svg labels the pipeline:

Wish → Ruse → Ritual → Rubric → Deliverable → Harvest

@peterswimm to confirm these are the six steps the dashboards track.

Acceptance criteria

  • Step names confirmed.
  • Six step colours proposed, light and dark, each passing WCAG AA on its surface. The spec's own rule applies: keep them separate from the six mode accents (observatory, workshop, pilgrimage, sanctum, federation, consentgate), so one colour never means two things.
  • Colours hold up alongside each other and alongside the §3 warning states (see #173).
  • The proposal is written as DTCG entries for Brand/UDG/products/spelwork/dtcg/color.json. It needs Peter's sign-off before merge, because it adds colours to the system.
Section 4 of [`spelwork-dashboard-design-part1.md`](https://git.toilville.dev/Toilville/toilville-design/src/branch/main/Brand/specs/spelwork/spelwork-dashboard-design-part1.md) was **blocked** because the six pipeline step names weren't available. The repo already has them. [`08-primary-execution-pipeline-vertical.svg`](https://git.toilville.dev/Toilville/toilville-design/src/branch/main/Brand/source/infographics/08-primary-execution-pipeline-vertical.svg) labels the pipeline: **Wish → Ruse → Ritual → Rubric → Deliverable → Harvest** @peterswimm to confirm these are the six steps the dashboards track. ## Acceptance criteria - [ ] Step names confirmed. - [ ] Six step colours proposed, light and dark, each passing WCAG AA on its surface. The spec's own rule applies: keep them separate from the six mode accents (observatory, workshop, pilgrimage, sanctum, federation, consentgate), so one colour never means two things. - [ ] Colours hold up alongside each other and alongside the §3 warning states (see #173). - [ ] The proposal is written as DTCG entries for `Brand/UDG/products/spelwork/dtcg/color.json`. It needs Peter's sign-off before merge, because it adds colours to the system.
forge-ci commented 2026-09-28 20:56:49 +00:00
Author
Member
Copy link

Recommendation: use the dimension stages, coloured with one sequential ramp

Steps: Foundation → Intent → Structure → Execution → Scale → Outcome (stages 0–5).

Three candidate sets of six exist. This is the only one the system records: they are the stages in core.dimensions, the rubrics gate on them (rubrics.gate_stage), and each already has house-style art (spel.stage.0–5).

  • Wish · Ruse · Ritual · Rubric · Deliverable · Harvest (the pipeline infographic) is concept wording. Nothing records "Deliverable" or "Harvest" as a state, so there's no data to chart.
  • admit → hydrate → preflight → dispatch → observe → result → closeout (core.execution_stages) are the runtime stages. There are eight counting failure, and failure overlaps the warning states. Use them as an uncoloured timeline inside the task-in-progress dashboard.

Colours: one sequential ramp, not six hues.

The steps are in order, so position, label and icon already identify each one. The usual practice for ordered categories is a single-hue ramp with evenly stepped lightness.

  • Hues run out. Categorical hues stop being distinguishable past about 6–8, and these dashboards already use six mode accents plus the status colours.
  • A lightness ramp works in greyscale and for colour-blind viewers.
  • Build it on the SPELWork brand blue color.brand.primary (#7394C8) and keep it clear of red, amber and green, which belong to status.
  • Always show the stage icon and name with the colour. Colour alone must never carry the meaning (WCAG 1.4.1).

Acceptance criteria, revised

  • Peter confirms the dimension stages are the steps.
  • A six-step lightness ramp on the brand hue, light and dark. Each step clears 3:1 against the chart surface (WCAG 1.4.11), and any text on a step passes AA.
  • Each step pairs its colour with its spel.stage.N icon and name in every chart.
## Recommendation: use the dimension stages, coloured with one sequential ramp **Steps: Foundation → Intent → Structure → Execution → Scale → Outcome** (stages 0–5). Three candidate sets of six exist. This is the only one the system records: they are the stages in `core.dimensions`, the rubrics gate on them (`rubrics.gate_stage`), and each already has house-style art (`spel.stage.0–5`). - **Wish · Ruse · Ritual · Rubric · Deliverable · Harvest** (the pipeline infographic) is concept wording. Nothing records "Deliverable" or "Harvest" as a state, so there's no data to chart. - **admit → hydrate → preflight → dispatch → observe → result → closeout** (`core.execution_stages`) are the runtime stages. There are eight counting `failure`, and `failure` overlaps the warning states. Use them as an uncoloured timeline inside the task-in-progress dashboard. **Colours: one sequential ramp, not six hues.** The steps are in order, so position, label and icon already identify each one. The usual practice for ordered categories is a single-hue ramp with evenly stepped lightness. - **Hues run out.** Categorical hues stop being distinguishable past about 6–8, and these dashboards already use six mode accents plus the status colours. - **A lightness ramp works in greyscale and for colour-blind viewers.** - **Build it on the SPELWork brand blue `color.brand.primary` (`#7394C8`)** and keep it clear of red, amber and green, which belong to status. - **Always show the stage icon and name with the colour.** Colour alone must never carry the meaning (WCAG 1.4.1). ## Acceptance criteria, revised - [ ] Peter confirms the dimension stages are the steps. - [ ] A six-step lightness ramp on the brand hue, light and dark. Each step clears 3:1 against the chart surface (WCAG 1.4.11), and any text on a step passes AA. - [ ] Each step pairs its colour with its `spel.stage.N` icon and name in every chart.
peterswimm commented 2026-10-20 15:09:29 +00:00
Owner
Copy link

Recommendation (2026-10-20), pending my confirmation of the six steps:

Steps: use the dimension stages Foundation, Intent, Structure, Execution, Scale and Outcome, not the infographic names. These are the stages the system records and gates on. Deliverable and Harvest have no data behind them.

Colour: one sequential brand-blue lightness ramp, not six hues. Pair each stage with its icon and name, so colour is never the only signal.

Once I confirm, ville drafts the DTCG entries for review.

**Recommendation (2026-10-20), pending my confirmation of the six steps:** **Steps:** use the dimension stages Foundation, Intent, Structure, Execution, Scale and Outcome, not the infographic names. These are the stages the system records and gates on. Deliverable and Harvest have no data behind them. **Colour:** one sequential brand-blue lightness ramp, not six hues. Pair each stage with its icon and name, so colour is never the only signal. Once I confirm, ville drafts the DTCG entries for review.
peterswimm commented 2026-10-21 23:42:09 +00:00
Owner
Copy link

Confirmed (Peter, 2026-10-21).

  • Steps: the dimension stages Foundation, Intent, Structure, Execution, Scale and Outcome.
  • Colour: one sequential brand-blue lightness ramp. Each stage also has its icon and name, so colour is never the only signal.

@ville, over to you: draft the DTCG entries for review. The colour-blind check in #173 then runs against this ramp.

**Confirmed (Peter, 2026-10-21).** - **Steps:** the dimension stages Foundation, Intent, Structure, Execution, Scale and Outcome. - **Colour:** one sequential brand-blue lightness ramp. Each stage also has its icon and name, so colour is never the only signal. @ville, over to you: draft the DTCG entries for review. The colour-blind check in #173 then runs against this ramp.
peterswimm commented 2026-10-27 23:06:59 +00:00
Owner
Copy link

Signing off on the stage tokens. Closing.

The decision was made 2026-10-21 — the six dimension stages (Foundation, Intent, Structure, Execution, Scale, Outcome) rather than the infographic's pipeline names, on one sequential brand-blue lightness ramp, with the icon and name always travelling with the colour. #226 shipped exactly that: color.stage.0 to .5 in the baseline and the SPELWork palette, extract.py aliases, 18 non-text 3:1 pairs in wcag.py.

§4 now carries the full table. Contrast against the surface rises at every step in both themes, so the ramp is readable as an ordering and not only as six colours.

Two stale things worth naming rather than leaving:

  • §4 still says the tokens are "drafted for his sign-off" and the open-questions list still says they "need Peter's sign-off before merge". The merge already happened in #226. This comment is that sign-off, retroactively.
  • The two token questions §4 genuinely leaves open — SPELWork's dark stage values, and whether text on a stage fill needs on-colour tokens — are carried to #234 so they do not close with this issue.
**Signing off on the stage tokens. Closing.** The decision was made 2026-10-21 — the six dimension stages (Foundation, Intent, Structure, Execution, Scale, Outcome) rather than the infographic's pipeline names, on one sequential brand-blue lightness ramp, with the icon and name always travelling with the colour. #226 shipped exactly that: `color.stage.0` to `.5` in the baseline and the SPELWork palette, `extract.py` aliases, 18 non-text 3:1 pairs in `wcag.py`. §4 now carries the full table. Contrast against the surface rises at every step in both themes, so the ramp is readable as an ordering and not only as six colours. Two stale things worth naming rather than leaving: - §4 still says the tokens are *"drafted for his sign-off"* and the open-questions list still says they *"need Peter's sign-off before merge"*. The merge already happened in #226. **This comment is that sign-off**, retroactively. - The two token questions §4 genuinely leaves open — SPELWork's dark stage values, and whether text on a stage fill needs on-colour tokens — are carried to #234 so they do not close with this issue.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
archive/ds-bundle-snapshot-20261007
archive/design-system-superset-20260628
Labels
Clear labels   
build-dist
Ask the UDG build bot to run just build and commit generated files to this PR

  
priority
P1
 Urgent — no working icon yet (custom art pending) or a shipping asset

  
priority
P2
 High — has an accessible stand-in; bespoke art wanted

  
priority
P3
 Medium — stage visual headers

  
priority
P4
 Low — behavioral dimension family

  
bug
Something is not working

  
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
help wanted
Need some help

  
invalid
Something is wrong

  
question
More information is needed

  
wontfix
This won't be fixed

No labels
build-dist
priority
P1
priority
P2
priority
P3
priority
P4
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
ville
peterswimm
2 participants
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
Toilville/toilville-design#172
No description provided.