All Stored in the Old Rust Crate
Two weeks of heat, halyards, a storybook promise, Behaviour OS, and the unnamed third system. A field note from the build.
Founder field notes by Mark Nicoll
Building complex software, AI systems, graph infrastructure, product architecture, and decision systems in slow-moving sectors.
Two weeks of heat, halyards, a storybook promise, Behaviour OS, and the unnamed third system. A field note from the build.
Thirty minutes, a local folder, a git repo, and fourteen videos. How I used Codex and Remotion to build the entire distribution infrastructure for Deployed Works before the site was live.
I built Deployed Works because modern teams often need deployable capability before they need permanent headcount.
A short, frustrating attempt to bring serious technology to UK defence procurement, and the structural reason brilliant people leave the sector before they ever get started.
Why a relational database gives you the trunk and nothing else, and what it takes to build something that can read across the wood itself.
A boring but useful breakdown of the hardware and tooling behind every Rust engine I build. People always ask. Here is the actual answer.
Why the same Rust engine can power six different health surfaces, and why nobody can copy the blueprint without having lived the context that produced it.
The night I negotiated a contract with Michael Jackson's creative team, drunk, with no brief and no authority. What I learned has driven everything since.
The Rust compiler does not care about your intentions. It cares about your precision. That is not a bug. It is the whole point.
Two near-deaths, a decade of being told nothing was wrong, and what I finally understood about how systems fail from the inside out.