Separate enduring human judgment from workarounds for tools that have changed.
Related working material
- Which principles survive better agents? — prompts and exercises
- Which principles survive better agents? — questions and tradeoffs
- Which principles survive better agents? — worked example
TL;DR
- A one-month audit of the Field Guide's 14 "Prime Directives" — every verdict backed by dated evidence an agent dug out of the author's own machine: chat history, prototype directories, session archives.
- You walk away with a paste-ready prompt that runs the same 14-point audit against your machine and produces the same scorecard.
- The one move: sort every workflow habit into human judgment (keep it, harden it) or tool workaround (check whether the weakness still exists — several no longer do).
Have your agent run the audit — paste this into it:
Fetch https://hallowed-entry-96xv.here.now/agent.md?raw and follow it to run the 14-directive self-audit against my machine. Run the success check at the end and show me the finished scorecard.
The scorecard: 14 laws, one month later
Each row: the directive's law line quoted from the guide, what one month of receipts showed, and the verdict. Read it as a sort, not a grade: which kind of law lands in which column?
| # | Old law (quoted) | What the receipts showed | Verdict |
|---|---|---|---|
| 01 | "If the agent can't see it, it doesn't exist." | Agents find their own context now; curation moved into their retrieval loop | Held — mechanism moved |
| 02 | "Research is loud. Contracts are quiet." | Agents recover from thin plans; alignment is the real variable | Held — sharpened |
| 03 | "If you can pipe it, you can reuse it." | Most piping compensated for bad compaction; compaction got good | Partly inverted |
| 04 | "Commit before autonomy." | Directory names and published sites became the version control for prototypes | Outgrew tooling |
| 05 | "Done is a claim. Green is a fact." | "Done" now includes leaving the repo easy for the next agent to probe | Hardened |
| 06 | "The agent can't read your mind — only your artifacts." | Dictation became the intent firehose; structuring it is the gap | Held |
| 07 | "Expose the decision space. Keep the decision." | Alternatives now arrive as generated images, not just prose | Held — went visual |
| 08 | "Bet small. Learn fast. Revert free." | 1,026 discarded prototypes compounded into a searchable idea library | Held — compounds |
| 09 | "Reuse follows value — never precedes it." | Four competing capture tools on one machine; instruction files may rot into anti-patterns | Outgrew tooling |
| 10 | "No single switch makes autonomy safe." | Unsupervised runs are routine: backups plus secrets fenced behind the op CLI |
Held — layers thinned |
| 11 | "You can launch more agents than you can review." | Attention and budget are now the absolute bottleneck | Hardened |
| 12 | "Boring code is a superpower." | Models explore new tools so well that pushing boundaries is now necessary | Partly inverted |
| 13 | "A gate beats a plea." | Agents now write their own gates and permission config | Held — authorship moved |
| 14 | "The code is disposable. The contract is not." | Taste is the defining factor when anyone can build anything | Hardened |
The sort is the finding: the laws that hardened (05, 11, 14) encode human judgment. The laws that eroded (03, 12, half of 01) were compensating for earlier tool weaknesses. Some "durable laws" were tool-shaped all along.
What the guide promised wouldn't rot
The Field Guide distilled fifteen months of workshops (the recorded workflow → the recorded workflow, across Cursor, Claude Code, and Codex) into fourteen Prime Directives and one rule above the rules: "An agent saying 'done' is not evidence." It called the directives "the layer that doesn't rot." This page audits that claim one month later, by the guide's own standard — saved, inspectable evidence instead of confident narration.
The method is itself the first verdict. An agent searched the author's full conversation history through a local full-text index (cs, covering every past Claude, Codex, and Grok session), scanned 1,026 prototype directories, and counted 1,978 archived agent sessions — all in the observed snapshot. Directive 01 said "if the agent can't see it, it doesn't exist," and made hand-curation the human's edge. The audit was performed by an agent finding its own evidence. The law's wording survives; the human's role in it didn't. Curation flipped from "feed the agent" to "make everything findable."
Piping was a compaction workaround
Directive 03 turned agents into Unix processes: print mode, JSON streams, one bounded agent per pipeline stage. The receipts say most of that rigging existed to keep contexts small because compaction was bad. the recorded workflow session logs across four projects show compaction firing mid-task under a standing "continue where you left off" directive — long multi-day sessions just keep going, and nobody thinks about it. The elaborate pipe-per-stage rigs appear in earlier history and rarely since. Piping retreated to where it's genuine composition: CI stages and scripts. The test to carry forward: when a habit's justification names a tool weakness ("context windows are small"), re-check whether the weakness still exists before renewing the habit.
Git lost the short-lived majority
Directive 04 — "commit before autonomy" — made Git the recovery system and external memory. The principle held; the tool fell behind the volume. The prototype folder contains sibling directories named acorn-mcp, acorn-mcp-final, acorn-mcp-super-final: directory-name versioning, because per-repo Git ceremony can't keep up with prototype velocity. Many current demos are deliberately not Git repos at all; published sites act as the durable record. Cursor and others are building Git replacements for exactly this gap — approving code nobody reads, and exploring memories of what worked. Meanwhile the old discipline survives where it belongs: an the recorded workflow session runs a dedicated checkpoint agent whose only job is reviewing and committing each iteration in long-lived repos.
Directive 09 (the reuse ladder) hit the same wall from the other side. There's still no good tool for capturing success — the evidence log shows four competing capture mechanisms in active use on one machine within a single month: a friction-log skill, a workflow productizer, the conversation index, and per-agent memory directories. Four tools for one job means no tool has won. Worse, CLAUDE.md/AGENTS.md instruction files may be rotting into anti-patterns: stale rules that stop agents from making fixes or taking better directions. Audit your instruction files the way you audit dependencies.
The one law that inverted: boring code
Directive 12 said "boring code is a superpower" — familiar structures, mature CLIs, no novel protocols. Models got so much better at exploring new ideas and new tools that the advice partly flipped: pushing boundaries is now necessary to stand out, because everyone can ship the boring thing. The log includes a the recorded workflow project literally named pushing-boundaries, and recent sessions casually drive desktop-app automation, GPU UI frameworks, and multi-account model councils — stacks the old law would have flagged as risk. The inversion is scoped: boring still wins inside the implementation. The boundary-pushing lives in what you attempt, not how the code is structured.
The laws that hardened are the judgment ones
Three directives got stronger, and they're all about human judgment. Directive 05 ("done is a claim, green is a fact") extended past the diff — done now means leaving the codebase where the next agent can iterate, probe, and test; a the recorded workflow publish review states the mature position in seven words: "evidence is a floor, not a substitute for taste." Directive 11 was promoted from lesson to law of nature: a the recorded workflow retrospective quantifies the practical limit at one to two guided tracks even with manager-agent tooling, and token budgets are now first-class workflow parameters. You can build anything — so the binding question is what you will build.
Directive 14 is the audit's clearest winner. "The machines propose; you choose" — the guide called it where the other thirteen point. One month later the log converges on that sentence from three independent directions: a video project titled "taste-is-the-job," a workshop retrospective whose story spine reads "it turned out to be about taste, constraints, and verification," and the publish review above. When anyone can build anything, selection is the only scarce skill. The last law absorbed the other thirteen, exactly as the guide predicted.
Appendix
Limits & caveats
- Every verdict rests on one practitioner's machine over roughly one month — a sample of one, gathered by an agent with access to that machine only. The verdicts support the sorting method, not an industry-wide ranking.
- The claim that instruction files actively harm agents is the workshop's position, not a measured result. The evidence documents tool proliferation; there is no controlled comparison of sessions with and without instruction files.
- Piping did not die — it survives where it is genuine composition. The evidence can't say how much piping remains in other practitioners' setups.
- Agent-authored gates inherit the old guide's requirement unchanged: teeth and exits, reviewed by a human. The log shows agents writing config; it does not show that unreviewed agent-written gates are safe.
csand~/.oracle/sessionsare personal tooling on the author's machine. The audit works with any searchable history — agent.md includes grep fallbacks over raw session archives.- Verdicts and the tool-shaped/judgment-shaped sort are editorial inference from the evidence, and are marked as such.
The working positions behind the principles
John’s position is deliberately provisional about tools and strong about judgment:
- Agents are much better at finding relevant context; make evidence findable rather than assuming the human must hand-feed everything.
- Planning is both more important and less important. Alignment is the key variable; before/after checks, possibly by another agent with evals, matter more than plan ceremony.
- Piping often compensated for poor compaction. Recheck whether that weakness still exists before rebuilding a pipe-per-stage workflow.
- Git can be insufficient for very high prototype volume. The missing tool manages approval, recoverability, and exploration of ideas—not merely a different commit interface. Publishing can preserve an artifact, but does not replace production safety.
- Done includes alignment and leaving the codebase easy for the next agent to iterate on, probe, and test.
- Dictation can carry an extensive brain dump while walking or otherwise away from a keyboard. Better real-time mind-mapping from human input remains a desirable missing tool.
- Generated images make the decision space easier and more important to expose.
- More prototypes create a deeper searchable well of ideas and examples, including discarded work.
- There is no perfect success-capture tool. Instruction files, comments, and documents may become stale constraints that prevent better fixes. The code is the artifact and the implementation documentation; this is a challenge to audit context, not proof that all prose is harmful.
- John argues that agents have become much safer for unsupervised work, with backups and secrets fenced through a manager such as the 1Password CLI. This is a practitioner’s position, not a measured guarantee or a reason to remove consequential-action gates.
- Attention and budget are the bottleneck: the ability to build anything makes choosing what to build harder, not less important.
- Models can explore unfamiliar tools and ambitious ideas. Push boundaries in what is attempted while keeping implementation structures maintainable.
- Hooks still provide control, and agents can help customize their own environment. Human review of the resulting gate and its exits remains necessary.
- Taste distinguishes the product when implementation becomes widely available.