Project memory that agents can inspect

The MCP layer is designed around a simple boundary: code stays in Git, short startup rules stay in project.md, and long-lived agent work memory is stored in the local project.ithz archive. That archive can keep decisions, gates, risks, next steps and checkpoints close to the project instead of scattering them across chats or vendor-side memory.

Project Ledger v1 adds a more explicit control surface on top of that memory. A team can record durable decisions, scoped claims, blocked claims, reviewer notes and replication packs. In practice, this helps an agent know not only what the project remembers, but also what it is allowed to claim, what is still conditional and what must not be repeated publicly.

This does not turn ITHZ MCP into a production database, cloud sync product or Git replacement. Git remains the transport and history for source code. ITHZ MCP complements it with auditable work memory: bounded context packs, provenance, redaction checks and a clearer handoff trail for AI-assisted development.

For a team, the practical value is less context drift. A new agent run can start from project status, workflow profiles and a deterministic context pack before it reads broad source trees. Reviewers get a trail of why something was done, which gates applied, and which claims are safe or blocked.

The public package also keeps the safety boundary visible: raw prompts are not the default public memory surface, sensitive content can be redacted or blocked, and large repositories can avoid turning every task into a full-scan exercise.