Fourteen principles that held across three generations of agent tooling and fifteen months of churn. These carry no stamps — they are the layer that doesn't rot. Each opens with its law: the one-line version you'll actually remember at 2 a.m.
If the agent can't see it, it doesn't exist.
Agent quality is constrained by the relevance of the evidence it can see. Search results, files, examples, docs, diagrams, and previous decisions are the raw material of reasoning. And no — more is not better: irrelevant context consumes attention and invites drift. Find everything, then delete ruthlessly, and carry only the gold.
Arc · whole-repo bundles → hand-curated search packs → diagrams & task artifacts → bounded per-worker context
Research is loud. Contracts are quiet.
Research accumulates ambiguity, rejected ideas, and broad evidence — that's its job. But execution works better from a clean contract: the chosen direction, the constraints, and the proof requirements. Nothing else. Different contexts; sometimes different agents.
Arc · scaffold-then-outline habits → plan outside the implementation session → clean-session handoff → coordinator/worker contracts
If you can pipe it, you can reuse it.
Agents become dramatically more useful the moment they participate in normal program composition: print mode, stdin, JSON output, pipes, functions, child processes, CI. A conversation is a one-off; a process is infrastructure.
Arc · print-mode wrappers → structured streams & tool allowlists → script orchestration → specialist agents, hooks, coordinated lanes
Commit before autonomy.
Small commits make experiments reversible, preserve why, support independent review, and give the next agent a stable object to inspect. And hear this clearly: chat rewind does not restore repository state. The beacon trail behind you is the only path back that actually works.
Arc · safety checkpoints → worktrees & parallel isolation → commits as review boundaries and reasoning stamps
Chat rewind is not an undo button.— lesson learned the expensive way
Done is a claim. Green is a fact.
An agent's completion claim is not evidence. Tests, type checks, scripts, logs, diffs, screenshots, and browser receipts must be runnable or inspectable outside the conversation. Terminal form — the four words on the cover: no saved check, no claim.
Arc · "agents without tests are dangerous" → independent review & stop hooks → proof scenarios and saved receipts
The agent can't read your mind — only your artifacts.
If intent exists only in your head, the agent must guess — and it will guess confidently. Dictation, examples, plans, diagrams, acceptance criteria, constraints, and explicit non-goals transmit the actual design problem instead of a lossy summary of it.
Arc · spoken step lists → task files & diagrams → durable contracts, goals, proof surfaces
Expose the decision space. Keep the decision.
Ask for meaningful variation, then exercise human taste. The Rule of Threes, persona reviews, council setups — all the same move. Three advisors with different temperaments will disagree; that disagreement is the product.
Arc · "give me three options" → independent persona lenses → councils → one-variable-per-lane comparison with shared proof
Bet small. Learn fast. Revert free.
Prefer a cheap, reversible experiment over an elaborate speculative plan. State the hypothesis, run the smallest useful trial in a contained space, inspect the evidence — then discard it or promote it. One mitten stays on the reset switch the whole time.
Arc · ad-hoc try/fail/learn → branch-isolated experiments → explicitly disposable implementations tested against durable contracts
Reuse follows value — never precedes it.
A successful conversation may become a saved prompt, a shell function, a CLI wrapper, an agent, a skill, a hook, or a CI check. Climb one rung at a time, and use the lightest form that preserves the benefit. The top slot stays empty until it's earned.
Arc · aliases & functions → agent scripts → progressively-loaded skills → deterministic hooks and CI gates
No single switch makes autonomy safe.
Safety is a stack: bounded scope, allowlists, isolation, Git checkpoints, observable output, deterministic checks, stop conditions, human review. If you must run without safety checks, do it behind the blast glass — bounded, watched, reversible — never in the open.
Arc · permission prompts & allowlists → hooks & worktrees → recursion guards, visible lanes, preflight checks, saved proof
You can launch more agents than you can review.
Parallel agents multiply review obligations faster than they multiply trustworthy output. Parallelism pays when ownership is disjoint, results are comparable, and you can still evaluate them. Otherwise it manufactures merge conflicts and hidden review debt. Point the scope at the flare; let the steady beacons run.
Arc · fan-out enthusiasm → one or two supervised tracks → coordinator/worker roles with controlled variation
Parallelism multiplies review faster than it multiplies output.— the wall every orchestration era hits
Boring code is a superpower.
"Just code normal" and "prefer mature CLIs over novel protocols" are the same principle: familiar structures give humans and models stronger priors, and shrink the custom explanation you must haul around in context.
Arc · official scaffolds & real examples → conventional application code → custom protocols only for genuinely new capability
A gate beats a plea.
Optional expertise belongs in instructions. Mandatory invariants belong in deterministic controls. A skill can explain how to work; only a hook or CI check can physically prevent an invalid result from being accepted. Watch the two lanes: the barrier stops its robot. The polite hologram gets rolled straight past.
Arc · prompt reminders → lifecycle hooks → stop gates, routing hooks, persisted verification
The code is disposable. The contract is not.
Generated code may be cheap; requirements, taste, decisions, and proof are not. The lasting asset is the system that lets implementations be regenerated, compared, and verified without losing intent. When every option is plausible, the final instrument is taste — the machines propose; you choose.
This is where the other thirteen point.
Arc · plans & task files → diagrams & decision artifacts → goals, coordinator context, proof scenarios, receipts
fourteen laws // zero stamps required