# Codee3 > Codee3 installs an authority-graded knowledge layer into a code repository, routes supported AI coding tools to it, and provides zero-dependency guard scripts that fail CI when the governed structure breaks. Positioning: your agents do not have a memory problem; your repository has an authority problem. Codee3 governs the knowledge an agent reads, rather than optimising the agent. Scope boundary, stated precisely: the guards check STRUCTURE inside the governed .ai/ directory. They do not establish factual correctness, do not compare prose against source code, do not observe runtime behaviour, and do not prevent production incidents. Commercial status: commercial access is not open yet. Published pricing is the intended launch model, not an offer. ## Product - [Codee3 — authority-graded repository knowledge, enforced in your CI](https://codee3.com/): Your agents do not have a memory problem. Your repository has an authority problem. Codee3 installs an authority-graded knowledge layer beside your code, routes your agents to it, and fails CI when its governed structure breaks. - [Structural enforcement — how Codee3 guards run in your CI](https://codee3.com/enforcement): Dashboards report drift. Repository guards can stop structural drift from merging. What each Codee3 guard checks inside the governed .ai/ directory, what it fails on, and what it does not prove. - [How Codee3 works — installation, routing, guards](https://codee3.com/how-it-works): What Codee3 writes into your repository, how it routes ten AI coding tools at one governed source, what the guards check, and where the authoring boundary sits. - [Architecture — the authority model behind Codee3](https://codee3.com/architecture): The layered authority model, the document lifecycle, index-first navigation, determinism, the no-versioning law, and the advanced opt-in governance layer. - [How Codee3 compares to docs, wikis, ADRs, RAG and agent memory](https://codee3.com/compare): An honest comparison. What READMEs, wikis, ADRs, retrieval, per-tool rules files, doc generators and portals each solve, and what each leaves open. - [Access — intended licence and commercial terms](https://codee3.com/access): Commercial access is not open yet. The intended one-time legal-entity licence, what it covers, what is not built, and the ownership terms — published so they can be evaluated. ## Method - [Authority-Graded Repository Knowledge — an open specification](https://codee3.com/standard): An open specification for giving repository knowledge declared authority, visible verification state, timeless identity and index-first routing. Vendor-neutral, adoptable without any product. Authored by Codee3. ## Learn - [Learn — repository knowledge, AI agents, and knowledge governance](https://codee3.com/learn): Three pillars: what repository knowledge actually is, how to work with AI agents in a real codebase, and how knowledge governance works. Plus a glossary of governed-knowledge terms. - [Why repositories fail AI agents](https://codee3.com/why-repositories-fail-agents): A repository is an incomplete account of itself. The authority problem, the staleness problem, the fragmentation problem, the accumulation problem, and why agents amplify all four. - [Context is not knowledge](https://codee3.com/learn/context-is-not-knowledge): Feeding an agent more text is not the same as giving it knowledge. Knowledge has identity, warrant, an owner and declared authority; context is bytes in a window. - [Why repositories are hostile to AI agents](https://codee3.com/learn/why-repositories-are-hostile-to-ai-agents): Humans carry the missing context in their heads. Agents do not. The five structural failure modes of an ungoverned repository. - [Retrieval is not truth](https://codee3.com/learn/retrieval-is-not-truth): Vector search answers where. Governance answers whether you may rely on it. Why retrieving the text is only half the problem. - [Documentation is not governed authority](https://codee3.com/learn/documentation-is-not-governed-authority): Why /docs rots. A projection with no declared source, no verified date and nothing accountable for it will drift by default. - [Context rot, and why a bigger window does not fix authority](https://codee3.com/learn/context-rot-and-why-bigger-windows-do-not-help): Measured degradation as input length grows, why models do worse on logically ordered haystacks, and why none of it is solved by adding tokens. - [Why generated instruction files can make things worse](https://codee3.com/learn/why-generated-instruction-files-can-make-things-worse): A controlled study found LLM-generated repository context files reduced task success and raised cost. What that does and does not tell you about writing your own. - [Proposal versus decision](https://codee3.com/learn/proposal-versus-decision): An agent cannot tell "we might do X" from "we decided X" unless the repository says so. How standing gets lost, and what declaring it costs. - [What happens at month three](https://codee3.com/learn/what-happens-at-month-three): The point where AI-assisted work stops feeling fast. What accumulates, why it is invisible at first, and which parts are structural rather than behavioural. - [What belongs in an instruction file — and what does not](https://codee3.com/learn/what-belongs-in-an-instruction-file): A practical rule: include what the agent cannot discover by reading the repository, and leave out everything it can. - [Enforcement versus reporting](https://codee3.com/learn/enforcement-versus-reporting): The difference between a check that fails a build and a score that appears on a dashboard, and why the distinction decides whether standards hold. - [What to measure, and what not to](https://codee3.com/learn/what-to-measure-and-what-not-to): Governance tooling dies from developer resistance more often than from budget refusal. Measuring repository structures instead of people. ## Company - [About Codee3](https://codee3.com/about): Why Codee3 exists, the product principles it is built under, and what it is today. - [Privacy](https://codee3.com/privacy): The Codee3 product collects no telemetry or customer data. This website stores only information you deliberately submit. - [Terms](https://codee3.com/terms): Website terms. The commercial licence terms are not yet settled.