Operating Stack · how I direct AI
The layer that makes one operator run like a team.
The model is the engine. This is the operating system I run it with.
Everything else on this site — the repos, tools, cron jobs, architectures — is the output. This section is the method: a versioned operating doctrine, an execution register for the work that has to land, the hooks that keep both live automatically, and a live instrument that shows me exactly what every session costs and where it stands.
The four pieces
Operating doctrine
Eleven behavioral clauses I run the model against — versioned (NEXUS v14.2), injected into every session.
OpenThe Fable register
A frontier-execution mode for work where the finished quality is the whole deliverable.
OpenThe hooks
Five Claude Code hooks that keep the doctrine and register live — and the whole setup reproducible.
OpenThe status line
A seven-row live instrument: tokens, cache economics, spend, and limits, in one glance.
OpenWhy bother
A frontier model is only as good as the operator directing it. The gap between a chat and a shipped system is discipline — spec first, verify adversarially, never claim a result you didn’t observe. I encode that discipline once, in NEXUS v14.2 and a set of hooks, so it runs on every task without being re-typed. This is that layer.