The wedge is the cold path
The inspector is where an agent answer becomes debuggable: the page centers source lineage, superseded memory, and forgotten context rather than a performance claim.
Which source records appeared in the answer path.
The trail starts with the content items, tags, artifacts, and snippets the agent used when forming the response.
Which memories were replaced by newer evidence.
When a source changes, the old memory should not silently compete with the current one. The inspector is designed to show that lineage.
Where the answer path ran out of useful context.
Forgotten context is actionable only when a human can see the gap and add or refresh the right source material.
Supersession must be visible
Agents need current memory, but operators need to know what changed. Supersession keeps replaced evidence available for inspection without letting stale context masquerade as the current answer path.
Original source artifact retained for audit.
Active source artifact used for recall.
Human can inspect which current item was used.
What the inspector should expose
The page treats inspectability as a concrete data contract. A useful inspector needs source, artifact, current-state, supersession, and answer-use signals in one place.
| Signal | What it proves |
|---|---|
source | Original page, ticket, CSV row, or document |
artifact | Summary, extracted text, metadata, and tags |
current | Whether this memory is the active version |
supersedes | Prior item replaced by newer evidence |
used | Whether the item appeared in the answer trail |
What stays on the roadmap
The real inspector screenshot and measured retrieval scorecard belong on the roadmap until the product and evaluation harness support them.
Inspection is how memory earns trust.
Use the MCP server for recall, then inspect the source trail when an answer needs evidence or correction.