Project Ledger: Human-in-the-Loop Memory System for AI Coding Agents

A GitHub project called project-ledger provides a human-in-the-loop system for managing what AI coding agents remember about your codebase. The core problem it addresses: agents can't judge what matters—they treat implementation bugs the same as architectural flaws and log what they changed rather than what's important.

How It Works

The system has three main components:

• A YAML ledger with structured entries containing summaries, confidence levels, tags, and cross-references
• A /ledger skill that publishes entries and automatically spawns a Haiku auditor to review them cold
• A UserPromptSubmit hook that runs TF-IDF search on every prompt and injects matching entries automatically before the agent starts thinking

The hook is critical—without it, you're just writing YAML into the void. As noted in the source: "Agents never go read reference docs unprompted—the hook runs on every prompt, searches the ledger, and injects relevant entries before the agent starts thinking."

Practical Example

The creator describes a real-world use case: weeks after fixing a color rendering issue on an embedded project, they asked an agent "remember what we did where we fixed this before?" The hook surfaced the exact entry about 8-bit quantization crushing color fidelity at low values, including root cause, thresholds, and affected components.

Comparison & Approach

Compared to OpenViking, this system requires manual work but has a simpler architecture: just a YAML file plus a shell hook with no backend. The philosophy is that for projects where insights are hard-won, humans should decide what gets carried forward.

The system is designed to prevent technical debt accumulation as AI agents operate in codebases—each change gets harder to get right without proper context about what matters.