1 · Loading
Checking controls
Reading the current control set from the audit log.
2 · Empty
No engagements yet
Engagements appear here once a statement of work is countersigned.
3 · Partial — some of it worked
3 of 5 sources loaded
Two systems did not respond. Figures below exclude them.
4 · Error
Could not load the control set
The audit service did not respond. Nothing was changed.
AUDIT_TIMEOUT · req 4f2a91c · 14:02:11Z
5 · Permission denied
You do not have access to the audit log
Access is granted per engagement. Ask the engagement lead to add you.
6 · Success
Engagement signed
G8V-2026-014 is live. The audit trail starts from now.
Empty — with a picture
No coverage yet
Cells fill in as tests are linked to requirements.
Nothing has happened yet
Every change to this engagement is recorded here.
No documents yet
Upload a statement of work to start the library.
Nothing waiting for you
Findings assigned to you appear here.
No matches
Try fewer words, or search every engagement.
Error boundary — a region that threw while rendering
This part could not be shown
Something in it went wrong. The rest of the page still works.
ErrorBoundary draws this in place of what it wraps, inside the frame
around it. It never shows the error's own text — that goes to onError for the log. A new
resetKey (the page's path, a record's id) clears it; so does Try again.
Every state names what happened, whether anything changed, and what to do next.
Error carries a .state-detail line a support engineer can quote and a user can ignore.
Partial is the one most systems omit, and the one that matters most in audited
environments — a figure computed from three of five sources must say so.