Live case register
Reports in. Decisions reconstructed.
Reports awaiting reconstruction stay on the broken rail. Completed audits move to the solid record.
- Awaiting audit
- —
- Past audits
- —
Reported incidents
- Loading case activity…
Audit history
- Loading audit history…
Case source
Loading the case register.
Checking for reported incidents and completed audits.
Sample case · RA–2026–07
Was the agent wrong—or was the truth late?
HindSight reconstructs the moment of decision: what was true, what the agent could know, and what only became clear later. Run one case from incorrect invoice to safe remediation and reusable memory.
- Jul 01€0.15 rate takes effect
- Jul 02Agent sees €0.25 and bills the call
- 48 HKnowledge gap
- Jul 03Correction becomes queryable
- Reconstructtruth and available knowledge
- Judgethe decision without hindsight bias
- Learnfrom a safe, reusable remediation
01 · Outcome
The invoice was wrong. The agent wasn’t.
02 · Timeline
What was true vs what the agent could know
All times are shown in UTC.
The correct rate took effect before the billing decision, but it did not become queryable until 48 hours later.
48 h
effective → recorded
Business truth
What actually applied to the call
- Correct rate takes effect —
- Call is billed —
- Correction is recorded The correct rate becomes queryable
Reconstructed assertion: —
Agent knowledge
What the agent could query at decision time
- Available rate —
- Decision is made The agent uses the only version it can see
- Correction finally becomes visible It was unavailable when the agent decided
Selected assertion: —
Accountability verdict
Why the agent is not at fault
- Billed
- —
- Expected
- —
- Refund
- —
Root cause: —
Inspect the original decision record
Decision snapshot
Billing decision
- Event
- —
- Agent
- —
- Action
- —
- Duration
- —
- Amount
- —
- Selected rate
- —
- Decided at
- Decision ID
—
03 · Evidence
The missing record is part of the proof
Available, retrieved, and used are separate states.
The corrected tariff was not in the agent’s record when it made the billing decision. HindSight records both the evidence it used and the evidence it could not have retrieved.
Inspect the full evidence trace
| Evidence | Available | Retrieved | Method | Shown to model | Used | Exclusion reason |
|---|
04 · Safe fix
Refund once. Replay without duplicates.
- Final invoice
- —
- Refund
- —
- Dispute
- —
- Incidents opened
- —
- Memories created
- —
- Applied runs
- —
Inspect remediation attempts
Remediation attempts
05 · Learning
The next investigation starts with precedent, not from zero.
Cases reused—
Checklist loaded—
Recommendation—
Root cause confirmed—
Investigation starts cold
—
—
procedural steps reused
Investigation starts with a proven playbook
—
—
steps loaded from a similar incident
- Method
- —
- Rank
- —
- Score
- —
- Suggested cause
- —
06 · Technical proof
The model explains. Deterministic systems decide.
Amazon Bedrock
- Model
- —
- Turns
- —
- Role
- —
CockroachDB Managed MCP
- Transport
- —
- Tool access
- —
- Mutations
- —
Vector memory
- Index
- —
- Embedding
- —
- Dimensions
- —
Inspect request-level proof
- Agent run ID
—- Context snapshot
—- Tool calls
- Request IDs