Control
Quiet control session
A quiet reference case showing what normal coverage and bounded secondary-warning output look like.
Project TellTale
Trajectory diagnostics demo
TellTale analyzes agent-session structure and turns it into a readable diagnostic report. This demo keeps the contrast simple: one quiet control case, one pathological reset case, and one Gemini-adaptation walkthrough.
Guided walkthrough
Short TellTale demo video
A quick guided pass through the control and pathological specimens. Best paired with the landing page itself as the underlying evidence surface.
Pathology
Reset-polluted session
A visibly broken case with replay/collision and coverage trouble surfaced as one incident story.
Adaptation
Gemini adaptation demo
Shows a Gemini-shaped synthetic source fixture being adapted into the standard TellTale report path with provenance kept explicit.
Canonical run path
Repeatable report bundle
Use the same bounded run shape every time to turn a session artifact into the report bundle that powers the demo surfaces.
telltale run --input session.jsonl --out ./report [--label specimen-name]
The resulting bundle should include the markdown report, the structured report artifact, and the paired demo surfaces in one output folder.
Report contract
What a finished report needs
The contract is simple: explicit coverage, visible source provenance, a chronological incident summary, separated primary vs secondary signals, and practical next steps.
The renderer, sample report, and demo shell should all agree on that shape.
Reading guide
How to move through it
- Start with the control case so the quiet baseline is clear.
- Then open the pathological case and compare the incident summary, primary findings, and warnings.
- Use the Gemini demo for the source-adaptation lane, where provenance and bounded evidence stay explicit.
Field notes
Notes and framing
A browsable note surface for category-setting posts, public framing, and short explanations of what TellTale is actually for.