Post-voyage analysis
Reports
Read from every registered workspace’s artefacts
⚑Build note: QA Reports, Token Usage, Acceptance Criteria, Security Review and Voyage Summary all read real Maestro artefacts through the Hub backend. Where a figure was never recorded, a page says so rather than showing a zero.
Live data→
QA Reports
Per-order QA verdicts: test counts, acceptance criteria, defects, and sign-off.
…reading /api/v1/reports/qa
Live data→
Token Usage
Filterable token spend with drill-down: project → voyage → order → role/model. CSV export.
Liveforward-looking · recorded from v5.0.2
Live data→
Acceptance Criteria
Coverage of recorded verification, then met / partial / outstanding over covered orders — with each result’s source.
Livecoverage computed on the page
Live data→
Security Review
Per-order SEC review verdicts, UNDETERMINED where unreadable — and archived scanner runs, kept separate.
Liveverdicts read on the page
Live data→
Voyage Summary
Per voyage: PR and dates, token spend by role and crew, and each order’s QA, criteria and security verdicts.
Livecomposed per voyage on the page