Evaluation & systems · Local foundation
Sentinel Replay
Keep the evidence. Expose the coverage gaps.
A local agent-incident forensics foundation with a hash-chained journal, bounded workspace recovery and an explicit policy boundary for one routed tool.
The question
An incident record must distinguish what was observed, what was authorized, what actually completed and which actions were never covered.
How it works
- Record proposals, decisions and effects in a verifiable journal.
- Match bounded events to a synthetic incident and compare policies without rewriting history.
- Use a narrow MCP/OPA copy-tool path and conservatively label native tools outside that path as uncovered.
Evidence & results
- A retained cooperative run includes a denied fixture copy and an allowed public-fixture copy.
- A separate same-run check shows a denied gateway request alongside an uncovered native action.
- Local named-file recovery checks verify bounded effect bytes before finalizing an interrupted record.
Scope & next steps
- Not comprehensive action interception, production prevention or verified replay of a general coding agent.
- Hash-chain integrity does not establish author identity, trusted origin or causality.
- Synthetic journals and local fixtures do not establish real-world incident rates or beneficiary outcomes.
Go one level deeper.
Ask about the implementation, tradeoffs, or my contribution.
Explore with the portfolio guide