Skip to content
SearchSubscribe
LEARN THROUGH PRACTICE

A little understanding.
Then put it to work.

Lessons in AI-assisted building, from the first instruction file to the systems that keep complex work on track.

71 published lessons
71 entries to exploreFrom the TruPath archive
LessonAI systemsFoundations

Your first CLAUDE.md

The instruction file your AI reads on every session. What goes in it, what doesn't.

10 min read · 20 min applyRead
LessonAI systemsFoundations

Your first MCP server

The 20-minute setup, the gotchas, when MCP beats writing a tool.

15 min read · 20 min applyRead
LessonAI systemsFoundations

Tool permissions and you

Allow vs ask vs deny — the model that prevents 90% of "wait I didn't mean that" moments.

12 min read · 20 min applyRead
LessonAI systemsOperating

Sprint contracts in practice

The contract format with three real examples — QC firmware, Parley research, MHG site search.

20 min read · 45 min applyRead
LessonAI systemsOperating

Test-first with agents

TDD with an LLM that wants to skip it. The 3 enforcement patterns that work.

18 min read · 45 min applyRead
LessonAI systemsOperating

Plan-mode discipline

Plan mode for senior operators. When to skip Plan, when to triple it, the exit ritual.

16 min read · 30 min applyRead
LessonBusiness operationsOperating

What public disclosure does to your patent rights

Pitch without an NDA, publish a write-up, prompt a consumer LLM — each can be a disclosure. The grace period, the foreign-filing trap, and what to check before anything goes public.

12 min read · 60 min applyRead
LessonAI systemsOperating

Decompression channels

A parallel technical project that restores focus to the main work instead of competing for it. How to tell if yours qualifies.

12 min read · 30 min applyRead
LessonAI systemsOperating

Skill-transfer adjacency

Picking a topic close enough to compound with the main work, far enough to feel like rest.

10 min read · 25 min applyRead
LessonAI systemsOperating

The "won't become a product" rule

Declare in writing, before starting, that the arm will not become a product. The declaration is what makes it survive.

10 min read · 20 min applyRead
LessonAI systemsOperating

When NOT to start an arm

Three conditions under which a second project is a distraction, not an arm. Honest about when I would have said no.

10 min read · 15 min applyRead
LessonAI systemsOperating

Scope rails for a research arm

Naming what you commit to NOT building, in writing, before starting. The Parley scope-rails block as the worked example.

10 min read · 30 min applyRead
LessonAI systemsOperating

Kaggle as a publishing loop

Using a public platform as the forcing function instead of a private repo. Why public is the discipline lever.

10 min read · 15 min applyRead
LessonAI systemsExpert

Scope creep prevention

The amendment protocol at scale. Refusing 'while we're in there' work. Without becoming an obstacle.

12 min read · 30 min applyRead
LessonAI systemsExpert

Multi-agent orchestration patterns

Beyond chief-of-staff routing: parallel-spawn, gather-then-merge, race-then-cancel. When each fires and when each breaks.

18 min read · 60 min applyRead
LessonAI systemsExpert

Production debugging playbook

When an agent misbehaves in prod: the diagnostic ladder. Five rungs from "claim says done but isn't" through context drift, tool failures, schema mismatches, upstream model regressions.

20 min read · 60 min applyRead
LessonAI systemsOperating

Reproduce the as-built model before you correct it

Two models that disagree tell you almost nothing until you can regenerate the one you are auditing. Reproduction converts ambiguous divergence into a named mechanism, and it finds defects before the correction work even starts.

12 min read · 30 min applyRead
LessonSimulationOperating

The simulator-label trap

Two models agreed on every trajectory to a hundredth of a foot and still flipped 48.3 percent of scored outcomes. Simulated states degrade gracefully; simulated labels fail all at once, right where the outcomes get interesting.

10 min read · 25 min applyRead
LessonAI systemsOperating

Run the sensitivity tornado before you measure anything

Friction swung our prediction 14.9 inches of a roughly 15-inch budget, three times the runner-up, and mass was noise. A one-afternoon sensitivity sweep turned the measurement wishlist into a spending plan.

10 min read · 40 min applyRead
LessonAI systemsOperating

Uncertainty budgets tell you which stage to distrust

The audit put ±2 inches of uncertainty on our flight prediction and ±15 on everything after contact. The failure lived in one stage, and a per-stage budget is what kept us from throwing away the stage that worked.

10 min read · 20 min applyRead
LessonAI systemsOperating

Research isn't done until the handoff brief is written

The QC physics audit produced runnable models, a dozen figures, and a stack of CSVs. The artifact that mattered three weeks later was none of them — it was a short brief written for the engineers who have to act on the findings.

10 min read · 25 min applyRead
LessonAI systemsOperating

Your domain intuition imports the wrong physics

We assumed spin mattered the way it matters on a golf ball. Priced in the same units, the borrowed mechanism was worth 3 inches and the real one 23, a 7× miss in which mechanism matters, caught in one afternoon before it spent our measurement budget.

10 min read · 20 min applyRead