Memory belongs to the workspace
Not to a login and not to a chat history. It carries who was involved, so you keep both facts: what the team knows, and who it came from.
The project remembers, not the person.
Every team has a person who holds the history. That is a single point of failure wearing a hoodie. Oolkin keeps the reasoning in the workspace, tagged with who was involved, so continuity stops depending on attendance.
Free to start. No card. Takes about a minute.
What actually goes wrong
- 01Onboarding is three weeks of asking people questions whose answers were written down nowhere.
- 02The same debate returns twice a year because the losing argument was never recorded, only the conclusion.
- 03When someone leaves, you find out how much of the project only existed in the conversation.
What Oolkin does about it
Standing rules everyone inherits
Set a rule once at the workspace level and every colleague in it is bound by it. A single colleague can be corrected more narrowly, and the narrower correction wins where the two disagree — the way a real organisation works.
Corrections are signed and reversible
When a human overrules a colleague's default, that becomes a signed rule with a version behind it. You can see what changed, when, and who signed it — and roll back to the version before if it made things worse.
What that looks like
worked exampleYou type
“A workspace rule: never present a metric without the date it was measured and the query that produced it.”
You get
Every colleague in the workspace
The rule binds all of them from the moment it is signed. A colleague that quotes a bare number gets corrected by its own standard.
Three weeks later
Any judgement formed before the rule is marked as predating it — so you can tell old habits from current behaviour instead of guessing.
Describe them once. They take it from there.
Free to start. No card. Takes about a minute.