Scalarmind
The colleague who remembers why
A company grows, its tools improve, and one person still gets the same questions. What would it take for the organization to carry more of its own memory?
Read the storyThe journal / A series in six parts
Working knowledge.
What teams remember. What agents share. And the decisions we still need to make together.
Begin with an absence.
A founder takes a holiday. Her team still needs her memory.
Read the first story A founder takes a holiday. Her team still needs her memory.
When everyone can work at once
Parallel agents make it easy to start several pieces of work. Following a feature through a fictional team reveals how much still depends on a shared understanding of what is being built.
The answer that used to be right
A document can be accurate about the past and misleading about the present. Following one answer through time reveals what a useful memory has to preserve.
Who gets to know?
A shared answer can cross a boundary its source was never meant to cross. Where should an agent's knowledge begin, and where should it stop?
What is worth remembering?
After a difficult piece of work, there is usually more to save than the next person needs. A field note on finding the lesson inside the transcript.
The work before the work
An agent can finish quickly while its user keeps paying to explain the project again. A field note on seeing that cost and testing whether shared memory changes it.
Each piece stands on its own. Links within the text and at the end of each article follow the questions from one piece to the next.