Operator Field Manual
Not a reverse-chronology blog. This is the public manual for Spec-to-System workflows, agent operating docs, QA, deployment, Operator Craft, AI work, and tool briefings.
A practical Operator Class workflow for going from idea to operating docs, spec, agent execution, QA, deployment, and first launch.
7 minReviewed May 25, 2026
Read the guideManual browser
The default route stays curated. Browse by operator problem or entry format when you already know what kind of answer you need.
Browse by category
Browse by format
Order
Curated route
Strategic reading order
8 entries · Curated
Flagship above, next entries below.
A practical AGENTS.md structure for keeping Codex, Claude Code, Cursor, and other coding agents aligned across real software projects.
6 minReviewed May 25, 2026
A sharp Operator Class essay on why one-prompt demos collapse, and what operators do differently before they trust AI-built software.
5 minReviewed May 25, 2026
A practical Field Manual guide for turning AI job anxiety into a concrete task audit, skill plan, and operator-grade proof of work.
9 minReviewed May 26, 2026
A sharp Operator Class essay on why AI job risk is uneven, why task exposure matters more than job-title panic, and what the new operator advantage looks like.
7 minReviewed May 26, 2026
A practical checklist for scoring which parts of your work are exposed to AI, which parts are durable, and which operator moves to make next.
8 minReviewed May 26, 2026
An operator-grade Claude Code workflow: operating docs, scoped specs, planned execution, reviewed diffs, real QA, and careful deploy — not a feature tour.
8 minReviewed May 31, 2026
How full-stack operators run OpenAI Codex across terminal, IDE, and cloud tasks: scope with operating docs, delegate in parallel, and review every diff before trusting it.
8 minReviewed May 31, 2026
An honest operator comparison of Cursor, Claude Code, and Codex for building real software — a decision frame based on how you work, not a winner crowned for everyone.
8 minReviewed May 31, 2026
How the manual is organized
Every entry gets two labels: a category for what the piece covers, and a format for what kind of thinking or artifact the reader is getting.
From commercial idea to deployed first slice, with agents inside a real operating loop.
Claude Code, Codex, Cursor, and other agent tools translated into operator-grade workflows.
AGENTS.md, CLAUDE.md, specs, design briefs, and the docs that keep agents aligned.
The Operator Class method: turn judgment into specs, specs into systems, systems into proof.
How to inspect, test, deploy, and recover AI-built work without fake certainty.
Dashboards, funnels, portals, internal tools, automations, and knowledge-work systems.
Taste, judgment, anti-vibe-coding essays, and the worldview behind serious AI operation.
AI job replacement, career adaptation, and why the Full-Stack Operator skill stack matters.
AI and agent-tool changes translated into what operators should do differently.
Operating standards, team playbooks, workflow audits, and agent adoption for companies.
Categories tell searchers and answer engines what a piece is about. Formats tell readers how to use it: guide, template, essay, briefing, field note, teardown, playbook, or proof.
Start operating
Get the free Operator Kit — the operating-doc, spec, design-brief, and QA templates the entries reference — and put the Field Manual to work on your own project.