For executives
One board showing what is broken, who it affects and the evidence.
One board
| Finding | Kind | Severity | Persona | Runs | Verdict |
|---|---|---|---|---|---|
| A contributor can open the rates table for all writers | permission | major | lin-contributor | 1 | confirmed |
| On a phone the Submit button sits under the keyboard | friction | major | sam-author | 2 | confirmed |
| Scheduling an issue for a past date returns a server error | bug | major | ada-editor | 1 | confirmed |
| The draft title field has no accessible name | accessibility | minor | sam-author | 1 | pending |
| The payment status "settled" is unclear to a contributor | question | info | lin-contributor | 3 | pending |
Each row names the problem, its severity, the persona affected and the reviewer’s verdict. A screenshot sits behind each one. The board is static files, so it can sit behind your own login.
What a run costs
Each run record stores its model calls, tokens and cost in US dollars. These two are synthetic examples, and the Grafana dashboards show spend by model over time.
Where it stands
- Scaffold
- Engine
- Demo app and example cast
- Packaging
- Clouds
- Target adapters
Dummy Run is pre-release. The code is under Apache-2.0 and telemetry is OpenTelemetry, so any backend you already pay for can store it. A QA lead or developer runs it. Compliance and product read the board.
Sources
The milestones are in the plan, sourced. The costs are the usage.cost_usd field of 2026-10-16-ada-editor-003 and 2026-10-17-ravi-reviewer-005, measured.