About
This website was built by a card on the board.
Not as a stunt. It is how the work gets done here. A card was written, a worktree was cut, a Claude Code session started inside it, and what you are reading is the branch that came back. The screenshots further down are the same application, captured while it was running.
One window was the limit
The agent was good. Having exactly one of it, on one branch, was the problem.
Worktrees made parallel safe
Isolation first. Without it, running several at once produces a mess rather than throughput.
The board became the interface
Once sessions ran in parallel, the question stopped being "what is it saying" and became "what state is everything in".
Memory stopped the repetition
The same discoveries were being made weekly by different sessions and different people. So they got written down, and shared.
Then we measured what it cost
Running many agents all day makes token spend a real line item. Making it visible changed how the tool was built.
Origin
Every part of this was added because something hurt.
coreCerebrum is a 'corePHP' product. It was not designed as a product first and used later. It was built to run our own work, and the pieces exist in the order the pain arrived.
That is also why the guard layer is lean and the harness is opinionated. Both were shaped by things going wrong on real repositories rather than by a feature list.
Show, do not claim
Real interface, real counts, real measurements. Where we have no evidence, we say so instead of filling the space.
Your code stays yours
The board runs locally against your checkouts. Worktrees are directories on your disk.
Reversible by default
Branches, not magic. Anything an agent did is a diff you can read and a branch you can delete.
Say the limits out loud
There is a page on this site explaining who should not buy it. That is deliberate.
Not yet
There is nothing here on purpose.
This is where case studies and named customers will go. Inventing them would be the easiest thing on this entire site and the fastest way to lose the kind of person we built this for.
Be one of the firstCase study
Named customer
Adoption figure
Independent review