Prototype the dashboard clarity additions #56

Closed
opened 2026-09-10 05:12:27 +00:00 by xavierk · 2 comments
Owner

Parent map: Chart Fenris dashboard clarity

Question

How should the five additions look on screen? Build a cheap mock (headless Textual render or ASCII sketch) of the Panes TUI showing: (1) Header bar reading "Fenris — NVMe endurance monitor"; (2) Bongbetic credit line in the bottom service strip; (3) persistence line such as "monitoring: active in background · persists across reboots"; (4) prominent quit affordance visually distinct from a monitoring-paused banner (Deliberate disable state); (5) one-time launch banner noting privileged actions prompt for authentication (polkit). Placement decisions from charting are fixed; this ticket refines visual presentation to react to. Link the prototype asset from this issue.

Parent map: [Chart Fenris dashboard clarity](https://git.bongbetic.com/xavierk/Fenris/issues/55) ## Question How should the five additions look on screen? Build a cheap mock (headless Textual render or ASCII sketch) of the Panes TUI showing: (1) Header bar reading "Fenris — NVMe endurance monitor"; (2) Bongbetic credit line in the bottom service strip; (3) persistence line such as "monitoring: active in background · persists across reboots"; (4) prominent quit affordance visually distinct from a monitoring-paused banner (Deliberate disable state); (5) one-time launch banner noting privileged actions prompt for authentication (polkit). Placement decisions from charting are fixed; this ticket refines visual presentation to react to. Link the prototype asset from this issue.
xavierk added this to the Wayfinder: Chart Fenris dashboard clarity milestone 2026-09-10 05:12:27 +00:00
xavierk added the wayfinder:prototype label 2026-09-10 05:12:27 +00:00
xavierk added a new dependency 2026-09-10 05:12:45 +00:00
xavierk self-assigned this 2026-09-10 05:29:13 +00:00
Author
Owner

Prototype asset: dashboard clarity variants on branch prototype/dashboard-clarity (commit 482c2ac).

Run: ./prototype/dashboard-clarity/run, then open http://127.0.0.1:8765/prototype/dashboard-clarity/?variant=a.

Three treatments preserve Panes layout while varying visual hierarchy: A Quiet integration, B Labelled rails, C Strong state blocks. Active/paused selector exposes quit-TUI versus Deliberate disable distinction. Awaiting HITL review before resolution.

Prototype asset: [dashboard clarity variants](https://git.bongbetic.com/xavierk/Fenris/src/branch/prototype/dashboard-clarity/prototype/dashboard-clarity/README.md) on branch `prototype/dashboard-clarity` (commit [482c2ac](https://git.bongbetic.com/xavierk/Fenris/commit/482c2ac)). Run: `./prototype/dashboard-clarity/run`, then open `http://127.0.0.1:8765/prototype/dashboard-clarity/?variant=a`. Three treatments preserve Panes layout while varying visual hierarchy: A Quiet integration, B Labelled rails, C Strong state blocks. Active/paused selector exposes quit-TUI versus Deliberate disable distinction. Awaiting HITL review before resolution.
Author
Owner

Resolution

Accepted visual direction:

  • Use A — Quiet integration as base treatment, preserving existing Panes information architecture.
  • Use C — Strong state blocks for monitoring-paused presentation: full-width, high-contrast banner clearly identifying Deliberate disable.
  • Use B — Labelled rails for quit affordance: prominent bordered q · QUIT TUI, visually separate from monitoring state.
  • Render launch authentication notice as A's quiet informational line; it must not compete with drive state.
  • Render persistence as B's labelled CONTINUITY row, providing clear anchor for TUI/CLI parity.
  • Place dimmed Bongbetic credit inline with service facts, not action row.

Prototype source: prototype/dashboard-clarity, commit 482c2ac.

This resolves visual presentation only. Exact wording remains with Lock the dashboard wording strings. No glossary or ADR change required.

## Resolution Accepted visual direction: - Use **A — Quiet integration** as base treatment, preserving existing Panes information architecture. - Use **C — Strong state blocks** for monitoring-paused presentation: full-width, high-contrast banner clearly identifying **Deliberate disable**. - Use **B — Labelled rails** for quit affordance: prominent bordered `q · QUIT TUI`, visually separate from monitoring state. - Render launch authentication notice as A's quiet informational line; it must not compete with drive state. - Render persistence as B's labelled **CONTINUITY** row, providing clear anchor for TUI/CLI parity. - Place dimmed **Bongbetic** credit inline with service facts, not action row. Prototype source: [prototype/dashboard-clarity](https://git.bongbetic.com/xavierk/Fenris/src/branch/prototype/dashboard-clarity/prototype/dashboard-clarity/README.md), commit [482c2ac](https://git.bongbetic.com/xavierk/Fenris/commit/482c2ac). This resolves visual presentation only. Exact wording remains with [Lock the dashboard wording strings](https://git.bongbetic.com/xavierk/Fenris/issues/57). No glossary or ADR change required.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: xavierk/Fenris#56