Git for the intent behind agent-written code. Records what your coding agent decided and why, and links every commit to it.
JavaScript ai-codingclaudeclaude-codeclaude-code-pluginclicoding-agentsdeveloper-toolsgitllmtypescript
docs(readme): show how the why falls away as abstraction rises
Eren699969299869
diff --git a/README.md b/README.mdindex b7d57de..dd4c8fa 100644--- a/README.md+++ b/README.md@@ -76,6 +76,8 @@ just in separate places. cogit ties them together, so you can always walk back asomething was done. It helps most when you juggle projects: I run 5-10 agents at once across 2-3of them, and a few minutes later I can lose track of what I did where.+<img src="docs/images/why-abstraction.png" alt="A conceptual chart from machine code to software factories: abstraction keeps rising, while how much of the why you can still trace falls sharply once AI starts writing code. cogit keeps what falls away.">+The problem is bigger than one person's memory. In a working paper on 718 firms, agents brought23% more pull requests and 49% longer time to merge, with no significant rise in finished work.A reviewer sees what changed, not why. [More, with sources](docs/guide/why.md).diff --git a/docs/images/why-abstraction.png b/docs/images/why-abstraction.pngnew file mode 100644index 0000000..8ea21c4Binary files /dev/null and b/docs/images/why-abstraction.png differ