Programme 01 · PegBit WitnessStage: Pilot
Verifiable records of what AI agents do
- Question
- Can anyone independently verify what an autonomous AI agent did, without having to trust the organisation that ran it?
- Why it matters
- Agents now run commands, touch data and make decisions. When something goes wrong, the only record is often held by the same party being questioned, and logs can be edited. Monitoring tools usually also require sending private data to another cloud.
- Approach
- Every prompt, answer and tool call is sealed into a SHA-256 hash chain, so editing, dropping or reordering a record breaks the chain.
- A split-plane design keeps private data in the customer's own environment. Only hashes are sealed.
- Canonical hashing follows RFC 8785 and timestamps follow RFC 3161.
- Detection of breakout and runaway-loop behaviour, and a one-click human circuit breaker that freezes an agent.
- An offline verifier that checks an evidence bundle in a browser with no internet connection.
- Evidence so far
- The sealing engine, breakout and loop detection, circuit breaker and offline verifier are built and tested internally.
- A staging pilot is running with GlobalPrayerAltar.
- A public sample console, loaded with sample evidence, can be opened and tried.
- Open work
- Publish the offline verification method as an open, documented protocol.
- Run on low-power edge hardware with no cloud connection.
- Pilots with community and public-interest teams running AI agents.