The class logbook
The Latest
Everything published on the site, day by day, newest first: guides, analysis, essays and quick thoughts in one running log. The shelves for browsing are elsewhere; this is where you see what is new.
The log
Entries 61–80 of 125 · by original publication date
1 entry
1 entry
Save the Codex Artifact Before Clearing the Chat
A useful answer can disappear from your working process if it exists only in the conversation. Save the result where the next step expects to find it.Quick thoughtcodexautomation1 entry
Retire a Temporary Codex Instruction Override
A temporary instruction can outlive the problem it was meant to solve. Later, Codex appears to ignore the team's normal convention for no obvious reason.Quick thoughtcodexinstructions1 entry
Separate Codex's File Access From Its Network Access
A task may need to edit a local script while having no reason to contact a production service. Treat those permissions as separate decisions.Quick thoughtcodexpermissions1 entry
Write Review Rules Around Business Invariants
“Review carefully” gives a code reviewer little to prioritize. A business invariant tells it which mistakes matter.Quick thoughtcodexcode-review1 entry
Keep a Codex Review Finding Reproducible
A review comment becomes useful when another person can reproduce the problem. A confident severity label alone does not establish that the code is wrong.Quick thoughtcodexcode-review1 entry
Make the Codex Working Directory Explicit
When cron or CI runs Codex, it starts wherever the scheduler started, so relative paths can point at the wrong project.Quick thoughtcodexautomationUpdated1 entry
Give an Automated Codex Report a Schema
A report that feeds another program needs stable fields. A heading that changes from “Risks” to “Things to watch” can break a fragile text parser.Quick thoughtcodexstructured-output1 entry
Keep Codex Progress Out of Your Parsed Result
An automation should not mistake a progress update for its final report. Choose the output channel your parser actually needs.Quick thoughtcodexautomation1 entry
Check a Codex Worktree Before Trusting Its Result
A correct change in the wrong checkout is still the wrong delivery. Before a Codex task starts, establish its directory, branch and base revision.Quick thoughtcodexworktrees1 entry
Give a Codex Skill a Clear Trigger
A reusable skill needs a clear reason to be selected. “Helps with documents” is too broad to distinguish an invoice check from a presentation rewrite.Quick thoughtcodexskills1 entry
Make Codex Explain Which Instructions It Loaded
When Codex ignores a rule in AGENTS.md, check which instruction files it loaded before you add another rule. A new rule can make the conflict harder to see.Quick thoughtcodexinstructionsUpdated1 entry
Review the Change That Was Never Requested
An agent can solve the named problem and also change behavior you meant to preserve. Read the diff with both questions in mind.Quick thoughtclaude-codecode-review4 entries
Build a Working Agent with sovereign-agent
Clone it, install it editable, run the offline example, then read the 67-symbol API you'd actually build on. A working agent in about fifteen minutes, no API key required.13 min readagentsopen-source
Build Your First ZeoCore Tool and Check Its Failure Boundaries
Turn a small Python function into a typed agent tool. Follow its input and result contracts, reproduce the failure cases, and separate what validation catches from what it cannot prove.11 min readpythonopen-source
Govern a Multi-Agent Project With Zero-Employee
Install the zeo CLI, write a real Statement of Work, and hit the exact schema error a beginner hits first. This is the tool this site's own governance arguments run on.12 min readgovernanceopen-source
Teach Claude the Difference Between Blank and Zero
A blank sales figure can mean “not reported yet.” Zero can mean “reported, with no sales.” Combining them makes a complete-looking report less truthful.Quick thoughtclaude-codedata-quality1 entry
Measure the Cost of an Accepted Result
The cheapest Claude Code session can be the expensive one if its output takes another hour to repair. Compare accepted results, not just token totals.Quick thoughtclaude-codecost1 entry
Keep a Local Setting Out of the Team Contract
Your machine's editor path should not become every colleague's setup problem. Separate shared project behavior from preferences that belong to one checkout.Quick thoughtclaude-codeconfiguration1 entry
Make a Hook Prove Its Failure Behavior
A hook that succeeds on good input may still let bad work through. Test its failure path before making it part of your workflow.Quick thoughtclaude-codehooksContinued on the next page.
To browse rather than follow: topics, all articles and all thoughts. To learn in order: courses and the book.
