Span Chain
Blog GitHub ↗
Field Notes

Blog

Auditing AI agents · GhostFactory
2026-10-14

We audited an agent’s report. Then we had to audit the audit.

At the end of a session an agent writes a summary, and that summary is what I act on. So I wanted to know how much of a summary actually holds: every factual claim, checked against git history and the tool outputs recorded in the transcript.

2026-09-26

The toggle did not stop the pack. “Destroyed” is still a vendor claim.

A coding agent packs your workspace under ~/.zcode, including .git. Toggles that look like off switches do not stop capture. “Destroyed” is still a vendor claim, not a session fact.

2026-09-24

Changelog said AGENTS.md. The session never recorded it.

Two developers pull the same commit and the same AGENTS.md. One session loads the file; the other skips it with no warning. That is a record problem, not a philosophy problem.

2026-09-18

How to Audit Claude Code Sessions: A Tamper-Evident Trail for Every Tool Call

Claude Code reads files, writes code and runs shell commands on your behalf. Here is how to audit Claude Code sessions into a hash-chained, tamper-evident trail you control — using two hooks and one Python script.

2026-08-06

How to Audit AI Agents: From Mutable Logs to Tamper-Evident History

When an AI agent fails, the first question is why. The second, increasingly asked by security and compliance teams, is: can you prove it?

Span Chain

Self-hosted trace recorder and structural regression-diff layer for AI agents.

Product

  • GitHub ↗
  • Self-host
  • Blog

Company

  • GhostFactory
  • Contact
© 2026 GhostFactory · MIT LicenseBack to top ↑