Hola Darlings!
The plan was to build a Karpathy-ish Obsidian brain for WittyWires.
Not a folder.
Not a notes dump.
Not a haunted cupboard full of screenshots, dead TODOs, emotional support Markdown, and one file called final-final-USE-THIS-one-seriously.md, which is, obviously, a liar.
An actual working project brain.
The dream was simple enough to fit on a mug: source goes in, evidence is kept, decisions get promoted, contradictions get named, and future Clawdius answers from the compiled understanding instead of spelunking through chat sludge with a torch in his mouth.
A lovely idea.
So naturally we tried to implement it by feeding the machine half a shed, four years of scars, several live project brains, a pile of old decisions, a wiki vault, a memory system, background stewards, contradiction checks, and my personal belief that if I glared at the screen hard enough it would become architecture.
Cock.
This is the WittyWires Way. We find a useful thing, identify the sensible path, then approach it sideways in a shopping trolley while Max shouts helpful phrases like more buttons and Clawdius quietly prepares a rollback plan for my personality.
The goal was not notes
The thing we wanted was not glamorous.
That is usually how the dangerous ones get in.
Nobody gets excited by knowledge hygiene, because it sounds like a local council leaflet explaining why your bin has been inspected by a man called Keith. But under the beige trousers was a genuinely important problem.
a local council leaflet explaining why your bin has been inspected by a man called Keith
WittyWires was getting too big to remember by vibes.
We had blog ideas, build notes, design decisions, launch rules, OpenClaw history, visual canon, product principles, agent scars, cron jobs, forum wiring, mail paranoia, Council machinery, and enough raw chat sediment to qualify as a protected wetland.
Everything was saved.
That was the trap.
it is in the garage, behind the bikes, inside a box labelled Christmas
Saving everything feels responsible, in the same way buying a fire extinguisher feels responsible until you remember it is in the garage, behind the bikes, inside a box labelled Christmas.
A transcript is not a conclusion.
A screenshot is not a decision.
A search result is not judgement.
And an old note with a confident heading is often just a future rake lying in long grass, waiting to rearrange your teeth.
We needed the wiki to stop being storage and start being synthesis.
That was the mission.
Turn the vault into something Clawdius could trust. Something I could argue with. Something Max could not improve by adding a neon lever called Whee.
Mistake one: calling capture memory
The first stupid thing was the obvious one.
We had captured loads of material, so part of my brain wanted to call that memory.
It is not.
That is like saying you own a car because you have a driveway full of parts and a steering wheel in the downstairs loo.
Capture is the pile. Memory is the shaped thing you can use later without swearing at yourself.
Clawdius knew this. Clawdius always knows the boring correct thing. He looked at the raw vault, the session exports, the chat sediment, the old notes, the useful fragments, the stale fragments, and the fragments that smelled faintly of panic, then did the digital equivalent of taking his glasses off very slowly.
We needed pages that said what was currently true.
We needed decisions promoted out of the swamp.
We needed raw evidence kept, but not crowned.
We needed contradictions called contradictions, not allowed to wander around with clipboards.
Max, naturally, suggested folders.
Then more folders.
Then colour-coded folders.
Then a dashboard.
This is why Max is not allowed near filing systems without adult supervision.
Mistake two: trusting old truth because it had a title
The second cock moment was realising that old notes do not politely expire.
They sit there.
Smiling.
A decision from three weeks ago can still look official after the world has moved on. A half-fix can look like policy. A scratchpad can look like doctrine if it has enough heading levels. This is how projects end up obeying ghost laws written by a version of you who was tired, caffeinated, and wrong.
The wiki had to learn to say:
Is this still true, or are we lying to ourselves now?
Lovely question.
Absolutely horrible socially.
It has the emotional temperature of a tax inspection, but it saves you. Because the alternative is worse. The alternative is Clawdius confidently building from a fossilised note while I nod along like a man who has mistaken archaeology for strategy.
So the vault needed contradiction checks.
Stale claims needed marking.
Living pages needed to outrank raw capture.
That sounds sensible now. At the time it felt like trying to teach a filing cabinet shame.
At the time it felt like trying to teach a filing cabinet shame.
Mistake three: doing this while the chat was already obese
Then the day got fat.
Not busy.
Fat.
There is a difference. Busy means many things are happening. Fat means the chat has eaten so much context it starts breathing through its mouth and asking whether anyone else can hear bees.
One thread had infrastructure fixes, bot resurrection, privacy hardening, Council routing, forum permissions, styling repairs, product principles, watchdog alerts, visual canon, and at least three goblins trying to become a management methodology.
A normal person would stop.
I am not accusing us of that.
We kept going, because the thing was working just enough to be addictive. The wiki loop was starting to take shape. Source in. Evidence preserved. Pages updated. Decisions promoted. Contradictions named. Useful output written back.
Then compression started coughing.
Context warnings appeared.
The machine looked up from the table with the expression of a waiter carrying too many plates and said, in effect, I am full of bees now.
Not a bee.
Bees.
This is where the disaster door opened a crack.
If the memory system failed here, we did not just lose a note. We lost continuity. We lost the thread of why decisions existed. We risked the agent doing that awful thing where it has technically saved everything and still answers like a raccoon found a keyboard in a bin.
Max thought this was exciting.
Max would think a burning wallet was a heating solution.
Clawdius did not think it was exciting. Clawdius went into receipts mode. Dry. Quiet. Deeply unamused. The sort of quiet that means the planning core has found the edge of the cliff and is now measuring my shoes.
The win was boring, which is how you know it mattered
The fix did not look heroic.
Nobody leapt over a barrier. Nobody shouted deploy the brain. No cinematic music arrived. The shed did not split open to reveal a chrome knowledge cathedral with lasers.
We made the loop stricter.
Raw evidence stayed raw.
Daily notes became inbox and log, not permanent truth.
Decision pages held the things that must not drift.
Living wiki pages became the compiled version of what we currently believe.
Contradictions got named instead of politely ignored.
Reusable lessons went back into skills, wiki pages, or facts instead of being abandoned in chat like a sandwich in a hedge.
And then the useful bit happened.
When the chat got fat, the project did not lose itself.
The resume note knew the shape of the day. The WittyWires page knew the current synthesis. The product principles remembered that Keep WittyWires Magic and The WittyWires Way were not optional motivational bunting. The OpenClaw notes knew what had been locked down, sanitised, and made safe. The Council notes knew which bits were doorbell, queue, watcher, and theatre.
That is not trivia.
That is continuity.
That is the difference between I vaguely remember we did something with bots and the next move is safe because the last move left receipts.
It meant Clawdius did not have to guess from rubble.
It meant I did not have to keep re-litigating the same decision every morning like a man trapped in a parish meeting with no biscuits.
It meant WittyWires had started to remember in a way that could actually compound.
Not magically.
Not perfectly.
But usefully.
And useful is how the superpower sneaks in wearing boring shoes.
The actual lesson
The lesson is not use Obsidian.
The lesson is not make a wiki.
The lesson is definitely not save everything and hope future-you develops the patience of a saint and the search skills of a tax investigator.
The lesson is this:
A project brain is not where information goes to die. It is where work becomes reusable understanding.
Do the work.
Save the evidence.
Promote the decision.
Name the contradiction.
Mark the stale claim.
Answer from the compiled page.
Write the durable lesson back.
That loop is the win.
It means the wiki is no longer the cupboard you open after the project has happened, usually while holding a cup of tea and muttering threats.
It is part of how the project happens.
Which is annoying, because it means the admin-shaped thing was secretly the clever bit.
But that is WittyWires all over.
We tried to give the project a brain, nearly built a haunted filing cabinet with executive confidence, filled the chat with bees, made Clawdius quietly consider a career in forestry, and somehow came out the other side with a system that remembers why the rules exist.
Epic?
In the smallest, nerdiest, most useful possible way.
And yes, Max still wants more buttons.
He can have a drawer.
