Tools / 13 min read
What If the Whole Computer Changed Faster Than You Could Hack It?
What happens if we stop trying to make software impossible to understand, and instead make what an attacker understands expire before they can use it?
The Brainn.dev blog
Notes from
the workshop.
Play a game. Make something useful. See what went into it.
Follow with RSSGuides & development notes
Find your next read.
8 articles in Tools
Tools / 3 min read
Neuron is the system. Orion is the agent.
Giving the agent a name clarified a larger design question: who owns the work when a conversation ends?
Tools / 3 min read
Teach the team to own the workflow
Brainn for Business starts with one repeated task, a result people can check, and a team that knows how to run it again.
Tools / 3 min read
When the hooks block the repair
A terminal cascade exposed a hard requirement for our agent harness: recovery has to work when the normal execution path is blocked.
Tools / 4 min read
The page had content. Navigation made it disappear.
Brainn.dev's Work and Research lists exposed a state ownership bug that a direct page load could miss.
Tools / 4 min read
Stop the command. Keep the terminal.
Neuron's terminal work exposed a small but consequential distinction between ending an operation and turning off a capability.
Tools / 4 min read
Make an editable workflow diagram with TurtlePen
Start with a real six-step example, reuse its prompt, and keep the editable drawing alongside the finished SVG.
Tools / 4 min read
A green check still needs a pair of eyes
Building TurtlePen's gallery showed why geometry checks, visual inspection and an editable source file each earn their place in the workflow.
Keep following the work
New notes, at your pace.
Follow new articles with RSS, choose weekly project updates, or try Daily Bites: one AI problem and one practical solution.