The Log Is the Agent: Event-Sourced Graphs for Auditable, Forkable AI Systems

Yohei Nakajima's new paper, The Log Is the Agent, introduces ActiveGraph — a runtime that flips the typical agent architecture on its head. Instead of a conversation loop with bolted-on logging, ActiveGraph makes an append-only event log the single source of truth. The working graph is a deterministic projection of that log; behaviors (functions, classes, LLM calls, or logic on typed edges) react to graph changes and emit new events. No component instructs another — coordination happens through the shared graph.
Key Properties
- Deterministic replay — any run can be replayed from its log, exactly reproducing state.
- Cheap forking — branch a run at any event without re-executing the shared prefix. Useful for experimentation and debugging.
- End-to-end lineage — from high-level goal down to each model call that produced an artifact, traceable from the log alone.
Architecture Highlights
- The event log is immutable; the graph is recomputed on replay.
- Behaviors are attached to typed edges — they react to graph changes and emit new events, which append to the log.
- A determinism contract ensures that replay is sound: given the same log, the same graph state is produced.
Why This Matters for Agent Developers
Retrieval-and-summarization memory systems (common in frameworks like LangChain or BabyAGI) lose exact history. ActiveGraph's log-based approach gives you full causal reconstruction from log alone. The paper includes a worked diligence example where all causal structure is recoverable.
Open Source & Reproducible
The implementation is Apache-2.0 licensed. The paper promises a reproducible quickstart demo, deterministic replay, fork-and-diff, and lineage tracing. It extends the BabyAGI lineage and prior graph-memory research.
If you're building agents that need audit trails, debugging, or self-improvement loops, this architecture is worth evaluating. The log-based design is unusually well-suited for agents that need to replay, fork, and trace their own behavior.
📖 Read the full source: HN AI Agents
👀 See Also

Sense: Go SDK for LLM-powered test assertions and structured text extraction
Sense is a Go SDK that uses Claude for two main functions: evaluating non-deterministic output in tests with plain English assertions, and extracting typed structs from unstructured text through reflection and forced tool_use.

Prism MCP v5.1 adds 10x memory compression and agent learning from corrections
Prism MCP v5.1 introduces 10x memory compression via TurboQuant ported to TypeScript, enabling millions of memories on a laptop without vector databases. The update adds agent learning from user corrections and a visual knowledge graph interface.

Benchmark Results: GitHub CLI vs MCP Approaches for AI Agents
An independent benchmark compared GitHub CLI, MCP, MCP with Tool Search, and MCP with Code Mode for AI agent tasks. GitHub CLI was the most cost-effective, while MCP approaches showed trade-offs in cost, latency, and failure modes.

Claude Code Hook Monitors WIP Accumulation in AI Coding Workflows
A developer built a UserPromptSubmit hook for Claude Code that surfaces work-in-progress accumulation across four queues: uncommitted changes over 200 lines, three or more unpushed commits, pushed commits without changeset files, and release PRs open longer than 24 hours.