← All cases · System builds system · in operation · since July 2026
Many writers, no overwriting
One shared, versioned knowledge base — over 3,000 commits from around two dozen identities in the team brain since the start.
Figure: über 3.000 Commits von rund zwei Dutzend Commit-Identitäten im Team-Brain seit dem Start im Frühsommer · measured 24 October 2026
Request: „Share my state.“
- Every note has an owner; others contribute through version control (Git)
- Personal branches are synchronised with the main state automatically and merged back conflict-free
- A custom merge driver combines parallel contributions without a model run; a note's stable ID is its identity
- Protected branches are not changed directly
Parallel changes to a shared knowledge base overwrite each other; contributions pile up in a staging folder — that is how it goes wherever several people work on the same files.
Approval to share.
The first contribution path via a collection folder piled up around 30 open contributions — replaced by automatic merging; the 30 were reviewed and resolved one by one.
Any team that maintains knowledge together. Merging is done by a program without a language model, so nothing gets invented.
A shared brain is only shared if many people can work on it at the same time. Every note has an owner, everyone else contributes through Git — merged by a program without a language model so nothing gets invented; a note's stable ID is its identity. Since the start in early summer the team brain has accumulated over 3,000 commits from around two dozen identities. The first approach with a collection folder piled up around 30 open contributions — automatic merging solved that, and the folder is gone.
Evidence in my own archive · as of 25 October 2026.