The working A prototype: use its controls to test the build question.
Audit whether an AI agent actually did the job well, not just produced a convincing answer.
RN conceived the question, structured the evidence boundaries, designed the experience, implemented the prototype and documented its limits.
This independent prototype demonstrates an approach; it is not a deployed client system, professional advice or proof of real-world outcomes.
Work through the controls with a situation of your own rather than the sample values. The tool responds to what you put in, so the useful output comes from real input, and everything is processed in your browser as you go. Any sample content you find already loaded is there to show the shape of a filled-in state, and you can clear it and start again at any point.
The build overview sets out the question, the purpose, the role and the evidence status in one place, and the public record behind it states what changed, what another person can reuse and what supports the system. If you want to judge how far this build should be trusted, the record is the page to read, not this one.
BUILD 039-A
Agent Work Trace Inspector
Audit whether an AI agent actually did the job well, not just produced a convincing answer.
TRACE BLOCKED
1 failed or aborted · 1 integrity gaps
S1 · plan
Declared plan only; not execution.
parent ROOT · successS2 · tool
retrieve_sources
parent S1 · successS3 · evidence
Declared event
parent S2 · failedS4 · decision
DECISION-020-TRACE
parent S3 · successS5 · answer
SRC-PRIMARY-01
parent S4 · successS3: evidence identity, scope, source, and freshness required.
Boundary: This is a redacted, synthetic, user-visible event record—not hidden reasoning or a complete runtime log. “Complete” means only complete against this declared schema and capture boundary. Replay inspects stored data and never repeats live side effects; traceability does not prove truth, correctness, safety, or approval.