A developer who runs a 911 dispatch floor released Arcaeon 0.9.0, an MIT-licensed tool that makes AI agent logs verifiable by third parties. Agents write their own records of tool calls; Arcaeon adds an external, checkable chain so anyone can detect edits without the agent's cooperation. It targets the gap where an agent's self-reported 'story' is the only audit trail.
An arXiv paper, Hearsay, asks whether auditors can trust the records agent harnesses write of their own runs. Across sixteen deployed frameworks, none writes a record a third party can verify without trusting the writer. The authors show an externally kept append-only log of harness-model exchanges catches all fabricated or omitted entries, where hash chains over the harness's own record do not.
An arXiv paper, Hearsay, asks whether auditors can trust the records agent harnesses write of their own runs. Across sixteen deployed frameworks, none writes a record a third party can verify without trusting the writer. The authors show an externally kept append-only log of harness-model exchanges catches all fabricated or omitted entries, where hash chains over the harness's own record do not.
AgentAudit is a Python SDK that records what AI agents do — LLM calls, decisions, tool calls, inputs/outputs — into a hash-chained, tamper-evident audit trail. It targets teams building agents who need to debug failures and satisfy EU AI Act traceability requirements. The builder is seeking feedback and testers.
AgentAudit is a Python SDK that records what AI agents do — LLM calls, decisions, tool calls, inputs/outputs — into a hash-chained, tamper-evident audit trail. It targets teams building agents who need to debug failures and satisfy EU AI Act traceability requirements. The builder is seeking feedback and testers.
A developer describes why agent-written traces and compaction summaries make untrustworthy records of what an autonomous run actually did, and how their reef setup on a Raspberry Pi instead keeps runtime-written records of every exchange and report. A harness-evolution tutorial run also emits a replay.html showing each step's verdict and tree diff. The system records but does not enforce; enforcement must live where writes or sends happen.
A developer describes why agent-written traces and compaction summaries make untrustworthy records of what an autonomous run actually did, and how their reef setup on a Raspberry Pi instead keeps runtime-written records of every exchange and report. A harness-evolution tutorial run also emits a replay.html showing each step's verdict and tree diff. The system records but does not enforce; enforcement must live where writes or sends happen.
A lightweight accountability layer for AI agents that lets anyone verify what an agent did from their terminal in 15 lines of code, with no signup required. It uses blockchain-based finality semantics (settled, blockNumber) to provide tamper-evident records, solving the trust problem for agents acting with real authority.
A lightweight accountability layer for AI agents that lets anyone verify what an agent did from their terminal in 15 lines of code, with no signup required. It uses blockchain-based finality semantics (settled, blockNumber) to provide tamper-evident records, solving the trust problem for agents acting with real authority.
Cinchor is a lightweight tool that lets operations teams share verifiable records of autonomous agents' context, instructions, and output. It uses a custom L1 blockchain to anchor proofs in a tamper-evident manner, solving the problem of trusting first-party logs from AI agents.
Cinchor is a lightweight tool that lets operations teams share verifiable records of autonomous agents' context, instructions, and output. It uses a custom L1 blockchain to anchor proofs in a tamper-evident manner, solving the problem of trusting first-party logs from AI agents.