Execution Transparency Dashboard
Build dashboards that answer operator questions, reveal drift between intended and actual execution, and shorten the time from anomaly to corrective action.
When to Use
- Building internal dashboards for workflow runtimes, migrations, multi-agent systems, or refactors.
- Exposing authority drift, verifier status, backlog burn-down, runtime health, or user-visible failure patterns.
- Replacing ad hoc status spreadsheets with a source-of-truth operator surface.
- Designing a panel set where every chart must map to a specific operator decision.
NOT for
- Marketing, growth, or executive KPI dashboards whose value is narrative rather than intervention.
- One-off exploratory charts with no owner, threshold, or follow-up action.
- Duplicate reporting for product analytics that already has a stable home.
- Full UI implementation details for internal tooling chrome. Use
admin-dashboard when the shell and controls are the hard part.
Decision Points
- Start with operator questions, not available metrics. If nobody can act on the panel, cut it.
- Separate live runtime truth from planned work. Mixing them produces false confidence.
- Prefer status panels that expose blocked edges, drift, or unverified states over vanity totals.
- Add drill-down only when operators need to localize a failure boundary, not just admire the aggregate.
- Make freshness explicit whenever a panel can lag behind the underlying runtime.
flowchart TD
A[Need transparency dashboard] --> B{What operator question matters most?}
B -->|Authority mismatch| C[Authority Drift panel]
B -->|Migration progress| D[Legacy Burn-Down panel]
B -->|Execution trust| E[Verification Matrix]
B -->|User-visible failure| F[User Pain Register]
C --> G[Map each metric to a concrete source of truth]
D --> G
E --> G
F --> G
G --> H[Ship only if the panel changes operator behavior]
Failure Modes
- Dashboard theater. Symptom: attractive panels with no linked operator action. Recovery: attach an owner and decision threshold to each panel or delete it.
- Drifted truth. Symptom: the dashboard summarizes a shadow data source instead of the runtime contract. Recovery: trace every metric to one authoritative source.
- Mixed horizons. Symptom: planned work and live state appear identical. Recovery: visually distinguish forecast, backlog, and verified runtime facts.
- Hidden staleness. Symptom: operators act on outdated data because freshness is invisible. Recovery: display timestamps and refresh mechanics directly in the panel.
- Metric sprawl. Symptom: dozens of weak charts dilute attention. Recovery: keep only the panels tied to intervention, escalation, or rollout confidence.
Worked Example
Need: build a migration dashboard for moving a workflow engine from frontend-simulated execution to backend authority.
- Create an
Authority Drift panel showing how many flows still depend on frontend-only transitions.
- Add a
Legacy Burn-Down panel for compatibility shims, dual-path adapters, and remaining migration blockers.
- Add a
Verification Matrix panel that distinguishes tested, untested, and failing subsystems.
- Track a
User Pain Register for incidents the migration is meant to eliminate, not just internal technical milestones.
- Expose freshness timestamps and drill-down links so operators can move from red panel to exact failing boundary.
The expert move is treating the dashboard as an operational contract, not a decorative readout.
Quality Gates
Anti-Patterns and Shibboleths
- "If the data exists, it deserves a chart." Wrong. Operators need intervention surfaces, not metric hoarding.
- "A migration dashboard should mostly show percent complete." Weak. Experts track drift, blocked edges, and unverified seams because those predict rollout risk.
Reference Map
references/INDEX.md
references/dashboard-panels.md
1---2name: execution-transparency-dashboard3description: Design dashboards for migrations and runtimes. Use for authority drift, verifier status, burn-down, runtime health, or pain panels. NOT for vanity analytics, ad hoc charts, or duplicate reporting.4license: Apache-2.05allowed-tools:6 - Read7 - Write8 - Edit9 - Grep10 - Glob11 - Bash(rg *)12 - Bash(cat *)13 - Bash(sed *)14metadata:15 source: https://skillmd.com/skills/curiositech/execution-transparency-dashboard16 category: Operations17 tags:18 - dashboard19 - transparency20 - observability21 - migration22 - runtime23 - evaluation24 pairs-with:25 - skill: data-viz-202526 reason: Good dashboards still need legible, information-dense visual treatment.27 - skill: admin-dashboard28 reason: Internal operator surfaces need the right interaction model and controls.29 - skill: technical-writer30 reason: Dashboards need explicit panel questions, metrics, and action semantics.31 runtime:32 user-invocable: true33 provenance:34 kind: first-party35 owners:36 - some-claude-skills37 authorship:38 maintainers:39 - some-claude-skills40---4142# Execution Transparency Dashboard4344Build dashboards that answer operator questions, reveal drift between intended and actual execution, and shorten the time from anomaly to corrective action.4546## When to Use4748- Building internal dashboards for workflow runtimes, migrations, multi-agent systems, or refactors.49- Exposing authority drift, verifier status, backlog burn-down, runtime health, or user-visible failure patterns.50- Replacing ad hoc status spreadsheets with a source-of-truth operator surface.51- Designing a panel set where every chart must map to a specific operator decision.5253## NOT for5455- Marketing, growth, or executive KPI dashboards whose value is narrative rather than intervention.56- One-off exploratory charts with no owner, threshold, or follow-up action.57- Duplicate reporting for product analytics that already has a stable home.58- Full UI implementation details for internal tooling chrome. Use `admin-dashboard` when the shell and controls are the hard part.5960## Decision Points6162- Start with operator questions, not available metrics. If nobody can act on the panel, cut it.63- Separate live runtime truth from planned work. Mixing them produces false confidence.64- Prefer status panels that expose blocked edges, drift, or unverified states over vanity totals.65- Add drill-down only when operators need to localize a failure boundary, not just admire the aggregate.66- Make freshness explicit whenever a panel can lag behind the underlying runtime.6768```mermaid69flowchart TD70 A[Need transparency dashboard] --> B{What operator question matters most?}71 B -->|Authority mismatch| C[Authority Drift panel]72 B -->|Migration progress| D[Legacy Burn-Down panel]73 B -->|Execution trust| E[Verification Matrix]74 B -->|User-visible failure| F[User Pain Register]75 C --> G[Map each metric to a concrete source of truth]76 D --> G77 E --> G78 F --> G79 G --> H[Ship only if the panel changes operator behavior]80```8182## Failure Modes8384- Dashboard theater. Symptom: attractive panels with no linked operator action. Recovery: attach an owner and decision threshold to each panel or delete it.85- Drifted truth. Symptom: the dashboard summarizes a shadow data source instead of the runtime contract. Recovery: trace every metric to one authoritative source.86- Mixed horizons. Symptom: planned work and live state appear identical. Recovery: visually distinguish forecast, backlog, and verified runtime facts.87- Hidden staleness. Symptom: operators act on outdated data because freshness is invisible. Recovery: display timestamps and refresh mechanics directly in the panel.88- Metric sprawl. Symptom: dozens of weak charts dilute attention. Recovery: keep only the panels tied to intervention, escalation, or rollout confidence.8990## Worked Example9192Need: build a migration dashboard for moving a workflow engine from frontend-simulated execution to backend authority.93941. Create an `Authority Drift` panel showing how many flows still depend on frontend-only transitions.952. Add a `Legacy Burn-Down` panel for compatibility shims, dual-path adapters, and remaining migration blockers.963. Add a `Verification Matrix` panel that distinguishes tested, untested, and failing subsystems.974. Track a `User Pain Register` for incidents the migration is meant to eliminate, not just internal technical milestones.985. Expose freshness timestamps and drill-down links so operators can move from red panel to exact failing boundary.99100The expert move is treating the dashboard as an operational contract, not a decorative readout.101102## Quality Gates103104- [ ] Every panel is framed as an operator question.105- [ ] Every metric resolves to an authoritative source of truth.106- [ ] Planned, inferred, and verified states are visually distinct.107- [ ] Freshness and sampling cadence are visible.108- [ ] A red state implies a concrete next action or escalation path.109- [ ] Drill-down paths localize the failure boundary without requiring raw-log spelunking for common cases.110111## Anti-Patterns and Shibboleths112113- "If the data exists, it deserves a chart." Wrong. Operators need intervention surfaces, not metric hoarding.114- "A migration dashboard should mostly show percent complete." Weak. Experts track drift, blocked edges, and unverified seams because those predict rollout risk.115116## Reference Map117118- `references/INDEX.md`119- `references/dashboard-panels.md`