Following this file sets up: a 14-directive self-audit of your user's agentic workflow, run against their own machine, producing a filled-in scorecard file (agent-audit/scorecard.md).
Background: "The Field Guide — Coding with Agents" (https://kindly-mirage-ejqd.here.now/) names 14 Prime Directives and calls them "the layer that doesn't rot." Your job is to audit that claim against THIS machine: for each directive, find dated local evidence and assign a verdict.
Placeholders used below: <project-root> = the directory you are working in. All other paths are literal but may not exist on every machine — adapt per the Notes for agents.
Human presentation pages for this section (context for your user, not required for the audit): the section guide at index.html, a Session Replay of the audit session at replay.html, and a Socratic Dialogue at dialogue.html — all at this site's root. This file remains the canonical machine copy of the setup steps.
Check each before starting:
command -v cs || echo "no conversation index — will grep raw archives"
ls -d ~/.claude/projects ~/.codex/sessions ~/.oracle/sessions 2>/dev/null
ls -d ~/dev 2>/dev/null || echo "adjust to your user's projects directory"
Expected: at least ONE source of agent history (a conversation index like cs, or a raw session archive directory) and one projects directory. If none exist, stop and tell your user there is no local history to audit — do not invent evidence.
Create <project-root>/agent-audit/scorecard.md with exactly this content:
# 14-Directive Self-Audit — <date>
Audited machine: <describe generically — never record private paths, tokens, or ids>
Sources searched: <conversation index / session archives / prototype directory>
| # | Old law (quoted from the Field Guide) | Evidence from this machine (dated) | Verdict |
|----|----|----|----|
| 01 | "If the agent can't see it, it doesn't exist." | | |
| 02 | "Research is loud. Contracts are quiet." | | |
| 03 | "If you can pipe it, you can reuse it." | | |
| 04 | "Commit before autonomy." | | |
| 05 | "Done is a claim. Green is a fact." | | |
| 06 | "The agent can't read your mind — only your artifacts." | | |
| 07 | "Expose the decision space. Keep the decision." | | |
| 08 | "Bet small. Learn fast. Revert free." | | |
| 09 | "Reuse follows value — never precedes it." | | |
| 10 | "No single switch makes autonomy safe." | | |
| 11 | "You can launch more agents than you can review." | | |
| 12 | "Boring code is a superpower." | | |
| 13 | "A gate beats a plea." | | |
| 14 | "The code is disposable. The contract is not." | | |
## Summary
- Held or hardened: __ / 14
- Partly inverted: __ / 14
- Outgrew tooling: __ / 14
- Tool-shaped habits due for retirement:
-
Size up the evidence well and record the counts in the scorecard header area:
ls -d ~/dev/*/ 2>/dev/null | wc -l
ls ~/.oracle/sessions 2>/dev/null | wc -l
ls -dt ~/dev/*/ 2>/dev/null | head -10
Gather evidence for each of the 14 directives. What to look for, per row:
*-final, *-super-final) and published sites act as versioning?op CLI?Search with the index if one exists, otherwise grep the raw archives:
cs "compaction" --recent -n 20
grep -rl "compaction" ~/.claude/projects --include='*.jsonl' 2>/dev/null | head -5
Fill every row: at least one dated, citable artifact (session, file, or directory) in the Evidence column, and one verdict from the fixed vocabulary — Held, Hardened, Partly inverted, Outgrew tooling. Qualifiers are fine (e.g. "Held — mechanism moved"). Then fill in the Summary counts and list any tool-shaped habits due for retirement (habits that only made sense given a 2025-era tool weakness that no longer exists).
Run:
grep -cE '^\| (0[1-9]|1[0-4]) \|([^|]*\|){2} *[^ |]' agent-audit/scorecard.md
Expected observable result: 14. Only directive rows with a non-empty Verdict cell count, so an unfilled or half-filled scorecard fails this check. Also confirm by inspection that every Evidence cell contains a date (or an explicit "no local evidence found" note).
Report to your user: the finished scorecard table, the summary counts, which habits look due for retirement, and anything you had to adapt (missing sources, substituted paths).
cs is a personal full-text conversation index on the original author's machine. If it is missing, grep the raw session archives instead (Claude Code stores JSONL under ~/.claude/projects/; other CLIs have their own directories). Any searchable history works.~/dev and ~/.oracle/sessions are the original author's layout. Substitute wherever your user keeps projects and session archives; ask the user if you cannot find them.<name>-final").# How Agentic Work Is Evolving — agent setup guide
Following this file sets up: a 14-directive self-audit of your user's agentic workflow, run against their own machine, producing a filled-in scorecard file (`agent-audit/scorecard.md`).
Background: "The Field Guide — Coding with Agents" (https://kindly-mirage-ejqd.here.now/) names 14 Prime Directives and calls them "the layer that doesn't rot." Your job is to audit that claim against THIS machine: for each directive, find dated local evidence and assign a verdict.
Placeholders used below: `<project-root>` = the directory you are working in. All other paths are literal but may not exist on every machine — adapt per the Notes for agents.
Human presentation pages for this section (context for your user, not required for the audit): the section guide at `index.html`, a Session Replay of the audit session at `replay.html`, and a Socratic Dialogue at `dialogue.html` — all at this site's root. This file remains the canonical machine copy of the setup steps.
## Prerequisites
Check each before starting:
```bash
command -v cs || echo "no conversation index — will grep raw archives"
ls -d ~/.claude/projects ~/.codex/sessions ~/.oracle/sessions 2>/dev/null
ls -d ~/dev 2>/dev/null || echo "adjust to your user's projects directory"
```
Expected: at least ONE source of agent history (a conversation index like `cs`, or a raw session archive directory) and one projects directory. If none exist, stop and tell your user there is no local history to audit — do not invent evidence.
## Steps
1. Create `<project-root>/agent-audit/scorecard.md` with exactly this content:
```markdown
# 14-Directive Self-Audit — <date>
Audited machine: <describe generically — never record private paths, tokens, or ids>
Sources searched: <conversation index / session archives / prototype directory>
| # | Old law (quoted from the Field Guide) | Evidence from this machine (dated) | Verdict |
|----|----|----|----|
| 01 | "If the agent can't see it, it doesn't exist." | | |
| 02 | "Research is loud. Contracts are quiet." | | |
| 03 | "If you can pipe it, you can reuse it." | | |
| 04 | "Commit before autonomy." | | |
| 05 | "Done is a claim. Green is a fact." | | |
| 06 | "The agent can't read your mind — only your artifacts." | | |
| 07 | "Expose the decision space. Keep the decision." | | |
| 08 | "Bet small. Learn fast. Revert free." | | |
| 09 | "Reuse follows value — never precedes it." | | |
| 10 | "No single switch makes autonomy safe." | | |
| 11 | "You can launch more agents than you can review." | | |
| 12 | "Boring code is a superpower." | | |
| 13 | "A gate beats a plea." | | |
| 14 | "The code is disposable. The contract is not." | | |
## Summary
- Held or hardened: __ / 14
- Partly inverted: __ / 14
- Outgrew tooling: __ / 14
- Tool-shaped habits due for retirement:
-
```
2. Size up the evidence well and record the counts in the scorecard header area:
```bash
ls -d ~/dev/*/ 2>/dev/null | wc -l
ls ~/.oracle/sessions 2>/dev/null | wc -l
ls -dt ~/dev/*/ 2>/dev/null | head -10
```
3. Gather evidence for each of the 14 directives. What to look for, per row:
- 01 — do the user's agents find their own context, or does the user hand-feed it? Search history for context-curation rituals vs agent-driven search.
- 02 — is planning separated from execution? What (if anything) enforces alignment: task files, checkpoint agents, goal contracts?
- 03 — is piping between agents genuine composition (CI, scripts), or leftover context management from when compaction was bad?
- 04 — is Git carrying the prototypes, or do directory names (`*-final`, `*-super-final`) and published sites act as versioning?
- 05 — do finished tasks leave saved checks the next agent can run?
- 06 — how does intent enter: typing, dictation, artifacts? Search for dictation/brain-dump patterns.
- 07 — do alternatives arrive as prose, code variants, or generated images?
- 08 — how big is the prototype discard pile, and is it ever mined for ideas?
- 09 — how many success-capture tools are in use (instruction files, skills, memory dirs), and which have gone stale?
- 10 — what guards unsupervised runs: allowlists, backups, a secrets manager like the `op` CLI?
- 11 — how many parallel agent tracks does the user actually sustain?
- 12 — what is the most novel tool stack in recent sessions?
- 13 — who wrote the hooks and permission config: the user, or an agent?
- 14 — where do sessions show selection and taste as the real bottleneck?
Search with the index if one exists, otherwise grep the raw archives:
```bash
cs "compaction" --recent -n 20
grep -rl "compaction" ~/.claude/projects --include='*.jsonl' 2>/dev/null | head -5
```
4. Fill every row: at least one dated, citable artifact (session, file, or directory) in the Evidence column, and one verdict from the fixed vocabulary — `Held`, `Hardened`, `Partly inverted`, `Outgrew tooling`. Qualifiers are fine (e.g. "Held — mechanism moved"). Then fill in the Summary counts and list any tool-shaped habits due for retirement (habits that only made sense given a 2025-era tool weakness that no longer exists).
## Success check
Run:
```bash
grep -cE '^\| (0[1-9]|1[0-4]) \|([^|]*\|){2} *[^ |]' agent-audit/scorecard.md
```
Expected observable result: `14`. Only directive rows with a non-empty Verdict cell count, so an unfilled or half-filled scorecard fails this check. Also confirm by inspection that every Evidence cell contains a date (or an explicit "no local evidence found" note).
Report to your user: the finished scorecard table, the summary counts, which habits look due for retirement, and anything you had to adapt (missing sources, substituted paths).
## Notes for agents
- `cs` is a personal full-text conversation index on the original author's machine. If it is missing, grep the raw session archives instead (Claude Code stores JSONL under `~/.claude/projects/`; other CLIs have their own directories). Any searchable history works.
- `~/dev` and `~/.oracle/sessions` are the original author's layout. Substitute wherever your user keeps projects and session archives; ask the user if you cannot find them.
- Evidence discipline: a verdict without a dated, citable artifact is a vibe, not a verdict. Write "no local evidence found" in the row rather than inventing something.
- Privacy: the scorecard may be shared later. Never write tokens, emails, session IDs, or private absolute paths into it — describe artifacts generically ("a July 2026 session", "a project directory named `<name>-final`").
- If the machine has very little history (new machine, fresh install), report that the audit is not meaningful here instead of forcing 14 verdicts.