Observability
Answer “why did the system return this number?” from one trace
Every investigation carries enough context to reconstruct resolution, retrieval, validation, calculation and human action.
| Trace field | Example from anomaly case |
|---|---|
| requestId | DESP-REQ-004817 |
| userRole | industrial_statistics_officer |
| purpose | anomaly_investigation |
| establishmentId | DP-MFG-18427 |
| reportingPeriod | 2025-26 |
| recordVersion | submitted-v1 → corrected-v2 |
| toolsInvoked | resolve identity; get return; validate; correction history |
| validation | EMP_YOY_CHANGE = FAIL_HIGH |
| evidence | 7 source/version references |
| responseState | clarification_required → resolved |
| protectedAction | register correction |
| approvalState | supervisor-approved |
| auditOutcome | before/after versions retained |
Request ID
Resolved entity + period
Source/version retrieval
Rule execution
Evidence set
Officer review
Approved action
Immutable audit event
Correlation is mandatory across agent, tool and action layers so an explanation can be checked independently of the conversational response.
Primewayz industrial statistical intelligence