explanation-traces

To trace agent selection, query the session-trace.json file to view a factual timeline of routing decisions. This filters recorded JSON evidence to show exactly why a specific agent was picked, preventing post-hoc rationalizations.

Decision tracing handles incomplete evidence by flagging missing fields and reporting gaps honestly. It applies integrity checks against the session-trace.json schema to ensure answers do not overclaim when the recorded data is partial.

The best way to troubleshoot a failed gate is to filter the session-trace.json for gate verdicts. This read-only approach presents the exact recorded decision evidence, showing the specific reason a gate failed without reconstructing events.

You cannot visualize routing decisions without the trace file, but the system guides you on enabling hooks to generate it. It points to the expected trace schema so you can start recording session data for future analysis.

Decision tracing does not reconstruct events from memory. It parses session-trace.json using read-only discovery to present a human-readable timeline of routing and skill phase transitions, preserving the original evidence exactly as recorded.