// Track

Automation

Pipelines That Run Themselves

Build content flywheels, cron-AI pipelines, model routing, and git-based deployment — systems that produce output while you sleep.

9 lessons~83 min total

Lessons are shown in recommended order. Complete them in sequence for the best experience — or jump to any lesson.

Lesson 5·9 min read

Claude Code: The Coding Agent That Ships Product

Claude Code is not autocomplete. It reads your entire codebase, writes tests, runs them, iterates until green, and opens the PR — without hand-holding. Here is how to harness it.

Lesson 7·9 min read

The Content Flywheel: Automated Research to Multi-Platform Publishing

Content creation is a bottleneck that kills builder brands. The fix is not writing faster — it is pipeline-izing every stage so AI handles synthesis and you handle strategy.

Lesson 8·8 min read

The Cron-AI Pattern: Script First, AI Last

Using LLMs for structured data operations is like hiring a surgeon to take your blood pressure. The cron-AI pattern fixes this.

Lesson 9·8 min read

Model Routing: The Art of Using the Right Intelligence

Routing everything through your most powerful model is like sending a Navy SEAL to pick up your dry cleaning. Right asset, wrong mission.

Lesson 20·9 min read

Git as Your Universal Deployment Pipeline

Git is not version control. In an AI operating system, it is the universal delivery mechanism for everything — code, content, config, data. The PR is not bureaucracy. It is the unit of work.

Lesson 23·9 min read

LLM Cost Discipline: The Budget Model for AI Operators

Most AI builders have no cost model. They run until the bill arrives. If you are operating a production AI system without daily budget gates, you are not running a platform — you are running an open billing account.

Lesson 31·10 min read

Event-Driven vs. Polling Architecture: Why Your Data Is Always Stale

A polling system checking every 5 minutes is guaranteed to be wrong for 4 minutes and 59 seconds of every cycle. Event-driven systems respond in milliseconds. That gap is where alpha lives.

Lesson 32·11 min read

Provider Failback Chains: Never Block on a Single Dependency

Your image generation uses one provider. That provider goes down. Your content pipeline stops. Your blog doesn't publish. The failback chain pattern makes sure that never happens.

Lesson 33·10 min read

Content Frontmatter as Contract: The Three Layers of Verification

File committed plus frontmatter field set does not equal content renders correctly. These are three separate verifications. Missing any one is an invisible failure.