Akashic: A Continuous Knowledge Loop for AI-Driven Development
Stale AI context forces developers to re-explain boundaries and verify edge cases on every session. Akashic turns knowledge refresh into an automated byproduct of commits and archived chats, cutting the manual overhead that usually makes team documentation decay.
Akashic tackles a common problem: as AI aids more development work, team knowledge fragments into code, docs, and chat logs, and no one has time to manually reconcile them. The practice builds a three-layer knowledge base in Git: L1 AGENTS.md acts as an entry and router, L2 holds Skills and module docs for task-specific reuse, and L3 keeps source-code comments for implementation constraints. This structure lets an Agent load only the relevant slice of knowledge per task, avoiding the context bloat of dumping everything into one file.
Two automated write-back paths keep that knowledge fresh. On every code commit, a script maps changed files to potentially affected documents and provides diff evidence; an Agent then decides whether responsibilities or rules shifted and updates the docs in the same commit. Separately, archived sessions from Claude Code and Codex are mined by a Session Agent and an Audit Agent, which extract reusable conclusions, verify them against fixed snapshots of code and existing knowledge, and submit them as merge requests for human review. An Akashic CLI handles installation, config sync, and session uploads automatically via Git hooks, so members never manually maintain the tooling.
The system also produces conversation insights: metrics like session rounds, tokens, and duration, combined with labels such as 'supplement knowledge' and 'request redo', help teams spot where context is missing or execution goes wrong. The team reports that after introducing the loop, similar tasks saw fewer rounds and corrections, suggesting the knowledge base is actually closing the feedback cycle.
Baking knowledge updates into the commit pipeline is a sound way to keep docs fresh, but it depends on the Agent's judgment of whether a change actually shifts responsibilities; a wrong 'no update' call silently reintroduces the staleness it is meant to prevent.
The three-layer separation directly addresses the context-window overload problem: instead of loading a giant AGENTS.md, an Agent progressively drills from global route to module doc to source comment, matching the granularity to the task.
Measuring session rounds and correction labels gives teams a quantitative handle on AI collaboration quality, turning vague impressions about 'more iterations' into data that can be tied to specific knowledge gaps.
The human Owner review for every knowledge MR suggests the team trusts the pipeline to draft but not to publish; that human-in-the-loop is a pragmatic compromise between automation and accountability.