Building the operating system for agentic engineering.
AI tools are easy to adopt. The operating models around them are the hard part. This is a working record of the architecture, governance, and engineering patterns for humans and agents building software together.
Most of the conversation is about adoption: which tool, which prompt, which model. That's the easy 20%. The other 80% is operating-model work: how delivery changes, how roles move, how you govern agents you can't fully predict, and how any of it survives contact with a real engineering org. That's what this site is about.
A factory, not a Frankenstein machine.
Hekton is my personal agentic engineering operating system, a factory for running multi-agent software projects with real structure: a taxonomy, agent contracts, governance, durable context, and reproducible build workflows. The patterns here aren't theoretical. They run.
Field notes on the future of software delivery.
- The roles don't disappear. They move up the value chain.
- Governance stops being paperwork and becomes a delivery feature.
- Context, not code, becomes the architecture that's hard to get right.
Recent field notes.
Things I've built to find out.
Gremlins, a local LLM lab, a blog factory. Experiments that turn questions about agentic engineering into artefacts I can point at. Some graduate. Some get retired. A few quietly become load-bearing, which is its own kind of warning.
Hekton
A personal agentic engineering operating system: taxonomy, agent contracts, governance, durable context, reproducible builds.
Gremlins
Reusable agents that do the boring, load-bearing work: planning, review, sync, governance, momentum.
Local LLM Lab
Cost-aware model selection, routing, and LLM-as-judge evaluation. When local beats frontier.
Blog Factory
A content engine that turns project work into public writing without becoming a content mill.
Architecture leader. Builder by default.
I design engineering operating models, then build them to see if they hold. This site is the trail: the systems, the decisions, and what they mean for leading engineering in an AI-native world.
field note: tekton (τέκτων) is the Greek root for builder, the same root inside archi-tekton, master builder. The name is the job.
New field notes, occasionally.
No cadence promises, no growth-hacking. When I build something worth writing about, it lands here. Bring your own opinions about YAML.