docs(spelwork): Part 2 — sketches for the three §6 dashboards #224

Merged
peterswimm merged 2 commits from feat/171-dashboard-sketches-part2 into main 2026-10-22 14:43:08 +00:00
Member

Refs #171, #172, #174. Closes nothing.

Scope

Adds the Part 2 deliverable for the three §6 dashboards. Four new files, no edits to existing files:

  • Brand/specs/spelwork/spelwork-dashboard-design-part2.md
  • Brand/specs/spelwork/spelwork-dashboard-part2/worker-health.png
  • Brand/specs/spelwork/spelwork-dashboard-part2/task-in-progress.png
  • Brand/specs/spelwork/spelwork-dashboard-part2/system-wide-problems.png

Part 1 left §6 at "not started", blocked behind §3 (warning states) and §4 (step names). Both are now decided, and the sketches follow the decisions:

  • #174 (approved 2026-10-21): four severity levels plus a separate stale state. fine = color.accent.success, slow = color.accent.warning, broken = color.accent.error, very serious = color.accent.critical (new). old is the stale, data-freshness state, on a neutral in color.neutral.warm-* (new), outside the severity ladder. color.safety.* stays rejected for worker health.
  • #172 (confirmed 2026-10-21): the six steps are Foundation, Intent, Structure, Execution, Scale, Outcome, identified by spel.stage.0 to spel.stage.5. The step colour is one sequential brand-blue lightness ramp.

No token values are drafted yet. color.accent.critical, the stale-neutral token (its exact name is not decided) and the step ramp still need to be drafted, so the sketches draw no severity or step colour and name each missing token on the figure. System-wide problems is built on AttentionSummary, which ships, and carries no invented metric.

Screenprint is exploratory, not an approved production dashboard theme. The language is still being developed, and the dashboards may not use it at all. The figures settle the information architecture, content hierarchy, semantic separation and contract-backed data usage. Open dependencies are listed in §5 of the document.

Testing

Documentation and images only. No code, tokens or generated files change, so just build and just check have nothing new to verify. Review the document and the three figures.

Impact Statement

No effect on tokens, dist/ or any consumer. This gives #171 a reviewable starting point and records what #172 and #174 still need to supply before the sketches can use final colours.

Refs #171, #172, #174. Closes nothing. ## Scope Adds the Part 2 deliverable for the three §6 dashboards. Four new files, no edits to existing files: - `Brand/specs/spelwork/spelwork-dashboard-design-part2.md` - `Brand/specs/spelwork/spelwork-dashboard-part2/worker-health.png` - `Brand/specs/spelwork/spelwork-dashboard-part2/task-in-progress.png` - `Brand/specs/spelwork/spelwork-dashboard-part2/system-wide-problems.png` Part 1 left §6 at "not started", blocked behind §3 (warning states) and §4 (step names). Both are now decided, and the sketches follow the decisions: - **#174 (approved 2026-10-21):** four severity levels plus a separate stale state. fine = `color.accent.success`, slow = `color.accent.warning`, broken = `color.accent.error`, very serious = `color.accent.critical` (new). `old` is the stale, data-freshness state, on a neutral in `color.neutral.warm-*` (new), outside the severity ladder. `color.safety.*` stays rejected for worker health. - **#172 (confirmed 2026-10-21):** the six steps are Foundation, Intent, Structure, Execution, Scale, Outcome, identified by `spel.stage.0` to `spel.stage.5`. The step colour is one sequential brand-blue lightness ramp. No token values are drafted yet. `color.accent.critical`, the stale-neutral token (its exact name is not decided) and the step ramp still need to be drafted, so the sketches draw no severity or step colour and name each missing token on the figure. System-wide problems is built on `AttentionSummary`, which ships, and carries no invented metric. Screenprint is exploratory, not an approved production dashboard theme. The language is still being developed, and the dashboards may not use it at all. The figures settle the information architecture, content hierarchy, semantic separation and contract-backed data usage. Open dependencies are listed in §5 of the document. ## Testing Documentation and images only. No code, tokens or generated files change, so `just build` and `just check` have nothing new to verify. Review the document and the three figures. ## Impact Statement No effect on tokens, `dist/` or any consumer. This gives #171 a reviewable starting point and records what #172 and #174 still need to supply before the sketches can use final colours.
docs(spelwork): Part 2 — sketches for the three §6 dashboards
All checks were successful
PR policy check / policy-gate (pull_request) Successful in 0s
Test Generator / lint-workflows (pull_request) Successful in 38s
Security Scans / Gitleaks secret scan (pull_request) Successful in 39s
Security Scans / Trivy filesystem scan (pull_request) Successful in 40s
UDG dist drift gate / dist/ matches dtcg + udg sources (pull_request) Successful in 17s
Test Generator / lint-prose (pull_request) Successful in 27s
Block Validation / validate (pull_request) Successful in 1m22s
Copy coverage / Design copy reaching rendered HTML (pull_request) Successful in 46s
Test Generator / test (pull_request) Successful in 4m4s
2fd10a679c
Part 1 left §6 at "not started", blocked behind §3 (the five warning
states) and §4 (the six step names). Both are still unresolved, so each
sketch is drawn to read without the thing it is missing, and names the
missing thing on its own face.

Worker health uses no severity colour: the five color.severity.* tokens
do not exist, and the §3 proposal to reuse color.safety.* is withdrawn
because worker health is not governance. A task in progress uses
placeholder step names. System-wide problems is built on
AttentionSummary, which ships, and carries no invented metric.

The Screenprint treatment is exploratory, not an approved production
theme. The information architecture, content hierarchy, semantic
separation and contract-backed data usage are what the figures settle.

Closes nothing. Fourteen dependencies are recorded, not solved.

Refs: toilville-design#171, #172
docs(spelwork): align dashboard sketches with #172 and #174
All checks were successful
Test Generator / lint-workflows (pull_request) Successful in 38s
UDG dist drift gate / dist/ matches dtcg + udg sources (pull_request) Successful in 31s
Security Scans / Gitleaks secret scan (pull_request) Successful in 40s
Security Scans / Trivy filesystem scan (pull_request) Successful in 40s
PR policy check / policy-gate (pull_request) Successful in 0s
Test Generator / lint-prose (pull_request) Successful in 44s
Copy coverage / Design copy reaching rendered HTML (pull_request) Successful in 57s
Block Validation / validate (pull_request) Successful in 1m13s
Test Generator / test (pull_request) Successful in 4m8s
712773ab63
#174 (approved 2026-10-21) replaces the provisional color.severity.*
namespace: four severity levels map to color.accent.success, .warning,
.error and the new .critical, and old becomes a separate stale state on
color.neutral.warm-*. color.safety.* stays rejected for worker health.

#172 (confirmed 2026-10-21) fixes the six steps (Foundation, Intent,
Structure, Execution, Scale, Outcome), identified by spel.stage.0 to
spel.stage.5, with one sequential brand-blue ramp.

Worker health and A task in progress are re-rendered. No token values
are drafted: color.accent.critical, the stale-neutral token and the
step ramp are still to be written.

Refs: toilville-design#171, #172, #174
peterswimm deleted branch feat/171-dashboard-sketches-part2 2026-10-22 14:43:08 +00:00
Sign in to join this conversation.
No description provided.