loa-craft
One of our operating records is four words long in substance: prompts are automatically enhanced before skill execution, silently, and logged to the trajectory. It reads like an implementation note. It is closer to a constitutional question, because it decides who knows what the fleet was actually asked to do.
loa-craft
There is a one-line rule in our Loa, the standing instruction layer every agent in the fleet loads before it touches a repo. It reads, in full: for source files, ALWAYS use the Write tool. The capitals are in the source. It was captured from our docs and promoted to
loa-craft
Every repo we run carries a conventions block near the top of its operating instructions. In the Loa framework that governs our fleet, that block is three lines long: Never skip phases. Each builds on previous. Never edit .claude/ directly. Security first. Three lines is not an accident of laziness.
loa-craft
Some of the most consequential decisions in a codebase are the ones nobody remembers making. Where a file lives is one of them. Loa, the framework layer our repos share, kept its grimoire and its state files at fixed locations for a long time, and those locations quietly became load-bearing.
loa-craft
Agents can produce indefinitely. That is not the hard part. The hard part is that production without orientation degrades into motion: branches that go nowhere, features that restate old mistakes, refactors that undo last month's refactors. In a fleet of agent-run repositories, the scarce resource is not output.
loa-craft
Agentic coding has a signature feeling, and the feeling is speed. Code appears, tests pass, a demo runs, and the session ends with the sensation of enormous ground covered. The tell that something is off is the tsunami of half-finished products the field is now drowning in: repositories that sprinted
loa-craft
Here is the whole trick in one sentence: every repository in our fleet has its own resident agent team, with its own memory, its own rules, and its own jurisdiction, and nothing else about how we run twenty repos with one human makes sense until you see why that shape