Most AI memory systems are designed as conveniences inside a product. The Personal Context Repository starts from a different question: what would durable AI context look like if the person, rather than the model provider, owned and governed the record?
The project takes the form of a private Markdown and Git repository organized around a short agent boot path, provenance, freshness, privacy tiers, and compiled lookup surfaces. The public artifact is the replicable architecture, not Josiah's personal files. Its purpose is to give AI agents durable context while keeping the underlying knowledge inspectable, correctable, and private by design.
The question behind Personal Context Repository
The answer is a small knowledge infrastructure built from ordinary files. Human-readable Markdown keeps claims inspectable; Git makes changes reviewable; provenance and freshness distinguish remembered facts from stale or uncertain ones; and privacy tiers prevent convenience from becoming indiscriminate exposure. People who work repeatedly with AI agents may benefit. The subject of the context is also the person most at risk, so privacy, consent, and correction must remain first-class.
How Personal Context Repository took shape
Agents enter through a compact llms.txt map and load information progressively instead of ingesting the repository wholesale. Compiled lookup surfaces accelerate routine work, while bidirectional question-asking gives an agent a way to notice gaps and ask the human to correct drift. Josiah developed the architecture through sustained personal use, including the idea that downstream utility encourages honest input and that agents should ask questions to repair context drift.
System in motion · owned context loop
The record becomes useful work—and useful work keeps the record honest.
Public architecture · private records remain private.
This is the compounding mechanism: governed context improves real work, real work makes accuracy consequential, and reviewable questions keep the record from quietly drifting.
What the evidence supports
The private system is used as working infrastructure across projects. This Compendium's paired human and /llm routes are one public application of the same architecture. Its effectiveness comes from a feedback loop. Because stored context will influence future help, the human has a reason to keep it accurate, and because the files remain visible, corrections can become durable rather than disappearing inside a conversation. The public article describes that pattern without exposing the private record that proved it.
The private repository, personal examples, psychological context, credentials, and third-party information are never publication material. Public examples must be synthetic. The planned public companion is a complete synthetic replication guide that a person or agent can inspect, adapt, and build upon without access to Josiah's private records.