A Project Needs Two Memories—But Only One Should Travel With Git

A project requires two distinct types of memory: one for local, operational details and another for shared, team-approved facts stored in Git. Treating all project information as a single memory source creates problems where either sensitive runtime details leak into Git or project knowledge remains isolated on individual machines.

APX and APC address this by providing two memories with distinct purposes. APX retains local notes, capturing temporary contextual information while an agent operates, ensuring that this runtime-specific knowledge remains separate from the shared project memory. This local memory is not intended to become permanent project policy but rather to aid daily work without automatically becoming part of the repository.

In contrast, APC contains curated project facts that are safe for the entire team. These facts are reviewed and approved before being committed to APC, residing in the repository so Git can carry them through clones, reviews, and history. This ensures that decisions based on durable project knowledge are accessible across all team members and machines.

The key distinction lies in authorship: APX does not automatically treat captured runtime notes as permission to write to APC. Instead, a person reviews the note and decides its appropriate placement. The two memories work together to improve daily work by separating the types of knowledge. While APC makes shared context explicit, APX maintains its usefulness as a local runtime that can remember short-lived operational details without blurring the line between personal context and shared project artifacts.

The approach recognizes that local notes serve a different audience and have a different lifespan than information stored in APC. APC clarifies shared understanding, while APX provides the necessary local context for efficient operation. Both are valuable when handled deliberately and appropriately.