Challenge
Knowledge about a project lives in the head of whoever ran it. That person leaves and the code stays behind without explanations: why this database, where this formula came from, what was tried and why it was dropped.
We had the same illness in a different form. The AI assistant's memory was invisible to everyone else, and every new conversation started from zero.
Solution
We moved all of that memory outside, into a single store of linked notes, and made it the only source of truth.
Every project gets a status card, a work journal, a task list and decisions with their reasoning. Architectural decisions are recorded separately and include the price of not taking them.
A team of specialists works on top of the store: an architect, developers per stack, a tester, a security engineer, an infrastructure engineer, an analyst, a designer, and specialists for search and for writing. Each reads the shared rules and the profile of their project, does the work, and leaves a journal entry.
Architecture and implementation
How it is arranged:
· a single store of linked notes covering twelve projects
· a status card, journal, tasks and decisions for each project
· a body of shared rules, each with the history of how it appeared
· fourteen specialists with defined roles and boundaries
· a protocol that keeps one agent from overwriting another
What this case does not show: the contents of the notes, client names and credentials.
Result
The store runs twelve projects and does not lose context between sessions. The site you are reading was designed, written and reviewed inside it, and every stage is in the journal.
An ordinary case study says we can build this for you. This one says something else — we built it for ourselves and work inside it daily.
