DEV Community

EvanLin | Contorium
EvanLin | Contorium

Posted on

We Version Code. Why Don’t We Version Project Knowledge?

Git changed software development by making code history visible.

Every commit tells us what changed.

But it doesn’t tell us something equally important:

Why did we make that change?

The reasoning usually disappears into:

  • Chat conversations
  • Design meetings
  • Issue discussions
  • Temporary AI chats
  • Someone’s memory

Months later, developers—and now AI—have to reconstruct that reasoning from scratch.

We’ve become very good at versioning code.

We’re still surprisingly bad at versioning knowledge.

As AI becomes part of everyday software development, this gap becomes much more obvious.

AI doesn’t just need access to files.

It needs access to the project’s accumulated understanding.

What assumptions still hold?

Which architectural decisions have expired?

Which constraints should never be violated?

These questions are rarely answered by source code alone.

That’s why I’m exploring a different idea with Contorium.

Not another coding assistant.

Not another IDE.

But a Project Intelligence Layer that preserves the evolving knowledge behind a project, so both humans and AI can build on understanding instead of starting over.

Git remembers the code.

Projects should remember their thinking.

https://www.contorium.dev/ https://github.com/ContoriumLabs/contorium

Top comments (0)