Dashboard
Terminal Curator's dashboard shows published tasks, validation evidence and run history.
A demo dashboard is available here. Demo tasks, metrics and outcomes are synthetic. Actual run snapshots are shared separately.
Views
| View | Contents |
|---|---|
| Overview | Current publication, latest attempt, phase and measured counts. |
| Task List | Batch/task filters, ID/tag search and task details. |
| Validation | Oracle/NOP rewards, JUnit results and checksum linkage. |
| Runs | Archived attempts, outcomes, durations and recorded counts. |
A failed attempt can coexist with an older verified publication. Unknown
measurements display as —; report-only and conflicting evidence are labeled.
Curation validation does not establish semantic approval or a solved rollout.
Open your data
Use /terminal-curator:dashboard or $terminal-curator:dashboard. From the
block directory:
# Static snapshot, written to dashboard/site/index.html.
artifacts/env/terminal-curator/bin/python dashboard/progress_monitor.py --html
# Loopback server with automatic refresh every ten seconds.
artifacts/env/terminal-curator/bin/python dashboard/progress_monitor.py --serve --port 8086Use the same --config <file> / TERMINAL_CURATOR_CONFIG profile as the run.
Static snapshots require regeneration; the live server preserves filters and
navigation during refresh. Without either option, the command prints JSON.
Data and sharing
The browser receives selected metadata from state, matching reports, manifests, archives and contained trial/JUnit files. Task text, solutions, prompts, traces, full config, endpoints, host paths and raw errors stay off the page. IDs, tags, checksums and numeric usage remain visible; inspect them before sharing. Rendering is read-only; public deployment is a separate operation.