Why AI coding needs a project knowledge layer
Most AI coding context is reconstructed from scratch every session: the model re-reads files, re-derives structure, and re-learns conventions it learned an hour ago. A project knowledge layer replaces that repeated discovery with a validated, reusable account of how the system actually works, compiled per task and kept true against the real code.
The cost of rediscovery
Without a knowledge layer, every session starts at zero. The model opens the same files, traces the same call paths, and infers the same conventions, then throws all of it away when the session ends. The next session repeats the work. This is one of the largest hidden costs in AI coding, and it is invisible because each individual rediscovery looks cheap.
discover structure
discover it again
and again
What a knowledge layer actually is
It is not documentation, which goes stale and nobody updates. It is not raw retrieval, which fetches text without structure. It is the answer to "how does this system work right now," assembled deliberately, validated against the live files, and stored so the next task can reuse it instead of rebuilding it.
The defining property is that it is kept true. A note that is never checked is a liability. A knowledge layer is validated each time it is used, so it stays trustworthy as the code moves.
Compiled per task, not stuffed
A good knowledge layer is selective. It does not dump everything known about the project into every prompt; it compiles the slice relevant to the task at hand. The structure is what makes selection possible: because the layer knows what relates to what, it can hand the session exactly the context this task needs.
Selection beats stuffing. A knowledge layer is valuable because it lets a session start with the right context, not the most context.
Why it compounds
The payoff grows over time. Each validated piece of project knowledge makes future sessions start faster and make fewer wrong assumptions. Unlike a bigger context window, which costs the same every call, a knowledge layer is an investment that pays back on every subsequent task.
How Avorelo helps
Avorelo builds and maintains this layer as part of normal work. It assembles the relevant context for each task, validates it against the real files, and carries the verified result forward in the session receipt. The next session starts from known project knowledge instead of rediscovering the codebase, and the layer stays true because it is checked every time it is used.