Engineering teams routinely lose the reasoning behind their own systems. Architecture decision records preserve some of it as prose, but prose has no machine-readable structure, no stable identity, and no defined behavior under concurrent authorship. We descri… [PDF]
A decision log written by many independent machines and synchronized through an object store under the team's own control, with no coordinating server, must nevertheless replay identically on every machine. This requires a total order over events that every re… [PDF]
kgai stores a team's engineering decisions as an append-only log of immutable, content-addressed events, and serves queries from a property graph derived from that log. This report describes the derivation. The log is the single source of truth. The graph is a… [PDF]
Engineering decision records are conventionally maintained by editing them in place, deleting them when they no longer apply, or expiring them through staleness heuristics. Each of these practices destroys information that teams and their AI agents later need.… [PDF]
Retrieval layers for AI coding agents are dominated by embedding-based semantic search, which buys tolerance to paraphrase at the price of nondeterminism, model dependence, and operational weight. We describe the read path of kgai, a local-first memory of engi… [PDF]
Sharing a decision memory across a development team normally means either operating a server or merging files, and merging files means merge conflicts. We describe the synchronization design of kgai, a decision memory kept locally by AI-assisted development te… [PDF]
Software teams lose the rationale behind structural decisions because documentation is written after the fact, when the reasoning has already begun to fade. We describe the capture model of kgai, a local-first, immutable knowledge graph of engineering decision… [PDF]
A configuration file committed to a repository arrives on a developer's machine with git clone, authored by whoever created that repository. When a tool grants such a file authority, its keys become capabilities: a store path is a write capability, a sync dest… [PDF]
kgai records a software team's engineering decisions as an append-only, content-addressed log, split into one shard per writer and projected into a small live graph of domain elements. This report examines how that design behaves as the log grows. We summarize… [PDF]
kgai stores a team's engineering decisions in an append-only log projected into a graph of domain elements. This report examines where the boundaries of such a store lie and what actually holds them. The default boundary is the repository, one store per projec… [PDF]