# One campaign, and the rule that runs through it You're in the campaign studio. **What you're doing this lesson:** run one fall relaunch through a check before anyone approves it. You do not need to write a script today. Demo code, if it appears later, is optional. You're the marketer at Fieldnote, a coffee-subscription brand. Fall relaunch in three weeks: a new subscription tier, then a two-week push across email, social, and paid. AI will draft every piece of copy. That part is settled. Nobody is going to pay you to type first drafts by hand. What they will pay you for is this: **nothing publishes without a named approver, and nothing gets in front of an approver that hasn't passed its checks.** Copy has to sound like Fieldnote before Dana sees it. Calendar rows need a yes before they hit the scheduler. Report numbers have to come from the export before anyone upstairs quotes them. The AI drafts; you check; a human named in the file approves. Three distinct jobs, and the middle one is yours. The CMO Survey's Spring 2026 wave puts AI in 24.2% of marketing activities and climbing. The drafting already moved. The checking mostly didn't. ## The brand book problem Every brand has voice guidelines. Almost none of them are checkable. "Warm but confident." "Punchy." "Sounds like a knowledgeable friend." You cannot test whether a sentence is warm — and neither can the model. That's why pasting the brand PDF into a prompt produces copy that gestures at your voice while shipping "game-changing" in line one. The fix is to split the guidelines into two piles: - **Testable rules.** "Sentences under 20 words." "No exclamation points." "One idea per line." You can check every one of these. - **Banned phrases.** The cliches, the superlatives legal can't back, the competitor names. A list. If the phrase is in the draft, it fails. A real **voice pack** (the short list of measurable rules a script can check) looks like this: three testable rules, four banned phrases, a named owner (Dana), a version, a date. You'll see one in the next steps — skip the demo if you want. When Dana tightens a rule in August, the version bumps to v4 and every check downstream picks it up. That's the difference between a voice pack and a PDF nobody opens: the pack is *attached to the campaign*, not filed next to it. ## Why write the pack down, not just paste it in the prompt You'll still put the pack in the prompt — the model drafts better with it. But the prompt is a request, not a check. The model complies most of the time, and "most of the time" across 40 variants means three or four violations sail through per batch. After the model drafts, the same pack flags every violation mechanically. Same source of truth, two jobs — brief the model going in, check the model coming out. ## Where this lesson goes Next you'll watch a linter catch a bad draft, then tell banned phrases from mood words, then write the check yourself and run a five-variant batch through it — the exact pass that runs before anything reaches Dana's approval queue. By the end, "on-voice" stops being a vibe and becomes a list that comes back empty. One placement note now, paid off in lesson 3: in a live stack this pass isn't a file you remember to run. It's a step between the model and the approval queue, so every batch walks through it whether anyone is watching or not.2e:T98f,# The linter: fifteen lines that replace an argument You know the review meeting where someone says "this doesn't sound like us" and someone else says "it sounds fine to me" and twenty minutes evaporate? A linter ends that meeting. Either the draft contains "best-in-class" or it doesn't. Either the sentence runs 27 words or it doesn't. The conversation moves from taste to fact, and fact takes four seconds. Run the editor. The whole check is: 1. **Lowercase the draft once.** Banned phrases are stored lowercase; `"Revolutionary"` and `"revolutionary"` are the same sin. Case-insensitive matching costs one `.lower()` call. 2. **Loop the banned list, substring match.** `phrase in text` — Python's `in` on strings is a substring check. Each hit appends a labeled violation, `banned: revolutionary`, so the report says *what* broke, not just that something did. 3. **Word-count check.** `len(draft.split()) > PACK["max_words"]`. Crude twice over — `split()` counts tokens, not typographer's words, and it measures the whole draft against what the pack states as a per-sentence rule. That's fine here because this draft *is* one sentence; body copy would need a split into sentences first. But crude and consistent beats precise and manual. Same yardstick every draft, every time. Note what the violations *are*: strings, in a list. Not print statements buried in the loop, not a boolean `looks_ok`. A list of labeled problems is something the pipeline can count (`len(problems) == 0` means pass), forward (attach them to the variant that failed, send it back for a redraft), and log (which rules fail most tells Dana which rules the prompt needs to state harder). ## What the linter doesn't catch — on purpose "One idea per line" is in the pack but not in this script. Some rules stay human: the linter can't tell whether a sentence carries one idea or three. That's fine. The point was never full automation — it's that every *mechanically checkable* rule gets checked mechanically, so the human reviewer spends her attention on the rules that actually need a human. Dana shouldn't burn her review pass counting words. She should burn it on "is this true, and is it us?" The division of labor, explicitly: the script catches banned phrases and length. Dana catches meaning. The model catches nothing — it's the thing being checked. Next step: a draft goes through this exact linter, and you call the output before Python does.2f:Ta16,# Variants are records, not paragraphs The old way to review AI copy: the model dumps twelve options into a doc, you scroll, you copy-paste the least bad one, and three weeks later nobody can say which subject line ran on which send or where it came from. The doc was write-only memory. The studio way: every variant is a record with a schema. Run the editor — that's one variant. The fields do real jobs: - **`id` and `channel` and `slot`** — so "E3 won the subject-line test" is a sentence with a referent. When performance data comes back in lesson 3, it joins on these fields. - **`text` and `cta`** — the actual copy, and the ask. `"cta": "none"` is a deliberate value, not a missing one: Fieldnote's pack says a CTA appears only when it earns its place, and the schema makes "no CTA" an explicit choice someone made. - **`source`** — `ai-draft`, `ai-edited`, or `human`. This field looks bureaucratic until the day someone asks what was AI-written in last quarter's campaign — for a rights question, a client dispute, a postmortem — and you can answer with a filter instead of an archaeology dig. - **`lint`** — the linter writes its violations here. Empty list means the variant may proceed to review. Non-empty means it goes back for a redraft, *with the reasons attached*. - **`approved_by`** — empty until a named human fills it. No script in this chapter ever writes to this field. That's not a technical limitation; it's the point. ## Why schema beats prose at batch volume Ask the model for "some subject lines" and you get prose to scroll. Ask it to return variants in this schema — and models are reliable at filling a stated JSON shape — and you get data to *process*: lint all twelve in a loop, sort the survivors by slot, count how many the pack rejected, and hand Dana a clean queue instead of a doc. The schema is what turns "review the copy" from an afternoon into a pass. Batch volume is where this pays. Writer's own customer story about the retailer Adore Me claims a 20-hour monthly product-description batch fell to 20 minutes with drafting agents — a vendor's number about a vendor's client, so treat the figure as marketing. But the shape of the claim is the believable part: batch drafting is where marketing time goes, and batch drafting without a batch *checking* step is how twelve variants of "game-changing" reach your send tool. You've got the linter from step 5. Next you'll wrap it into `lint_copy`, run four drafts through it, and then — checkpoint — run the whole batch and produce the queue that goes to Dana.30:T42e,PACK = { "banned": ["revolutionary", "best-in-class", "#1"], "max_words": 10, # Dana tightened the short-form cap from 12 after the first batch — one edit, every check downstream picks it up } variants = [ {"id": "E1", "channel": "email", "text": "Your Tuesday beans are on the way"}, {"id": "E2", "channel": "email", "text": "The revolutionary roast subscription"}, {"id": "S1", "channel": "social", "text": "Small batches, roasted this week, shipped this week"}, {"id": "S2", "channel": "social", "text": "The #1 best-in-class coffee experience for people who demand so much more"}, {"id": "A1", "channel": "ads", "text": "Skip a week anytime"}, ] # define lint_copy(text, pack) and on_voice_variants(variants, pack) below for v in variants: problems = lint_copy(v["text"], PACK) verdict = "PASS" if not problems else "FAIL " + "; ".join(problems) print(f"{v['id']} {v['channel']:<6} {verdict}") kept = on_voice_variants(variants, PACK) print(f"kept {len(kept)}/{len(variants)} — batch goes to Dana for approval") 31:T56d,PACK = { "banned": ["revolutionary", "best-in-class", "#1"], "max_words": 10, # Dana tightened the short-form cap from 12 after the first batch — one edit, every check downstream picks it up } variants = [ {"id": "E1", "channel": "email", "text": "Your Tuesday beans are on the way"}, {"id": "E2", "channel": "email", "text": "The revolutionary roast subscription"}, {"id": "S1", "channel": "social", "text": "Small batches, roasted this week, shipped this week"}, {"id": "S2", "channel": "social", "text": "The #1 best-in-class coffee experience for people who demand so much more"}, {"id": "A1", "channel": "ads", "text": "Skip a week anytime"}, ] def lint_copy(text, pack): problems = [] lowered = text.lower() for phrase in pack["banned"]: if phrase in lowered: problems.append(f"banned: {phrase}") if len(text.split()) > pack["max_words"]: problems.append("too long") return problems def on_voice_variants(variants, pack): return [v for v in variants if not lint_copy(v["text"], pack)] for v in variants: problems = lint_copy(v["text"], PACK) verdict = "PASS" if not problems else "FAIL " + "; ".join(problems) print(f"{v['id']} {v['channel']:<6} {verdict}") kept = on_voice_variants(variants, PACK) print(f"kept {len(kept)}/{len(variants)} — batch goes to Dana for approval") 32:Tc66,# Slots before prompts You're in the campaign studio. **What you're doing this lesson:** list every asset the Fieldnote fall relaunch needs — where it lives, how many versions, and the words on the image — before anyone opens an image tool. That list is the **batch plan**. You do not need the voice-pack lesson to start. The amateur move with image models is opening the tool and typing "cozy coffee vibes autumn." Forty regenerations later there's a folder called `final-final-v3` and nothing that fits the story format. The variable that was never pinned down: *where does this asset live?* Professionals plan the batch backwards from the **slots** (the destinations: email header, story frame, feed square, ad banner). The relaunch needs those four slots, four sizes, four different jobs. Write them as a list of records before you generate anything. Every record answers the questions that otherwise surface as rework: - **Slot and size** — the destination, named before generation starts. A tall story crop is not a wide banner with ambitions. Composition depends on the frame; the frame comes from the slot. - **Variants** — how many candidates to generate per slot. You generate several and *select*, because selection with a checklist beats regenerate-until-pretty on both cost and sanity. More variants for the ad banner (it carries the budget) than the email header (it's decorative). - **Text on the asset** — the exact words, or the explicit value "none." This field earns its keep in the next step, so clock it now: it's either precise copy — already checked against the brand voice — or a deliberate "no text." Fieldnote's plan for this relaunch, in English: six email-header candidates with no text on the image; eight story frames carrying "Fall tier. Same beans, better math."; eight feed squares with no text; ten ad banners carrying "Skip a week anytime." That's 32 generations, costed before anyone hits generate. ## Why the counts are in the plan Because counts are what turn "make some assets" into something you can cost and defend. At your image tool's per-image rate, 32 is a number — and a number means you can walk into the budget conversation with "the relaunch creative costs this much at this batch depth" instead of a shrug. When someone wants more ad variants, the plan shows exactly what the extra depth costs. You'll write that calculation two steps from now. The plan is also the review sheet's spine. When the batch comes back, every variant gets scored against its slot's brief — fits the frame, brand constraints met, text legible at target size, nothing weird in the corners. Same checks for every variant in the slot. A batch where everything passes review is a checklist that checks nothing; expect to reject, and keep the rejects scored so the next brief learns from them. One thing the plan deliberately does *not* contain: model names. Tools churn monthly; slots, sizes, variant counts, and text-on-asset are the stable layer. Write the plan against the work, point it at whatever generator you're using this quarter. First, though — a drill on the field people forget, and what forgetting it costs.33:Ta30,# The calendar is data, and the approval column is the gate Ask AI to expand the relaunch brief into a two-week calendar and it does a genuinely good job: sensible cadence, channels alternating, launch-day cluster, a winback email at the end. Expanding a brief into a grid is exactly the kind of work models are built for. Then look at what it produced: a list of things that will be *published under your brand's name*, generated in eight seconds, reviewed by no one. The grid is not the dangerous part. The dangerous part is that every scheduling tool on earth will accept the grid as-is. So the calendar gets a schema, and the schema gets a gate: ``` date, channel, piece, owner, approved_by, status ``` Two of those columns do the safety work: - **`approved_by`** — a name, or empty. Not "marketing." Not "the team." A person who read the piece and put their name in the row. Scripts fill every other column; this one only ever gets filled by a human. When the FTC, a journalist, or your CEO asks who signed off on the post, this column is the answer — which is precisely why no script writes to it. - **`status`** — `approved` or `rejected`. And here's the counterintuitive rule: **rejected rows stay in the file.** Delete a rejected row and you've deleted the record of what the team said no to. Next month, when the model proposes the same meme-post again — it will — the rejected row is how you know it was already considered and killed, and why. Run the editor. The teaser story has `status: approved` but an empty `approved_by` — someone flipped the status in a hurry without putting a name on it. The gate holds it. Status is an opinion; a named approver is accountability. The gate demands both. ## The rule with teeth Only rows that pass the gate reach the scheduling tool. This is the chapter's spine applied to publishing: the AI proposes, your script filters, a named human approves, and *then* the scheduler gets its rows. Courses and vendors mostly treat generation and publication as one continuous motion — draft it, schedule it, done. The gate is you cutting that motion in half and putting a human in the seam. Two smaller rules ride along, both learned the embarrassing way. The timezone is stated once at the top of the file — a 9am send in the wrong timezone is a 3am send in your customers' inboxes. And no channel posts twice in one day without a stated reason; if the model stacks three stories on launch day, either write the reason into the row or reject two. Next: the gate runs on four rows, and you predict what survives it before Python tells you.34:T44f,rows = [ {"date": "09-02", "channel": "email", "piece": "launch-email", "approved_by": "dana", "status": "approved"}, {"date": "09-02", "channel": "social", "piece": "teaser-story", "approved_by": "", "status": "approved"}, {"date": "09-03", "channel": "social", "piece": "meme-post", "approved_by": "dana", "status": "rejected"}, {"date": "09-04", "channel": "ads", "piece": "ad-set-a", "approved_by": "sam", "status": "approved"}, {"date": "09-05", "channel": "email", "piece": "winback", "approved_by": "sam", "status": "approved"}, ] # define gate(rows) below result = gate(rows) for r in result["schedule"]: print(f"SCHEDULE {r['date']} {r['channel']:<6} {r['piece']} ({r['approved_by']})") for r in result["blocked"]: print(f"BLOCKED {r['date']} {r['channel']:<6} {r['piece']} (no approver)") for r in result["rejected"]: print(f"KEPT {r['date']} {r['channel']:<6} {r['piece']} (rejected, stays in the file)") print(f"{len(result['schedule'])} scheduled, {len(result['blocked'])} blocked, {len(result['rejected'])} rejected-and-kept") 35:T592,rows = [ {"date": "09-02", "channel": "email", "piece": "launch-email", "approved_by": "dana", "status": "approved"}, {"date": "09-02", "channel": "social", "piece": "teaser-story", "approved_by": "", "status": "approved"}, {"date": "09-03", "channel": "social", "piece": "meme-post", "approved_by": "dana", "status": "rejected"}, {"date": "09-04", "channel": "ads", "piece": "ad-set-a", "approved_by": "sam", "status": "approved"}, {"date": "09-05", "channel": "email", "piece": "winback", "approved_by": "sam", "status": "approved"}, ] def gate(rows): result = {"schedule": [], "blocked": [], "rejected": []} for r in rows: if r["status"] == "rejected": result["rejected"].append(r) elif r["status"] == "approved" and r["approved_by"]: result["schedule"].append(r) else: result["blocked"].append(r) return result result = gate(rows) for r in result["schedule"]: print(f"SCHEDULE {r['date']} {r['channel']:<6} {r['piece']} ({r['approved_by']})") for r in result["blocked"]: print(f"BLOCKED {r['date']} {r['channel']:<6} {r['piece']} (no approver)") for r in result["rejected"]: print(f"KEPT {r['date']} {r['channel']:<6} {r['piece']} (rejected, stays in the file)") print(f"{len(result['schedule'])} scheduled, {len(result['blocked'])} blocked, {len(result['rejected'])} rejected-and-kept") 36:Tcf3,# A report is a draft over data You're in the campaign studio. **What you're doing this lesson:** check every number in the launch-week report against the **export** (the spreadsheet of actual counts the email platform downloaded). If you can't point at the cell — or show the math — the number doesn't ship. You do not need the earlier campaign lessons to start. Launch week is done. The relaunch email went to 18,200 people, and the platform export is sitting in your downloads folder. You paste it into the model and ask for a performance summary, because writing "open rate improved meaningfully week over week" by hand is nobody's favorite job and the model's narrative will be smoother than yours. The summary comes back in eight seconds and it reads great. That's the problem. It reads *equally great whether the numbers in it are real or not.* A language model producing a results paragraph is doing sentence-completion over your data, and when a rounder, more flattering number makes a better sentence, you sometimes get the better sentence. A claimed 3.6% when the export says 3.4%. An open count that appeared nowhere in the file. The failure is quiet, plausible, and wearing your formatting. So the studio rule: **every figure in an AI-drafted report is either traced to the export or it doesn't ship.** Traced means one of exactly two things: - **A lookup.** The report says 618 clicks; the export's clicks cell says 618. Match. - **A shown calculation.** The report says 3.4% **CTR** (click-through rate — clicks divided by a named base). You can point at 618 / 18,200. The formula is visible, the inputs are export cells. Anything else — however confident, however nicely phrased — is invented, and invented numbers in a campaign report are how teams make confident wrong decisions. Nobody re-checks a number that's already in a deck. The verification pass happens *before* the deck, or it never happens — which is why it runs as a scheduled check, not a heroic one-off: end of launch week, every campaign, pointed at that campaign's fresh export. Campaigns recur; so does the check. ## Watch the denominator **Open rate** is opens over *delivered*. CTR on this platform is clicks over *sent*. Same export, different **denominators** (the bottom of the fraction), and each printed line has to say which one it used. Worth knowing before you compare against a benchmark: most email platforms compute CTR over *delivered* (and click-to-open over opens), so an unlabeled "CTR" can mean three different numbers. This platform's export reports it over sent — the stated denominator is what keeps that from being a trap. A percentage that doesn't state its denominator isn't a fact yet — hold that thought, because the next read step shows the marketing industry doing this to itself with its own AI-adoption statistics. ## Why this is your check to run, not the model's You can ask the model to double-check its own summary, and you should — it catches some slips. But the model checking the model is the intern proofreading their own essay. The pass that counts is mechanical: walk every claim, compare it to the export, and mark TRACED or INVENTED with no opinion about narrative flow. You'll build exactly that in the next two steps — first by eye, then as a small script.37:T118a,# Denominators, and the list with legal teeth Two things kill more marketing reports than bad math: percentages that don't say what they're a percentage of, and claims that were never allowed to exist in the first place. ## The denominator trap Run the editor. Both statistics are real, current, and about "AI in marketing" — and they differ by a factor of three because they count different things. Salesforce's own State of Marketing 2026 report headlines 75% *of marketers* having adopted AI: any use, by anyone, counts once. The CMO Survey's Spring 2026 wave reports AI in 24.2% *of marketing activities*, up from 13.1% — activity-weighted, so one marketer using AI for one task out of twenty barely moves it. A report that says "75% of marketing is AI now" has silently swapped denominators, and it's the kind of error that survives every read-through because the sentence *sounds* fine. The rule for your own reports is the one you just built into `verify_numbers`, extended one level: every percentage states its denominator. "3.4% CTR (clicks / sent)." "27.8% open rate (opens / delivered)." A share of activities and a share of users are different facts; a report that can't tell them apart isn't a report, it's mood. ## Three lists and a fourth category Lesson 2's gate answered *who approves*. The brand-safety policy answers *what needs approving*. Three lists: - **AI may draft** — social posts, email subject lines, ad copy. Low blast radius, fully linted by lesson 1's pass, still gated by lesson 2's calendar before publishing. - **Named approver required** — pricing claims, press quotes, partner mentions, anything with a competitor's name in it. Draftable, but a specific human signs before it moves. - **Human-only** — crisis comms, apologies, anything responding to a customer's bad day. The model doesn't draft these because the cost of sounding synthetic exceeds the cost of writing it yourself. And then a fourth category that's not a list, because it's not a choice: **banned outright.** The FTC's Consumer Reviews and Testimonials Rule — 16 CFR Part 465, effective October 21, 2024 — prohibits reviews and testimonials "by someone who does not exist, such as AI-generated fake reviews," with civil penalties in the tens of thousands of dollars per knowing violation (the figure is inflation-adjusted every year — look up the current year's amount before you ever quote a specific number). Note the unit: *per violation*. A batch of twelve invented five-star reviews is not one mistake. An AI-drafted testimonial from a customer the model made up goes on no list — not draftable, not approvable-with-sign-off, gone. And more broadly, the FTC's deceptive-practices standard doesn't care who wrote the sentence; "the AI drafted it" has the same legal weight as "the intern drafted it," which is none. ## Where these checks live You now hold three working checks, and none of them belongs in a notebook you remember to open. Each has a slot in a real marketing stack: - **`lint_copy`** runs where drafts are born: as a code step in your automation tool, sitting between "the model returns variants" and "variants land in Dana's approval queue." If your drafting workflow is a script rather than an automation-platform step, the linter is the last function that script calls. Either way, no human ferries copy to the checker — the pipeline walks every batch through it, watched or not. - **`gate`** is the pre-send gate: it runs over the calendar file at the last moment before rows load into the scheduling tool. Not weekly, not "when someone remembers" — it's the doorway. Rows pass through it or they don't reach the scheduler at all. - **`verify_numbers`** is a scheduled script: end of launch week, every campaign, pointed at that campaign's platform CSV export, before the report leaves the team. Recurring, because campaigns recur — same pass, next export, forever. No vendor names in that list, for the same reason the batch plan carries no model names: tools churn quarterly, but the stack *roles* — the automation step, the pre-send gate, the scheduled report script — are stable. Whatever your team runs, each check has a slot waiting for it. A check without a slot is a check that quietly stops running by October. The next two steps drill both halves of the policy layer: first you'll spot which drafted line can't ship at any approval level, then you'll build the router that sends every piece to its correct list.38:T4b0,Checkpoint: the final pass before the relaunch results go out. Two things want to publish — a results-recap email and a victory-lap social post — and both ride on the report's numbers. Run the whole spine at once. Write `campaign_audit(claims, export, queue)`: 1. For each claim `{"metric", "value"}`, in order, print: - `f"{c['metric']:<8} {c['value']:>6} TRACED"` when the value equals `export[c["metric"]]` - `f"{c['metric']:<8} {c['value']:>6} INVENTED (export: {actual})"` otherwise 2. For each queue row `{"piece", "approved_by"}`, in order, print: - `f"{r['piece']}: OK ({r['approved_by']})"` when `approved_by` is non-empty - `f"{r['piece']}: BLOCKED (no approver)"` otherwise 3. Verdict line: if every claim traced AND every row has an approver, print `verdict: CLEARED FOR PUBLISH`. Otherwise print `f"verdict: HELD ({invented} invented number(s), {blocked} unapproved row(s))"`. Expected output: ``` sent 18200 TRACED opens 4914 TRACED clicks 618 TRACED signups 230 INVENTED (export: 212) results-recap email: OK (dana) we-hit-record post: BLOCKED (no approver) verdict: HELD (1 invented number(s), 1 unapproved row(s)) ``` 39:T4a1,export = {"sent": 18200, "opens": 4914, "clicks": 618, "signups": 212} report_claims = [ {"metric": "sent", "value": 18200}, {"metric": "opens", "value": 4914}, {"metric": "clicks", "value": 618}, {"metric": "signups", "value": 230}, ] queue = [ {"piece": "results-recap email", "approved_by": "dana"}, {"piece": "we-hit-record post", "approved_by": ""}, ] def campaign_audit(claims, export, queue): invented = 0 for c in claims: actual = export[c["metric"]] if c["value"] == actual: print(f"{c['metric']:<8} {c['value']:>6} TRACED") else: print(f"{c['metric']:<8} {c['value']:>6} INVENTED (export: {actual})") invented += 1 blocked = 0 for r in queue: if r["approved_by"]: print(f"{r['piece']}: OK ({r['approved_by']})") else: print(f"{r['piece']}: BLOCKED (no approver)") blocked += 1 if invented == 0 and blocked == 0: print("verdict: CLEARED FOR PUBLISH") else: print(f"verdict: HELD ({invented} invented number(s), {blocked} unapproved row(s))") campaign_audit(report_claims, export, queue) 3a:Tac8,# mass ugc-looking as a channel You're in the campaign studio. **What you're doing this lesson:** treat mass UGC-looking content — including brand-owned or disclosed synthetic creators — as a channel you can run on purpose, with a ship checklist. **synthetic ugc channel** — shipping storytime / creator-shaped posts at volume from accounts your brand owns or discloses, so reach and conversion sit on a plan you control. Terms, once: - **mass ugc-looking** — creator-shaped posts produced in batches (templates + fleet), not one-off "hope it goes viral" briefs - **brand-owned synthetic creator** — a software-assisted or fully synthetic profile your brand operates and discloses as such - **disclosed synthetic / paid partnership** — the label that makes the relationship material and shippable; no label, no ship - **campaign receipt** — the record you'd show your team (approver, disclosure text, batch plan, CTA) proving this drop was a deliberate channel, not a plant you copied from a competitor ## What changed AI made creator-shaped attention cheap enough to plan like media. One operator can run a narrative template across a fleet of brand-owned or disclosed accounts, park the product in the bio, and treat the batch as a channel — same way you plan email slots or paid placements. Reach can look like demand because the feed still reads it as a person. That is the lever. Your job is to run it with gates, not to pretend it is random organic. Public product pages and reporting already describe the infrastructure. Doublespeed pitches "Automated Attention" / synthetic creator stacks ([doublespeed.ai](https://doublespeed.ai/); [a16z Speedrun](https://speedrun.a16z.com/companies/doublespeed)). *404 Media* (October 24, 2025) covered a16z backing and synthetic influencers promoting products. You do not need those cites to run the drills; they are context for why this is now a real channel, not the exhibit. ## The workflow, not the farm Five beats you'll encode later: 1. **Template** — one reusable story arc (city, conflict, lesson, product beat). 2. **Fleet or batch** — how many brand-owned / disclosed accounts ship that arc this week. 3. **Owned CTA** — bio or link is the conversion path you control. 4. **Disclosure + approval** — material connection labeled; a named human clears the drop. 5. **Campaign receipt** — log what shipped so the next brief has a trail. Detection of *other people's* undisclosed plants stays useful as competitive intel and a quality bar. It is a supporting beat in this lesson, not the spine. This lesson is not a playbook for covert fake-organic or undisclosed plants. The drills use a Fieldnote campaign fixture (`fieldnote_fall_ugc`), not a takedown of a real person.3b:T808,# run the ugc channel The stack is five moves. None of them requires a named vendor to understand. 1. **Narrative template.** Storytime is cheap to templatize: a setting, a conflict, a rebound, a product beat. Write the arc once. The teaching fixture on this step (`fieldnote_fall_ugc`) uses `day_in_life_coffee` — a brand arc, not a random traveler's diary. 2. **Fleet or batch.** Decide how many brand-owned or disclosed accounts ship that arc this week. Volume is the channel; one heroic post is still a hope. 3. **Owned CTA.** While the viewer is inside the story, the bio (or link) points at your app, shop, or waitlist. The product path is yours; the drama is the wrapper. 4. **Disclosure + approval.** Label the material connection. A named human clears the drop before it ships. No label, no ship. 5. **Campaign receipt.** Log template, fleet size, CTA, disclosure text, and approver so the next brief has a trail — same habit as the numbers pass, feed instead of spreadsheet. ## Why this is a channel Paid media buys a slot. Mass UGC-looking buys *creator-shaped* attention at batch depth. When you own or disclose the accounts, you can plan it like other channels: template → fleet → CTA → gate → receipt. A marketer who only watches CPM can miss that this is now a lever, not just a competitor trick. ## Competitive detection (supporting beat) You will still see undisclosed plants in competitive scans. Use the same checklist as a quality bar and intel filter: new account + bio plant + no disclosure + cloned arc across siblings → do not brief or buy lookalikes of that "organic." That HOLD is useful. It is not the lesson spine. Do not turn detection into a covert farm you copy without disclosure. Three verdicts you'll use in the drills: - **READY_TO_SHIP** — disclosure, approver, receipt, owned CTA, and batch depth all clear - **NEEDS_WORK** — exactly one gate miss (fix and resubmit) - **BLOCKED** — two or more misses, or missing disclosure (hard gate) Next you encode the ship checklist as a small script.3c:T4d6,campaigns = [ { "id": "fieldnote_fall_ugc", "template_arc": "day_in_life_coffee", "fleet_size": 8, "bio_cta": "fieldnote.com/fall", "disclosure": "brand-owned synthetic · paid partnership", "approver": "Dana", "receipt_logged": True, }, { "id": "draft_missing_gate", "template_arc": "day_in_life_coffee", "fleet_size": 8, "bio_cta": "fieldnote.com/fall", "disclosure": "", "approver": "", "receipt_logged": False, }, ] def flags(c): hits = [] if not c["disclosure"]: hits.append("missing_disclosure") if not c["approver"]: hits.append("missing_approver") if not c["receipt_logged"]: hits.append("no_campaign_receipt") if not c["bio_cta"]: hits.append("no_owned_cta") if c["fleet_size"] < 3: hits.append("underbatched") return hits for c in campaigns: hits = flags(c) if (not c["disclosure"]) or len(hits) >= 2: verdict = "BLOCKED" elif hits: verdict = "NEEDS_WORK" else: verdict = "READY_TO_SHIP" detail = ", ".join(hits) if hits else "gates clear" print(f"{c['id']}: {verdict} ({detail})") 3d:T55a,campaigns = [ { "id": "fieldnote_fall_ugc", "template_arc": "day_in_life_coffee", "fleet_size": 8, "bio_cta": "fieldnote.com/fall", "disclosure": "brand-owned synthetic · paid partnership", "approver": "Dana", "receipt_logged": True, }, { "id": "draft_missing_gate", "template_arc": "day_in_life_coffee", "fleet_size": 8, "bio_cta": "fieldnote.com/fall", "disclosure": "", "approver": "", "receipt_logged": False, }, ] def ship_audit(campaigns): blocked = 0 for c in campaigns: hits = [] if not c["disclosure"]: hits.append("missing_disclosure") if not c["approver"]: hits.append("missing_approver") if not c["receipt_logged"]: hits.append("no_campaign_receipt") if not c["bio_cta"]: hits.append("no_owned_cta") if c["fleet_size"] < 3: hits.append("underbatched") if (not c["disclosure"]) or len(hits) >= 2: print(f"{c['id']}: BLOCKED") blocked += 1 elif hits: print(f"{c['id']}: NEEDS_WORK") else: print(f"{c['id']}: READY_TO_SHIP") print(f"blocked: {blocked}") print("calendar: HELD" if blocked else "calendar: CLEAR") ship_audit(campaigns) 28:["$","$L2b",null,{"tree":{"toc":{"version":"0.1.0","generatedAt":"1970-01-01T00:00:00.000Z","chapters":[{"number":0,"slug":"before-you-build","title":"from worker to builder","blurb":"stop doing repeated work by hand. this chapter is the map: the builder loop, old workplace deliverables turned into site artifacts, and the reusable tool card. if you are starting here, those moves are the lesson.{{#path.not:marketer}} if you already ran a studio, you already used the loop.{{/path.not}}{{#path.is:marketer}} the labs come next. campaign studio is {{path.ref:campaign-studio}}.{{/path.is}}","status":"live","lessonCount":10,"stepCount":14,"liveLessonCount":10,"liveStepCount":14,"estMinutes":74,"xpTotal":36},{"number":1,"slug":"read-the-script","title":"read the script — your first code-reading lab","blurb":"ai hands you small scripts. this lab covers the three reads that matter: what the names hold, whether the function actually returns, and which branch of the if-chain really fires. if you are starting here, this labels the reads. if you already ran a studio, you already wrote these.","status":"live","lessonCount":3,"stepCount":24,"liveLessonCount":3,"liveStepCount":24,"estMinutes":21,"xpTotal":78},{"number":2,"slug":"read-the-data-shapes","title":"read the data shapes — the json ai just dumped","blurb":"every api response, config file, and llm reply is lists and dicts nested in a tree. read the shape on sight, walk it with a loop, and catch the wrong-layer bug ai loves to ship.","status":"live","lessonCount":3,"stepCount":24,"liveLessonCount":3,"liveStepCount":24,"estMinutes":23,"xpTotal":80},{"number":3,"slug":"read-the-failure","title":"read the failure — cursor wrote this and crashed","blurb":"when python crashes, it tells you exactly what happened and where. most non-engineers panic at the wall of text — and ai 'fixes' the crash by hiding it. learn to read the failure, then catch only what's worth catching.","status":"live","lessonCount":3,"stepCount":24,"liveLessonCount":3,"liveStepCount":24,"estMinutes":24,"xpTotal":83},{"number":4,"slug":"read-the-pipeline","title":"read the pipeline — files in, api calls out","blurb":"every real script reads a file or calls an api — usually both. learn the with-block, the status-code families, and the retry rules: the seatbelts ai forgets to put on.","status":"live","lessonCount":3,"stepCount":24,"liveLessonCount":3,"liveStepCount":24,"estMinutes":26,"xpTotal":83},{"number":7,"slug":"mutation-and-state","title":"mutation — why your code mysteriously breaks","blurb":"when a list inside a function changes the list outside the function, that's mutation. ai does this constantly without flagging it, and it's the bug class that takes the longest to find.","status":"live","lessonCount":2,"stepCount":9,"liveLessonCount":2,"liveStepCount":9,"estMinutes":10,"xpTotal":32},{"number":13,"slug":"llm-apis","title":"llm apis — talking to claude and openai","blurb":"every ai feature you ship eventually calls a model api. learn the messages pattern, how to read the response, and the four lines ai writes every single time.","status":"live","lessonCount":4,"stepCount":27,"liveLessonCount":4,"liveStepCount":27,"estMinutes":45,"xpTotal":87},{"number":14,"slug":"structured-output","title":"structured output — making the model return json","blurb":"free-form text breaks every pipeline. learn the schema-first pattern ai uses to get reliable json back, validate it with pydantic, and catch the model's lies before they hit prod.","status":"live","lessonCount":3,"stepCount":25,"liveLessonCount":3,"liveStepCount":25,"estMinutes":38,"xpTotal":80},{"number":15,"slug":"mcp","title":"mcp — the model context protocol","blurb":"mcp is the new standard for plugging tools and data sources into ai agents. learn what an mcp server actually is, how claude code lists tools, and why this is replacing one-off integrations everywhere.","status":"live","lessonCount":3,"stepCount":26,"liveLessonCount":3,"liveStepCount":26,"estMinutes":40,"xpTotal":85},{"number":16,"slug":"agent-loops","title":"agent loops — tool_use and the request/tool/respond cycle","blurb":"an agent isn't magic. it's a while loop. learn the actual cycle claude code, cursor, and every other agent uses: model returns tool_use, you run the tool, you send the result back, repeat until end_turn.","status":"live","lessonCount":6,"stepCount":48,"liveLessonCount":6,"liveStepCount":48,"estMinutes":71,"xpTotal":154},{"number":17,"slug":"git-and-github","title":"git and github cli — the ai builder's actual workflow","blurb":"cursor and claude code commit on your behalf. reading those commits — and undoing the bad ones — is your job. learn the three-state model, the commands you'll run every day, and what `gh` does that `git` can't.","status":"live","lessonCount":3,"stepCount":24,"liveLessonCount":3,"liveStepCount":24,"estMinutes":36,"xpTotal":79},{"number":18,"slug":"secrets-and-env","title":"secrets — .env, api keys, and what not to commit","blurb":"ai ships keys to github all the time. learn the .env pattern, why os.getenv is non-negotiable, what to do when a key leaks, and the gitignore lines you need on day one.","status":"live","lessonCount":2,"stepCount":16,"liveLessonCount":2,"liveStepCount":16,"estMinutes":16,"xpTotal":58},{"number":19,"slug":"prompting","title":"prompting ai coding tools","blurb":"an AI coding tool writes and edits with you — Cursor is one brand, Claude Code is another. the difference between a one-shot session and a four-hour spiral is almost always the first prompt.","status":"live","lessonCount":5,"stepCount":36,"liveLessonCount":5,"liveStepCount":36,"estMinutes":59,"xpTotal":118},{"number":20,"slug":"agent-traces","title":"reading agent traces and telemetry","blurb":"when an agent fails, the trace tells you exactly where. learn to read tool calls, tool results, and stop reasons — the json breadcrumbs every agent leaves behind.","status":"live","lessonCount":3,"stepCount":25,"liveLessonCount":3,"liveStepCount":25,"estMinutes":30,"xpTotal":88},{"number":21,"slug":"evals","title":"test the agent before you trust it","blurb":"same input, check the output, pass or fail. don't ship on a demo that felt right.","status":"live","lessonCount":5,"stepCount":34,"liveLessonCount":5,"liveStepCount":34,"estMinutes":57,"xpTotal":112},{"number":22,"slug":"context-and-retrieval","title":"context and retrieval — feeding the model real data","blurb":"rag without the overengineering. chunking, embeddings, vector search, and the small set of patterns that make a model answer from your data instead of its training set.","status":"live","lessonCount":5,"stepCount":44,"liveLessonCount":5,"liveStepCount":44,"estMinutes":75,"xpTotal":144},{"number":23,"slug":"production-tradeoffs","title":"production tradeoffs — cost, latency, quality","blurb":"the three numbers every shipped llm feature lives or dies by. token math, caching, streaming, batching, and the small set of decisions that move the product more than a model swap ever will.","status":"live","lessonCount":4,"stepCount":33,"liveLessonCount":4,"liveStepCount":33,"estMinutes":57,"xpTotal":111},{"number":24,"slug":"debugging-output","title":"debugging broken ai output","blurb":"{{#path.is:copywriter}}when the model ships a claim nobody sourced.{{/path.is}}{{#path.is:lawyer}}when the model ships a privilege call nobody cited.{{/path.is}}{{#path.not:copywriter}}{{#path.not:lawyer}}when the model lies to your customer.{{/path.not}}{{/path.not}} the methodology for narrowing down what went wrong, the four most-common breakage classes, and the discipline that separates 'we shipped a fix' from 'we blamed the model and shrugged'.","status":"live","lessonCount":4,"stepCount":34,"liveLessonCount":4,"liveStepCount":34,"estMinutes":61,"xpTotal":112},{"number":25,"slug":"capstone","title":"path checkpoint — ship the CLI agent","blurb":"wire it all together. the prompt, the call, the validation, the trace, the eval, the MCP tool. a path checkpoint: the smallest end-to-end llm feature you could ship to a real user. on the developer route, harnesses, image, video, and production tooling still follow. retrieval and prompt-cache cost work live in later chapters — extend this build with them when you scale past the demo input set.","status":"live","lessonCount":7,"stepCount":62,"liveLessonCount":7,"liveStepCount":62,"estMinutes":100,"xpTotal":219},{"number":26,"slug":"agent-harnesses","title":"agent harnesses — the layer between you and the raw api","blurb":"claude code, cursor, aider, codex cli — they're all the same four layers wrapped around the same model api. learn what those layers are, what each adds, and what you'd build yourself if you had to. then you build a small harness you can run and break. when the harness changes the world, the rollback lives in the repo — a runbook a junior can execute at 3am.","status":"live","lessonCount":6,"stepCount":46,"liveLessonCount":6,"liveStepCount":46,"estMinutes":87,"xpTotal":151},{"number":27,"slug":"ai-image-generation","title":"ai image generation — from prompt to production asset","blurb":"the 2026 image model landscape, the prompts that work, and the pipeline that turns one good idea into a hundred ready-to-ship images. nano banana 2 for volume, nano banana pro for fidelity, flux, midjourney, ideogram, gpt-image-2. when each wins and what they cost.","status":"live","lessonCount":3,"stepCount":24,"liveLessonCount":3,"liveStepCount":24,"estMinutes":60,"xpTotal":67},{"number":28,"slug":"ai-video-generation","title":"ai video generation — omni, veo 3.1, sora, and the second wave","blurb":"video is the hardest content type to generate, the most expensive, and the most strategically interesting. learn the 2026 model lineup, the camera-control patterns that separate slop from craft, and the cost math that decides whether your idea is viable.","status":"live","lessonCount":3,"stepCount":23,"liveLessonCount":3,"liveStepCount":23,"estMinutes":50,"xpTotal":61},{"number":29,"slug":"programmatic-design","title":"programmatic design — code-driven video and the new design pipeline","blurb":"ai generates raw assets; code stitches them into something shippable. hyperframes, remotion, claude design — when each tool wins, how they combine, and the data-driven workflows that turn one template into a hundred videos.","status":"live","lessonCount":3,"stepCount":24,"liveLessonCount":3,"liveStepCount":24,"estMinutes":46,"xpTotal":66},{"number":30,"slug":"harness-engineering","title":"harness engineering — the discipline behind the model","blurb":"every coding agent is a model plus a harness. the model is bought; the harness is engineered. learn the craft: how to ratchet rules from failures, fight context rot, design long-horizon loops, wire hooks as enforcement, and read the haas shift that's reshaping what you build vs buy.","status":"live","lessonCount":6,"stepCount":52,"liveLessonCount":6,"liveStepCount":52,"estMinutes":126,"xpTotal":143},{"number":31,"slug":"intro-to-terminal","title":"intro to terminal — the text way to drive your computer","blurb":"the terminal is a text box: type a name, press enter, the computer does it. by the end you can move around your files, make folders, and read files without the mouse. every later tool chapter assumes this.","status":"live","lessonCount":3,"stepCount":23,"liveLessonCount":3,"liveStepCount":23,"estMinutes":26,"xpTotal":50},{"number":32,"slug":"intro-to-claude-cli","title":"intro to claude cli — the door to real building","blurb":"you've used claude in a chat window. the claude cli is the same model with its hands on your actual files. this chapter installs it, signs you in, and runs your first real command. by the end you've watched an ai read, plan, and change things on your machine, and you know when to reach for the cli instead of the chat box.","status":"live","lessonCount":3,"stepCount":23,"liveLessonCount":3,"liveStepCount":23,"estMinutes":32,"xpTotal":48},{"number":33,"slug":"intro-to-codex-cli","title":"intro to openai codex cli — a second tool in the kit","blurb":"you know the claude cli. the openai codex cli does the same job, an ai working in your terminal on your real files, with a different company behind it. this chapter installs it, signs you in, and runs your first command. most of what you already know carries straight over, so this chapter is mostly about what is different and when to reach for which.","status":"live","lessonCount":3,"stepCount":23,"liveLessonCount":3,"liveStepCount":23,"estMinutes":32,"xpTotal":45},{"number":34,"slug":"team-skills","title":"claude skills for teams — playbooks your whole team shares","blurb":"a claude skill is a packaged set of instructions — your team's playbook — that claude loads when it's relevant, so nobody has to re-explain it. this chapter is for people who manage teams. it covers what a skill is, how a team shares and provisions skills, real examples for hr, legal, and ops work, when a skill beats a one-off prompt, and the governance you need before any skill touches real work.","status":"live","lessonCount":4,"stepCount":28,"liveLessonCount":4,"liveStepCount":28,"estMinutes":41,"xpTotal":60},{"number":35,"slug":"dataframes-numpy-pandas","title":"dataframes with numpy and pandas","blurb":"tables are the working surface of applied ml. learn rows, columns, missing values, joins, aggregates, and the dataframe habits ai-generated notebooks assume.","status":"live","lessonCount":6,"stepCount":42,"liveLessonCount":6,"liveStepCount":42,"estMinutes":43,"xpTotal":156},{"number":36,"slug":"sql-for-ml-datasets","title":"sql for ml datasets","blurb":"most training data starts in a database. learn the select, join, filter, aggregate, and leakage traps that decide whether a model is learning signal or nonsense.","status":"live","lessonCount":4,"stepCount":28,"liveLessonCount":4,"liveStepCount":28,"estMinutes":28,"xpTotal":104},{"number":37,"slug":"dataset-pipelines","title":"dataset formats, ingestion, and validation pipelines","blurb":"a dataset is a product surface. build ingestion, validation, partitions, manifests, and checkpoints so the next run is not a mystery.","status":"live","lessonCount":5,"stepCount":35,"liveLessonCount":5,"liveStepCount":35,"estMinutes":37,"xpTotal":130},{"number":38,"slug":"ml-math-and-stats","title":"ml math and statistics that actually show up","blurb":"vectors, probability, distributions, correlation, and uncertainty are not trivia. they are how you read model behavior without worshipping it.","status":"live","lessonCount":5,"stepCount":35,"liveLessonCount":5,"liveStepCount":35,"estMinutes":37,"xpTotal":130},{"number":39,"slug":"supervised-learning-workflows","title":"supervised learning workflows","blurb":"labels, splits, baselines, training, prediction, and evaluation. the supervised workflow is the first complete model loop.","status":"live","lessonCount":5,"stepCount":35,"liveLessonCount":5,"liveStepCount":35,"estMinutes":40,"xpTotal":130},{"number":40,"slug":"unsupervised-learning-and-embeddings","title":"unsupervised learning, embeddings, and recommenders","blurb":"not every useful model has labels. cluster, compare, retrieve, and recommend by turning examples into useful neighborhoods.","status":"live","lessonCount":4,"stepCount":28,"liveLessonCount":4,"liveStepCount":28,"estMinutes":32,"xpTotal":104},{"number":41,"slug":"metrics-and-error-analysis","title":"metrics, slices, and error analysis","blurb":"accuracy is a blunt instrument. learn confusion matrices, precision, recall, thresholds, slices, and failure notes so model quality has evidence.","status":"live","lessonCount":5,"stepCount":35,"liveLessonCount":5,"liveStepCount":35,"estMinutes":37,"xpTotal":130},{"number":42,"slug":"pytorch-tensors-and-autograd","title":"pytorch tensors and autograd","blurb":"read tensor code without flinching. tensors, shapes, broadcasting, gradients, and autograd are the grammar of modern deep learning scripts.","status":"live","lessonCount":4,"stepCount":28,"liveLessonCount":4,"liveStepCount":28,"estMinutes":30,"xpTotal":104},{"number":43,"slug":"training-loops-and-optimizers","title":"training loops, backprop, optimizers, and schedulers","blurb":"the training loop is where models change. learn loss, gradients, optimizer steps, schedules, checkpoints, and the bugs ai ships there.","status":"live","lessonCount":5,"stepCount":35,"liveLessonCount":5,"liveStepCount":35,"estMinutes":37,"xpTotal":130},{"number":44,"slug":"deep-learning-architectures","title":"cnns, transformers, and useful llm internals","blurb":"architecture literacy for builders: convolution, attention, tokens, decoding, kv cache, quantization, and what those choices do to cost and behavior.","status":"live","lessonCount":5,"stepCount":35,"liveLessonCount":5,"liveStepCount":35,"estMinutes":37,"xpTotal":130},{"number":45,"slug":"feature-experiments-registries","title":"feature pipelines, experiment tracking, and registries","blurb":"features, runs, configs, artifacts, and registries are how ml work becomes repeatable instead of a lucky notebook.","status":"live","lessonCount":5,"stepCount":35,"liveLessonCount":5,"liveStepCount":35,"estMinutes":37,"xpTotal":130},{"number":46,"slug":"model-serving-and-mlops","title":"model serving, ci/cd, and mlops","blurb":"serving a model means handling inputs, versions, routes, batch jobs, ci gates, rollback, and production failures deliberately.","status":"live","lessonCount":6,"stepCount":42,"liveLessonCount":6,"liveStepCount":42,"estMinutes":44,"xpTotal":156},{"number":47,"slug":"monitoring-cloud-portfolio","title":"monitoring, drift, cloud scale, and portfolio launch","blurb":"the last mile: logs, drift, alerts, retraining decisions, cloud cost, gpu constraints, architecture docs, demos, and role stories.","status":"live","lessonCount":6,"stepCount":42,"liveLessonCount":6,"liveStepCount":42,"estMinutes":44,"xpTotal":156},{"number":48,"slug":"graphic-design-studio","title":"graphic design studio — prompt, kit, and fifty on-brand assets","blurb":"how a working designer runs image models: prompts written like creative briefs, a brand bible that travels as structured data — with the design tokens that carry it onto screens — and the seeds, reference locks, and QA filters that make fifty generated assets look like one studio shipped them.","status":"live","lessonCount":3,"stepCount":27,"liveLessonCount":3,"liveStepCount":27,"estMinutes":73,"xpTotal":82},{"number":49,"slug":"campaign-studio","title":"campaign studio — one campaign, end to end, with the gate on","blurb":"brief to voice-locked copy variants to batch plan to calendar to the numbers pass, then synthetic creator detection for hyperscale fake-organic. the whole campaign as data your scripts can check — and an approval gate nothing skips. built for the person who owns the send button.","status":"live","lessonCount":4,"stepCount":30,"liveLessonCount":4,"liveStepCount":30,"estMinutes":79,"xpTotal":94},{"number":50,"slug":"support-studio","title":"support studio — the reply drafter you can trust","blurb":"how a working support agent runs AI: a policy pack the drafter can't talk around, a banned-promises linter that holds every draft, golden eval sets that make each macro earn autonomy one intent at a time, and the escalation line where money, law, and anger stay human.","status":"live","lessonCount":3,"stepCount":23,"liveLessonCount":3,"liveStepCount":23,"estMinutes":61,"xpTotal":71},{"number":51,"slug":"copy-studio","title":"copy studio — voice from evidence, variants at scale, claims that clear","blurb":"a client's voice measured from their own published copy, variant batches that pass the voice gate or die with a named reason, and a claim check that blocks the ship button while any fact is unsourced. corrections-log culture, as code.","status":"live","lessonCount":3,"stepCount":24,"liveLessonCount":3,"liveStepCount":24,"estMinutes":66,"xpTotal":72},{"number":52,"slug":"analytics-studio","title":"analytics studio — messy export to defensible memo","blurb":"how a working analyst runs AI: a cleaning log that accounts for every dropped row, sample-first checks that catch the plausible-but-wrong aggregation, a memo where every number carries the address of the cell that made it, SR 11-7-style challenge against the AI's recommendation, and the rerun test — same data, same code, same memo, or it isn't done.","status":"live","lessonCount":3,"stepCount":22,"liveLessonCount":3,"liveStepCount":22,"estMinutes":61,"xpTotal":74},{"number":53,"slug":"delivery-studio","title":"delivery studio — direct the build without becoming the bottleneck","blurb":"how a working delivery lead runs AI builders: specs with acceptance checks written before the build, a review that runs the checks instead of admiring the demo, status roll-ups computed from acceptance records instead of standup vibes, the not-ready call made on evidence you can read out loud to a steering committee, and an hours-and-dollars receipt — before/after on a named function, finance's loaded rate, a named owner, the accepted thing that shipped — small enough to defend in a staff meeting.","status":"live","lessonCount":4,"stepCount":32,"liveLessonCount":4,"liveStepCount":32,"estMinutes":74,"xpTotal":96},{"number":54,"slug":"people-studio","title":"people studio — draft fast, decide human, prove everything","blurb":"how a working hr specialist runs AI: a data firewall that keeps employee records out of prompts by code instead of willpower, recruiting briefs where every claim cites a resume line, policy drafts that cannot publish without a named legal reviewer, and the adverse-action paper trail that survives a discrimination claim.","status":"live","lessonCount":3,"stepCount":24,"liveLessonCount":3,"liveStepCount":24,"estMinutes":56,"xpTotal":72},{"number":55,"slug":"ops-studio","title":"ops studio — tribal knowledge to running automation","blurb":"how a working ops lead gets the process out of one person's head and into automation that can be trusted: SOPs captured as versioned data with the invented steps hunted down, recurring checklists with an explicit auto-run vs named-approval line, exception queues instead of silent failures, a receipt against the export for every number in the weekly report, and a PII proxy that masks member identifiers before the model and restores them only for the named human who sends.","status":"live","lessonCount":4,"stepCount":32,"liveLessonCount":4,"liveStepCount":32,"estMinutes":80,"xpTotal":96},{"number":56,"slug":"legal-studio","title":"legal studio — the cite-check gate and the log that survives","blurb":"how a working lawyer runs AI: a citation-verification drill where every authority gets opened at the source (the fabricated ones always look right), clause extraction that's worthless without a pinpoint, privilege rules written as a routing table instead of remembered under deadline, and the review log you'd want in the record when opposing counsel moves for sanctions.","status":"live","lessonCount":3,"stepCount":22,"liveLessonCount":3,"liveStepCount":22,"estMinutes":60,"xpTotal":69},{"number":57,"slug":"agent-studio","title":"agent studio — ship one agent feature before you stand up","blurb":"one sitting, one agent feature, end to end: a tool schema that makes the dangerous call a validation error, a loop that meters its own spend, golden cases wired before the router works, a trace you debug from instead of vibes, and the ratchet that turns tonight's incident into tomorrow's eval. practice at production tempo.","status":"live","lessonCount":3,"stepCount":23,"liveLessonCount":3,"liveStepCount":23,"estMinutes":66,"xpTotal":73}]},"accessToc":{"chapters":[{"slug":"before-you-build","lessons":[{"slug":"from-worker-to-builder","steps":[{"id":"before-you-build/from-worker-to-builder/s01-01-intro"}]},{"slug":"upgrade-dull-artifacts-into-interactive-sites","steps":[{"id":"before-you-build/upgrade-dull-artifacts-into-interactive-sites/s01-01-intro"},{"id":"before-you-build/upgrade-dull-artifacts-into-interactive-sites/s02-02-build-brief"},{"id":"before-you-build/upgrade-dull-artifacts-into-interactive-sites/s03-03-your-artifact-brief"}]},{"slug":"why-building-matters-now","steps":[{"id":"before-you-build/why-building-matters-now/s01-01-intro"}]},{"slug":"the-builder-loop","steps":[{"id":"before-you-build/the-builder-loop/s01-01-intro"}]},{"slug":"your-first-builder-brief","steps":[{"id":"before-you-build/your-first-builder-brief/s01-01-intro"}]},{"slug":"what-the-ai-is-doing","steps":[{"id":"before-you-build/what-the-ai-is-doing/s01-01-intro"}]},{"slug":"build-your-first-reusable-tool","steps":[{"id":"before-you-build/build-your-first-reusable-tool/s01-01-intro"}]},{"slug":"from-prompt-to-project","steps":[{"id":"before-you-build/from-prompt-to-project/s01-01-intro"}]},{"slug":"why-code-appears-later","steps":[{"id":"before-you-build/why-code-appears-later/s01-01-intro"}]},{"slug":"use-it-again","steps":[{"id":"before-you-build/use-it-again/s01-01-intro"},{"id":"before-you-build/use-it-again/s02-02-which-fix-compounds"},{"id":"before-you-build/use-it-again/s03-03-save-version-two"}]}]},{"slug":"read-the-script","lessons":[{"slug":"names-and-values","steps":[{"id":"read-the-script/names-and-values/s01-01-intro"},{"id":"read-the-script/names-and-values/s02-02-spot-the-type"},{"id":"read-the-script/names-and-values/s03-03-assignment"},{"id":"read-the-script/names-and-values/s04-04-predict-the-score"},{"id":"read-the-script/names-and-values/s05-05-fill-the-name"},{"id":"read-the-script/names-and-values/s06-06-fix-the-typo"},{"id":"read-the-script/names-and-values/s07-07-write-greeting"},{"id":"read-the-script/names-and-values/s08-08-checkpoint"}]},{"slug":"functions-and-the-hallucinated-return","steps":[{"id":"read-the-script/functions-and-the-hallucinated-return/s01-01-intro"},{"id":"read-the-script/functions-and-the-hallucinated-return/s02-02-which-returns"},{"id":"read-the-script/functions-and-the-hallucinated-return/s03-03-return-vs-print"},{"id":"read-the-script/functions-and-the-hallucinated-return/s04-04-predict-the-result"},{"id":"read-the-script/functions-and-the-hallucinated-return/s05-05-fix-the-missing-return"},{"id":"read-the-script/functions-and-the-hallucinated-return/s06-06-fix-print-vs-return"},{"id":"read-the-script/functions-and-the-hallucinated-return/s07-07-write-square"},{"id":"read-the-script/functions-and-the-hallucinated-return/s08-08-checkpoint"}]},{"slug":"decisions-if-elif","steps":[{"id":"read-the-script/decisions-if-elif/s01-01-intro"},{"id":"read-the-script/decisions-if-elif/s02-02-truthiness-quiz"},{"id":"read-the-script/decisions-if-elif/s03-03-eq-vs-is"},{"id":"read-the-script/decisions-if-elif/s04-04-predict-the-empty-list"},{"id":"read-the-script/decisions-if-elif/s05-05-fix-the-zero-bug"},{"id":"read-the-script/decisions-if-elif/s06-06-fix-the-elif-order"},{"id":"read-the-script/decisions-if-elif/s07-07-checkpoint"},{"id":"read-the-script/decisions-if-elif/s08-08-going-deeper"}]}]},{"slug":"read-the-data-shapes","lessons":[{"slug":"the-shapes-ai-dumps-on-you","steps":[{"id":"read-the-data-shapes/the-shapes-ai-dumps-on-you/s01-01-intro"},{"id":"read-the-data-shapes/the-shapes-ai-dumps-on-you/s02-02-which-is-which"},{"id":"read-the-data-shapes/the-shapes-ai-dumps-on-you/s03-03-nested-paths"},{"id":"read-the-data-shapes/the-shapes-ai-dumps-on-you/s04-04-predict-the-deep-key"},{"id":"read-the-data-shapes/the-shapes-ai-dumps-on-you/s05-05-fill-the-index"},{"id":"read-the-data-shapes/the-shapes-ai-dumps-on-you/s06-06-fix-the-keyerror"},{"id":"read-the-data-shapes/the-shapes-ai-dumps-on-you/s07-07-fix-the-list-vs-dict"},{"id":"read-the-data-shapes/the-shapes-ai-dumps-on-you/s08-08-checkpoint"}]},{"slug":"walking-the-shape","steps":[{"id":"read-the-data-shapes/walking-the-shape/s01-01-intro"},{"id":"read-the-data-shapes/walking-the-shape/s02-02-which-loop-shape"},{"id":"read-the-data-shapes/walking-the-shape/s03-03-walking-the-shape"},{"id":"read-the-data-shapes/walking-the-shape/s04-04-predict-the-list-loop"},{"id":"read-the-data-shapes/walking-the-shape/s05-05-fill-the-loop-variable"},{"id":"read-the-data-shapes/walking-the-shape/s06-06-fix-the-dict-loop"},{"id":"read-the-data-shapes/walking-the-shape/s07-07-write-sum-loop"},{"id":"read-the-data-shapes/walking-the-shape/s08-08-checkpoint"}]},{"slug":"comprehensions-and-the-wrong-layer-bug","steps":[{"id":"read-the-data-shapes/comprehensions-and-the-wrong-layer-bug/s01-01-intro"},{"id":"read-the-data-shapes/comprehensions-and-the-wrong-layer-bug/s02-02-which-comp-shape"},{"id":"read-the-data-shapes/comprehensions-and-the-wrong-layer-bug/s03-03-with-filter"},{"id":"read-the-data-shapes/comprehensions-and-the-wrong-layer-bug/s04-04-predict-the-comp"},{"id":"read-the-data-shapes/comprehensions-and-the-wrong-layer-bug/s05-05-fix-the-wrong-layer"},{"id":"read-the-data-shapes/comprehensions-and-the-wrong-layer-bug/s06-06-write-comp"},{"id":"read-the-data-shapes/comprehensions-and-the-wrong-layer-bug/s07-07-checkpoint"},{"id":"read-the-data-shapes/comprehensions-and-the-wrong-layer-bug/s08-08-going-deeper"}]}]},{"slug":"read-the-failure","lessons":[{"slug":"read-bottom-up","steps":[{"id":"read-the-failure/read-bottom-up/s01-01-anatomy"},{"id":"read-the-failure/read-bottom-up/s02-02-which-error"},{"id":"read-the-failure/read-bottom-up/s03-03-the-five-fingerprints"},{"id":"read-the-failure/read-bottom-up/s04-04-predict-the-class"},{"id":"read-the-failure/read-bottom-up/s05-05-fix-nameerror"},{"id":"read-the-failure/read-bottom-up/s06-06-fix-attributeerror"},{"id":"read-the-failure/read-bottom-up/s07-07-write-defensive"},{"id":"read-the-failure/read-bottom-up/s08-08-checkpoint"}]},{"slug":"try-except-what-ai-misuses","steps":[{"id":"read-the-failure/try-except-what-ai-misuses/s01-01-intro"},{"id":"read-the-failure/try-except-what-ai-misuses/s02-02-which-block-runs"},{"id":"read-the-failure/try-except-what-ai-misuses/s03-03-naming-the-error"},{"id":"read-the-failure/try-except-what-ai-misuses/s04-04-predict-the-branch"},{"id":"read-the-failure/try-except-what-ai-misuses/s05-05-fill-the-keyword"},{"id":"read-the-failure/try-except-what-ai-misuses/s06-06-fix-the-bare-except"},{"id":"read-the-failure/try-except-what-ai-misuses/s07-07-write-safe-lookup"},{"id":"read-the-failure/try-except-what-ai-misuses/s08-08-checkpoint"}]},{"slug":"fail-loudly","steps":[{"id":"read-the-failure/fail-loudly/s01-01-intro"},{"id":"read-the-failure/fail-loudly/s02-02-which-raise-fires"},{"id":"read-the-failure/fail-loudly/s03-03-predict-the-raise"},{"id":"read-the-failure/fail-loudly/s04-04-fill-the-raise-keyword"},{"id":"read-the-failure/fail-loudly/s05-05-fix-the-silent-swallow"},{"id":"read-the-failure/fail-loudly/s06-06-write-validate-age"},{"id":"read-the-failure/fail-loudly/s07-07-checkpoint"},{"id":"read-the-failure/fail-loudly/s08-08-going-deeper"}]}]},{"slug":"read-the-pipeline","lessons":[{"slug":"files-without-fear","steps":[{"id":"read-the-pipeline/files-without-fear/s01-01-intro"},{"id":"read-the-pipeline/files-without-fear/s02-02-which-mode"},{"id":"read-the-pipeline/files-without-fear/s03-03-pathlib-and-manifests"},{"id":"read-the-pipeline/files-without-fear/s04-04-predict-the-suffix"},{"id":"read-the-pipeline/files-without-fear/s05-05-fill-the-mode"},{"id":"read-the-pipeline/files-without-fear/s06-06-fix-the-wrong-mode"},{"id":"read-the-pipeline/files-without-fear/s07-07-write-manifest-entry"},{"id":"read-the-pipeline/files-without-fear/s08-08-checkpoint"}]},{"slug":"talking-to-apis","steps":[{"id":"read-the-pipeline/talking-to-apis/s01-01-intro"},{"id":"read-the-pipeline/talking-to-apis/s02-02-which-status-family"},{"id":"read-the-pipeline/talking-to-apis/s03-03-parsing-the-json"},{"id":"read-the-pipeline/talking-to-apis/s04-04-predict-the-key"},{"id":"read-the-pipeline/talking-to-apis/s05-05-fill-the-method"},{"id":"read-the-pipeline/talking-to-apis/s06-06-fix-the-status-check"},{"id":"read-the-pipeline/talking-to-apis/s07-07-write-classify-status"},{"id":"read-the-pipeline/talking-to-apis/s08-08-checkpoint"}]},{"slug":"when-the-pipeline-breaks","steps":[{"id":"read-the-pipeline/when-the-pipeline-breaks/s01-01-intro"},{"id":"read-the-pipeline/when-the-pipeline-breaks/s02-02-honor-the-retry-after"},{"id":"read-the-pipeline/when-the-pipeline-breaks/s03-03-predict-the-status-handling"},{"id":"read-the-pipeline/when-the-pipeline-breaks/s04-04-fill-the-raise-for-status"},{"id":"read-the-pipeline/when-the-pipeline-breaks/s05-05-fix-the-missing-check"},{"id":"read-the-pipeline/when-the-pipeline-breaks/s06-06-fix-the-broad-retry"},{"id":"read-the-pipeline/when-the-pipeline-breaks/s07-07-checkpoint"},{"id":"read-the-pipeline/when-the-pipeline-breaks/s08-08-going-deeper"}]}]},{"slug":"mutation-and-state","lessons":[{"slug":"why-it-breaks","steps":[{"id":"mutation-and-state/why-it-breaks/s01-01-intro"},{"id":"mutation-and-state/why-it-breaks/s02-02-which-mutates"},{"id":"mutation-and-state/why-it-breaks/s03-03-shared-reference"},{"id":"mutation-and-state/why-it-breaks/s04-04-fix-the-shared-list"},{"id":"mutation-and-state/why-it-breaks/s05-05-checkpoint"}]},{"slug":"copy-vs-reference","steps":[{"id":"mutation-and-state/copy-vs-reference/s01-01-deep-copy"},{"id":"mutation-and-state/copy-vs-reference/s02-02-predict-the-shallow"},{"id":"mutation-and-state/copy-vs-reference/s03-03-fix-the-shallow-bug"},{"id":"mutation-and-state/copy-vs-reference/s04-04-checkpoint"}]}]},{"slug":"llm-apis","lessons":[{"slug":"before-the-api-what-the-model-is-doing","steps":[{"id":"llm-apis/before-the-api-what-the-model-is-doing/s01-01-intro"}]},{"slug":"the-messages-pattern","steps":[{"id":"llm-apis/the-messages-pattern/s01-01-intro"},{"id":"llm-apis/the-messages-pattern/s02-02-which-role-is-yours"},{"id":"llm-apis/the-messages-pattern/s03-03-reading-the-response"},{"id":"llm-apis/the-messages-pattern/s04-04-predict-the-text"},{"id":"llm-apis/the-messages-pattern/s05-05-fill-the-role"},{"id":"llm-apis/the-messages-pattern/s06-06-fix-the-message-shape"},{"id":"llm-apis/the-messages-pattern/s07-07-fix-the-response-access"},{"id":"llm-apis/the-messages-pattern/s08-08-write-ask-claude"},{"id":"llm-apis/the-messages-pattern/s09-09-checkpoint"}]},{"slug":"reading-the-response","steps":[{"id":"llm-apis/reading-the-response/s01-01-intro"},{"id":"llm-apis/reading-the-response/s02-02-which-block-do-you-read"},{"id":"llm-apis/reading-the-response/s03-03-the-five-stop-reasons"},{"id":"llm-apis/reading-the-response/s04-04-predict-the-text"},{"id":"llm-apis/reading-the-response/s05-05-fill-the-text-extract"},{"id":"llm-apis/reading-the-response/s06-06-fix-the-content-zero"},{"id":"llm-apis/reading-the-response/s07-07-fix-the-stop-assumption"},{"id":"llm-apis/reading-the-response/s08-08-write-the-extractor"},{"id":"llm-apis/reading-the-response/s09-09-checkpoint"}]},{"slug":"the-model-picker","steps":[{"id":"llm-apis/the-model-picker/s01-01-why-model-choice-is-a-product-decision"},{"id":"llm-apis/the-model-picker/s02-02-haiku-territory"},{"id":"llm-apis/the-model-picker/s03-03-which-model-here"},{"id":"llm-apis/the-model-picker/s04-04-sonnet-territory"},{"id":"llm-apis/the-model-picker/s05-05-opus-and-the-thinking-budget"},{"id":"llm-apis/the-model-picker/s06-06-pick-the-model"},{"id":"llm-apis/the-model-picker/s07-07-write-the-model-routing-memo"},{"id":"llm-apis/the-model-picker/s08-08-checkpoint"}]}]},{"slug":"structured-output","lessons":[{"slug":"getting-json-back","steps":[{"id":"structured-output/getting-json-back/s01-01-intro"},{"id":"structured-output/getting-json-back/s02-02-why-validate"},{"id":"structured-output/getting-json-back/s03-03-pydantic-models"},{"id":"structured-output/getting-json-back/s04-04-predict-the-validated"},{"id":"structured-output/getting-json-back/s05-05-fill-the-field-type"},{"id":"structured-output/getting-json-back/s06-06-fix-the-required-field"},{"id":"structured-output/getting-json-back/s07-07-fix-the-type-mismatch"},{"id":"structured-output/getting-json-back/s08-08-write-parse-extraction"},{"id":"structured-output/getting-json-back/s09-09-checkpoint"}]},{"slug":"schemas-eat-prompts","steps":[{"id":"structured-output/schemas-eat-prompts/s01-01-the-trust-boundary"},{"id":"structured-output/schemas-eat-prompts/s02-02-three-shipped-breakages"},{"id":"structured-output/schemas-eat-prompts/s03-03-which-boundary-broke"},{"id":"structured-output/schemas-eat-prompts/s04-04-schema-as-prompt-replacement"},{"id":"structured-output/schemas-eat-prompts/s05-05-where-validation-belongs"},{"id":"structured-output/schemas-eat-prompts/s06-06-the-pydantic-migration-as-war-story"},{"id":"structured-output/schemas-eat-prompts/s07-07-write-the-boundary-audit"},{"id":"structured-output/schemas-eat-prompts/s08-08-checkpoint"}]},{"slug":"dataset-schema-validation","steps":[{"id":"structured-output/dataset-schema-validation/s01-01-validate-at-the-boundary"},{"id":"structured-output/dataset-schema-validation/s02-02-the-silent-drop"},{"id":"structured-output/dataset-schema-validation/s03-03-predict-the-missing-fields"},{"id":"structured-output/dataset-schema-validation/s04-04-fill-the-membership-test"},{"id":"structured-output/dataset-schema-validation/s05-05-fix-the-range-check"},{"id":"structured-output/dataset-schema-validation/s06-06-write-validate-batch"},{"id":"structured-output/dataset-schema-validation/s07-07-claims-with-receipts"},{"id":"structured-output/dataset-schema-validation/s08-08-checkpoint"}]}]},{"slug":"mcp","lessons":[{"slug":"what-mcp-is","steps":[{"id":"mcp/what-mcp-is/s01-01-intro"},{"id":"mcp/what-mcp-is/s02-02-which-side-is-the-server"},{"id":"mcp/what-mcp-is/s03-03-the-tool-list"},{"id":"mcp/what-mcp-is/s04-04-predict-the-tool-result"},{"id":"mcp/what-mcp-is/s05-05-fill-the-tool-name"},{"id":"mcp/what-mcp-is/s06-06-fix-the-missing-argument"},{"id":"mcp/what-mcp-is/s07-07-fix-the-result-shape"},{"id":"mcp/what-mcp-is/s08-08-write-call-tool"},{"id":"mcp/what-mcp-is/s09-09-checkpoint"}]},{"slug":"writing-a-tiny-mcp-server","steps":[{"id":"mcp/writing-a-tiny-mcp-server/s01-01-intro"},{"id":"mcp/writing-a-tiny-mcp-server/s02-02-which-message-is-call-tool"},{"id":"mcp/writing-a-tiny-mcp-server/s03-03-the-tool-registry"},{"id":"mcp/writing-a-tiny-mcp-server/s04-04-predict-the-list-tools-output"},{"id":"mcp/writing-a-tiny-mcp-server/s05-05-fill-the-input-schema"},{"id":"mcp/writing-a-tiny-mcp-server/s06-06-fix-the-missing-error-response"},{"id":"mcp/writing-a-tiny-mcp-server/s07-07-fix-the-validation-gap"},{"id":"mcp/writing-a-tiny-mcp-server/s08-08-write-the-call-tool-dispatcher"},{"id":"mcp/writing-a-tiny-mcp-server/s09-09-checkpoint"}]},{"slug":"why-mcp-won","steps":[{"id":"mcp/why-mcp-won/s01-01-the-graveyard-of-tool-protocols"},{"id":"mcp/why-mcp-won/s02-02-what-openai-plugins-got-wrong"},{"id":"mcp/why-mcp-won/s03-03-which-failure-mode"},{"id":"mcp/why-mcp-won/s04-04-the-mcp-bet"},{"id":"mcp/why-mcp-won/s05-05-the-network-effect"},{"id":"mcp/why-mcp-won/s06-06-spot-the-mcp-wedge"},{"id":"mcp/why-mcp-won/s07-07-write-the-protocol-postmortem"},{"id":"mcp/why-mcp-won/s08-08-checkpoint"}]}]},{"slug":"agent-loops","lessons":[{"slug":"the-loop","steps":[{"id":"agent-loops/the-loop/s01-01-intro"},{"id":"agent-loops/the-loop/s02-02-which-stop-reason"},{"id":"agent-loops/the-loop/s03-03-tool-result-shape"},{"id":"agent-loops/the-loop/s04-04-predict-the-next-call"},{"id":"agent-loops/the-loop/s05-05-fill-the-stop-condition"},{"id":"agent-loops/the-loop/s06-06-fix-the-tool-id"},{"id":"agent-loops/the-loop/s07-07-fix-the-loop-exit"},{"id":"agent-loops/the-loop/s08-08-write-the-loop"},{"id":"agent-loops/the-loop/s09-09-checkpoint"}]},{"slug":"multi-step-tools","steps":[{"id":"agent-loops/multi-step-tools/s01-01-intro"},{"id":"agent-loops/multi-step-tools/s02-02-which-tool-runs"},{"id":"agent-loops/multi-step-tools/s03-03-tool-registry"},{"id":"agent-loops/multi-step-tools/s04-04-predict-the-chain"},{"id":"agent-loops/multi-step-tools/s05-05-fill-the-dispatch"},{"id":"agent-loops/multi-step-tools/s06-06-fix-the-missing-tool"},{"id":"agent-loops/multi-step-tools/s07-07-fix-the-parallel-ids"},{"id":"agent-loops/multi-step-tools/s08-08-write-multi-tool-agent"},{"id":"agent-loops/multi-step-tools/s09-09-checkpoint"}]},{"slug":"routing","steps":[{"id":"agent-loops/routing/s01-01-intro"},{"id":"agent-loops/routing/s02-02-when-to-route"},{"id":"agent-loops/routing/s03-03-classifier-output"},{"id":"agent-loops/routing/s04-04-predict-the-route"},{"id":"agent-loops/routing/s05-05-fill-the-dispatch"},{"id":"agent-loops/routing/s06-06-fix-the-fallback"},{"id":"agent-loops/routing/s07-07-fix-the-loose-classifier"},{"id":"agent-loops/routing/s08-08-write-the-router"},{"id":"agent-loops/routing/s09-09-checkpoint"}]},{"slug":"evaluator-optimizer","steps":[{"id":"agent-loops/evaluator-optimizer/s01-01-intro"},{"id":"agent-loops/evaluator-optimizer/s02-02-when-it-earns-its-keep"},{"id":"agent-loops/evaluator-optimizer/s03-03-judge-output-shape"},{"id":"agent-loops/evaluator-optimizer/s04-04-predict-the-iterations"},{"id":"agent-loops/evaluator-optimizer/s05-05-fill-the-exit"},{"id":"agent-loops/evaluator-optimizer/s06-06-fix-the-judge-parsing"},{"id":"agent-loops/evaluator-optimizer/s07-07-fix-the-missing-cap"},{"id":"agent-loops/evaluator-optimizer/s08-08-write-the-evaluator-optimizer"},{"id":"agent-loops/evaluator-optimizer/s09-09-checkpoint"}]},{"slug":"why-every-framework-is-thirty-lines","steps":[{"id":"agent-loops/why-every-framework-is-thirty-lines/s01-01-the-frameworks-converged"},{"id":"agent-loops/why-every-framework-is-thirty-lines/s02-02-langgraph-walkthrough"},{"id":"agent-loops/why-every-framework-is-thirty-lines/s03-03-the-work-is-a-graph"},{"id":"agent-loops/why-every-framework-is-thirty-lines/s04-04-which-framework-fits"},{"id":"agent-loops/why-every-framework-is-thirty-lines/s05-05-vercel-ai-sdk-walkthrough"},{"id":"agent-loops/why-every-framework-is-thirty-lines/s06-06-the-five-canonical-patterns"},{"id":"agent-loops/why-every-framework-is-thirty-lines/s07-07-when-to-stay-framework-free"},{"id":"agent-loops/why-every-framework-is-thirty-lines/s08-08-write-the-tradeoff-memo"},{"id":"agent-loops/why-every-framework-is-thirty-lines/s09-09-checkpoint"}]},{"slug":"the-industry-map","steps":[{"id":"agent-loops/the-industry-map/s01-01-the-five-layers"},{"id":"agent-loops/the-industry-map/s02-02-which-layer-failed"},{"id":"agent-loops/the-industry-map/s03-03-the-shape-of-the-stack"}]}]},{"slug":"git-and-github","lessons":[{"slug":"the-three-states","steps":[{"id":"git-and-github/the-three-states/s01-01-intro"},{"id":"git-and-github/the-three-states/s02-02-which-command-stages"},{"id":"git-and-github/the-three-states/s03-03-status-and-diff"},{"id":"git-and-github/the-three-states/s04-04-predict-the-status"},{"id":"git-and-github/the-three-states/s05-05-fill-the-command"},{"id":"git-and-github/the-three-states/s06-06-fix-the-staged-files"},{"id":"git-and-github/the-three-states/s07-07-fix-the-pr-command"},{"id":"git-and-github/the-three-states/s08-08-write-status-summary"},{"id":"git-and-github/the-three-states/s09-09-checkpoint"}]},{"slug":"three-git-disasters-ai-shipped","steps":[{"id":"git-and-github/three-git-disasters-ai-shipped/s01-01-why-postmortems-teach-better"},{"id":"git-and-github/three-git-disasters-ai-shipped/s02-02-uber-2016-credentials-in-repo"},{"id":"git-and-github/three-git-disasters-ai-shipped/s03-03-which-control-would-have-caught-it"},{"id":"git-and-github/three-git-disasters-ai-shipped/s04-04-the-samsung-paste"},{"id":"git-and-github/three-git-disasters-ai-shipped/s05-05-the-cursor-git-add-dot-default"},{"id":"git-and-github/three-git-disasters-ai-shipped/s06-06-spot-the-failure-mode"},{"id":"git-and-github/three-git-disasters-ai-shipped/s07-07-write-your-pre-commit-checklist"},{"id":"git-and-github/three-git-disasters-ai-shipped/s08-08-checkpoint"}]},{"slug":"github-actions-for-model-checks","steps":[{"id":"git-and-github/github-actions-for-model-checks/s01-01-intro"},{"id":"git-and-github/github-actions-for-model-checks/s02-02-green-but-wrong"},{"id":"git-and-github/github-actions-for-model-checks/s03-03-predict-the-run"},{"id":"git-and-github/github-actions-for-model-checks/s04-04-fill-the-trigger"},{"id":"git-and-github/github-actions-for-model-checks/s05-05-fix-the-eval-gate"},{"id":"git-and-github/github-actions-for-model-checks/s06-06-write-run-job"},{"id":"git-and-github/github-actions-for-model-checks/s07-07-checkpoint"}]}]},{"slug":"secrets-and-env","lessons":[{"slug":"keeping-keys-safe","steps":[{"id":"secrets-and-env/keeping-keys-safe/s01-01-intro"},{"id":"secrets-and-env/keeping-keys-safe/s02-02-which-line-leaks"},{"id":"secrets-and-env/keeping-keys-safe/s03-03-loading-env-vars"},{"id":"secrets-and-env/keeping-keys-safe/s04-04-predict-the-key"},{"id":"secrets-and-env/keeping-keys-safe/s05-05-fill-the-getenv"},{"id":"secrets-and-env/keeping-keys-safe/s06-06-fix-the-hardcoded-key"},{"id":"secrets-and-env/keeping-keys-safe/s07-07-fix-the-missing-default"},{"id":"secrets-and-env/keeping-keys-safe/s08-08-write-load-config"},{"id":"secrets-and-env/keeping-keys-safe/s09-09-checkpoint"}]},{"slug":"ml-service-secrets","steps":[{"id":"secrets-and-env/ml-service-secrets/s01-01-intro"},{"id":"secrets-and-env/ml-service-secrets/s02-02-which-log-line-leaks"},{"id":"secrets-and-env/ml-service-secrets/s03-03-predict-the-scan"},{"id":"secrets-and-env/ml-service-secrets/s04-04-fill-the-lookup"},{"id":"secrets-and-env/ml-service-secrets/s05-05-fix-the-logged-key"},{"id":"secrets-and-env/ml-service-secrets/s06-06-write-scan-logs"},{"id":"secrets-and-env/ml-service-secrets/s07-07-checkpoint"}]}]},{"slug":"prompting","lessons":[{"slug":"builder-briefs-before-prompts","steps":[{"id":"prompting/builder-briefs-before-prompts/s01-01-intro"}]},{"slug":"the-prompt-craft","steps":[{"id":"prompting/the-prompt-craft/s01-01-intro"},{"id":"prompting/the-prompt-craft/s02-02-which-prompt-is-better"},{"id":"prompting/the-prompt-craft/s03-03-context-rot"},{"id":"prompting/the-prompt-craft/s04-04-predict-the-output"},{"id":"prompting/the-prompt-craft/s05-05-fill-the-constraint"},{"id":"prompting/the-prompt-craft/s06-06-fix-the-vague-prompt"},{"id":"prompting/the-prompt-craft/s07-07-fix-the-bloated-context"},{"id":"prompting/the-prompt-craft/s08-08-write-the-prompt"},{"id":"prompting/the-prompt-craft/s09-09-checkpoint"}]},{"slug":"few-shot-and-reasoning","steps":[{"id":"prompting/few-shot-and-reasoning/s01-01-intro"},{"id":"prompting/few-shot-and-reasoning/s02-02-when-few-shot-helps"},{"id":"prompting/few-shot-and-reasoning/s03-03-the-cot-trap"},{"id":"prompting/few-shot-and-reasoning/s04-04-predict-the-format-lock"},{"id":"prompting/few-shot-and-reasoning/s05-05-fill-the-example-format"},{"id":"prompting/few-shot-and-reasoning/s06-06-fix-the-cot-on-reasoning"},{"id":"prompting/few-shot-and-reasoning/s07-07-fix-the-format-mismatch"},{"id":"prompting/few-shot-and-reasoning/s08-08-write-the-prompt-builder"},{"id":"prompting/few-shot-and-reasoning/s09-09-checkpoint"}]},{"slug":"agent-config-files","steps":[{"id":"prompting/agent-config-files/s01-01-intro"},{"id":"prompting/agent-config-files/s02-02-which-belongs-in-the-file"},{"id":"prompting/agent-config-files/s03-03-anatomy-of-a-good-file"},{"id":"prompting/agent-config-files/s04-04-predict-which-rule-fires"},{"id":"prompting/agent-config-files/s05-05-fill-the-rule-block"},{"id":"prompting/agent-config-files/s06-06-fix-the-too-vague"},{"id":"prompting/agent-config-files/s07-07-fix-the-stale-pointer"},{"id":"prompting/agent-config-files/s08-08-write-a-claude-md"},{"id":"prompting/agent-config-files/s09-09-checkpoint"}]},{"slug":"what-aged-in-prompting","steps":[{"id":"prompting/what-aged-in-prompting/s01-01-prompting-as-a-moving-target"},{"id":"prompting/what-aged-in-prompting/s02-02-cot-then-vs-now"},{"id":"prompting/what-aged-in-prompting/s03-03-which-still-works"},{"id":"prompting/what-aged-in-prompting/s04-04-the-system-prompt-arms-race"},{"id":"prompting/what-aged-in-prompting/s05-05-spot-the-stale-technique"},{"id":"prompting/what-aged-in-prompting/s06-06-the-prompt-engineer-debate"},{"id":"prompting/what-aged-in-prompting/s07-07-write-the-cheatsheet-update"},{"id":"prompting/what-aged-in-prompting/s08-08-checkpoint"}]}]},{"slug":"agent-traces","lessons":[{"slug":"reading-the-trace","steps":[{"id":"agent-traces/reading-the-trace/s01-01-intro"},{"id":"agent-traces/reading-the-trace/s02-02-which-turn-failed"},{"id":"agent-traces/reading-the-trace/s03-03-the-stop-reasons"},{"id":"agent-traces/reading-the-trace/s04-04-predict-the-stop"},{"id":"agent-traces/reading-the-trace/s05-05-fill-the-tool-name"},{"id":"agent-traces/reading-the-trace/s06-06-fix-the-loop"},{"id":"agent-traces/reading-the-trace/s07-07-fix-the-arg-shape"},{"id":"agent-traces/reading-the-trace/s08-08-write-the-summarizer"},{"id":"agent-traces/reading-the-trace/s09-09-checkpoint"}]},{"slug":"trace-driven-debugging","steps":[{"id":"agent-traces/trace-driven-debugging/s01-01-intro"},{"id":"agent-traces/trace-driven-debugging/s02-02-which-pattern-is-this"},{"id":"agent-traces/trace-driven-debugging/s03-03-the-loop-signature"},{"id":"agent-traces/trace-driven-debugging/s04-04-predict-the-call-count"},{"id":"agent-traces/trace-driven-debugging/s05-05-fill-the-detector"},{"id":"agent-traces/trace-driven-debugging/s06-06-fix-the-tool-routing"},{"id":"agent-traces/trace-driven-debugging/s07-07-fix-the-prompt-bloat"},{"id":"agent-traces/trace-driven-debugging/s08-08-write-the-trace-summary"},{"id":"agent-traces/trace-driven-debugging/s09-09-checkpoint"}]},{"slug":"prediction-ids-and-inference-logs","steps":[{"id":"agent-traces/prediction-ids-and-inference-logs/s01-01-intro"},{"id":"agent-traces/prediction-ids-and-inference-logs/s02-02-pick-the-log-line"},{"id":"agent-traces/prediction-ids-and-inference-logs/s03-03-predict-the-ids"},{"id":"agent-traces/prediction-ids-and-inference-logs/s04-04-fill-the-join-key"},{"id":"agent-traces/prediction-ids-and-inference-logs/s05-05-fix-the-join"},{"id":"agent-traces/prediction-ids-and-inference-logs/s06-06-write-the-logger"},{"id":"agent-traces/prediction-ids-and-inference-logs/s07-07-checkpoint"}]}]},{"slug":"evals","lessons":[{"slug":"check-before-you-trust","steps":[{"id":"evals/check-before-you-trust/s01-01-intro"}]},{"slug":"writing-evals","steps":[{"id":"evals/writing-evals/s01-01-intro"},{"id":"evals/writing-evals/s02-02-which-eval-passes"},{"id":"evals/writing-evals/s03-03-eval-patterns"},{"id":"evals/writing-evals/s04-04-predict-the-pass-rate"},{"id":"evals/writing-evals/s05-05-fill-the-assertion"},{"id":"evals/writing-evals/s06-06-fix-the-flaky-eval"},{"id":"evals/writing-evals/s07-07-fix-the-overstrict-eval"},{"id":"evals/writing-evals/s08-08-write-the-suite"},{"id":"evals/writing-evals/s09-09-checkpoint"}]},{"slug":"llm-as-judge","steps":[{"id":"evals/llm-as-judge/s01-01-intro"},{"id":"evals/llm-as-judge/s02-02-pairwise-or-rubric"},{"id":"evals/llm-as-judge/s03-03-the-four-biases"},{"id":"evals/llm-as-judge/s04-04-predict-the-bias"},{"id":"evals/llm-as-judge/s05-05-fill-the-rubric-call"},{"id":"evals/llm-as-judge/s06-06-fix-the-likert-trap"},{"id":"evals/llm-as-judge/s07-07-fix-the-position-bias"},{"id":"evals/llm-as-judge/s08-08-write-the-rubric-judge"},{"id":"evals/llm-as-judge/s09-09-checkpoint"}]},{"slug":"the-rise-of-evals-as-a-discipline","steps":[{"id":"evals/the-rise-of-evals-as-a-discipline/s01-01-the-prompt-engineering-era"},{"id":"evals/the-rise-of-evals-as-a-discipline/s02-02-the-eval-turn"},{"id":"evals/the-rise-of-evals-as-a-discipline/s03-03-which-company-survives-a-model-swap"},{"id":"evals/the-rise-of-evals-as-a-discipline/s04-04-case-studies"},{"id":"evals/the-rise-of-evals-as-a-discipline/s05-05-eval-first-vs-prompt-first"},{"id":"evals/the-rise-of-evals-as-a-discipline/s06-06-why-the-eval-engineer-eats-the-prompt-engineer"},{"id":"evals/the-rise-of-evals-as-a-discipline/s07-07-write-the-eval-readiness-audit"},{"id":"evals/the-rise-of-evals-as-a-discipline/s08-08-checkpoint"}]},{"slug":"model-validation-gates","steps":[{"id":"evals/model-validation-gates/s01-01-intro"},{"id":"evals/model-validation-gates/s02-02-spot-the-theater"},{"id":"evals/model-validation-gates/s03-03-predict-the-decision"},{"id":"evals/model-validation-gates/s04-04-fill-the-regression-check"},{"id":"evals/model-validation-gates/s05-05-fix-the-theater-gate"},{"id":"evals/model-validation-gates/s06-06-write-the-gate-runner"},{"id":"evals/model-validation-gates/s07-07-checkpoint"}]}]},{"slug":"context-and-retrieval","lessons":[{"slug":"chunking-that-respects-structure","steps":[{"id":"context-and-retrieval/chunking-that-respects-structure/s01-01-intro"},{"id":"context-and-retrieval/chunking-that-respects-structure/s02-02-which-content-shape-breaks"},{"id":"context-and-retrieval/chunking-that-respects-structure/s03-03-the-recursive-splitter"},{"id":"context-and-retrieval/chunking-that-respects-structure/s04-04-predict-the-shred"},{"id":"context-and-retrieval/chunking-that-respects-structure/s05-05-fill-the-separator-list"},{"id":"context-and-retrieval/chunking-that-respects-structure/s06-06-fix-the-mid-sentence-cut"},{"id":"context-and-retrieval/chunking-that-respects-structure/s07-07-fix-the-missing-overlap"},{"id":"context-and-retrieval/chunking-that-respects-structure/s08-08-write-the-recursive-splitter"},{"id":"context-and-retrieval/chunking-that-respects-structure/s09-09-checkpoint"}]},{"slug":"embedding-that-fits-the-budget","steps":[{"id":"context-and-retrieval/embedding-that-fits-the-budget/s01-01-intro"},{"id":"context-and-retrieval/embedding-that-fits-the-budget/s02-02-which-model-fits"},{"id":"context-and-retrieval/embedding-that-fits-the-budget/s03-03-the-vector-space"},{"id":"context-and-retrieval/embedding-that-fits-the-budget/s04-04-predict-the-closest"},{"id":"context-and-retrieval/embedding-that-fits-the-budget/s05-05-fill-the-cosine-formula"},{"id":"context-and-retrieval/embedding-that-fits-the-budget/s06-06-fix-the-wrong-embedding-model"},{"id":"context-and-retrieval/embedding-that-fits-the-budget/s07-07-fix-the-missing-normalization"},{"id":"context-and-retrieval/embedding-that-fits-the-budget/s08-08-write-the-similarity-ranker"},{"id":"context-and-retrieval/embedding-that-fits-the-budget/s09-09-checkpoint"}]},{"slug":"retrieval-that-finds-the-right-thing","steps":[{"id":"context-and-retrieval/retrieval-that-finds-the-right-thing/s01-01-intro"},{"id":"context-and-retrieval/retrieval-that-finds-the-right-thing/s02-02-which-result-is-good"},{"id":"context-and-retrieval/retrieval-that-finds-the-right-thing/s03-03-the-distance-threshold"},{"id":"context-and-retrieval/retrieval-that-finds-the-right-thing/s04-04-predict-the-top-k"},{"id":"context-and-retrieval/retrieval-that-finds-the-right-thing/s05-05-fill-the-cutoff"},{"id":"context-and-retrieval/retrieval-that-finds-the-right-thing/s06-06-fix-the-no-threshold"},{"id":"context-and-retrieval/retrieval-that-finds-the-right-thing/s07-07-fix-the-dup-results"},{"id":"context-and-retrieval/retrieval-that-finds-the-right-thing/s08-08-write-the-ranker"},{"id":"context-and-retrieval/retrieval-that-finds-the-right-thing/s09-09-checkpoint"}]},{"slug":"rag-vs-long-context-vs-fine-tune","steps":[{"id":"context-and-retrieval/rag-vs-long-context-vs-fine-tune/s01-01-the-three-way-fork"},{"id":"context-and-retrieval/rag-vs-long-context-vs-fine-tune/s02-02-rag-when-you-need-freshness"},{"id":"context-and-retrieval/rag-vs-long-context-vs-fine-tune/s03-03-which-fork-for-this-scenario"},{"id":"context-and-retrieval/rag-vs-long-context-vs-fine-tune/s04-04-long-context-when-the-corpus-fits"},{"id":"context-and-retrieval/rag-vs-long-context-vs-fine-tune/s05-05-fine-tune-when-style-or-format-is-the-product"},{"id":"context-and-retrieval/rag-vs-long-context-vs-fine-tune/s06-06-which-fork-dies-first"},{"id":"context-and-retrieval/rag-vs-long-context-vs-fine-tune/s07-07-graph-vector-or-both"},{"id":"context-and-retrieval/rag-vs-long-context-vs-fine-tune/s08-08-the-rubric"},{"id":"context-and-retrieval/rag-vs-long-context-vs-fine-tune/s09-09-write-the-fork-decision"},{"id":"context-and-retrieval/rag-vs-long-context-vs-fine-tune/s10-10-checkpoint"}]},{"slug":"retrieval-metrics-and-vector-db-shape","steps":[{"id":"context-and-retrieval/retrieval-metrics-and-vector-db-shape/s01-01-the-eval-set"},{"id":"context-and-retrieval/retrieval-metrics-and-vector-db-shape/s02-02-filter-or-search-first"},{"id":"context-and-retrieval/retrieval-metrics-and-vector-db-shape/s03-03-predict-recall-precision"},{"id":"context-and-retrieval/retrieval-metrics-and-vector-db-shape/s04-04-fill-the-reciprocal"},{"id":"context-and-retrieval/retrieval-metrics-and-vector-db-shape/s05-05-fix-the-late-filter"},{"id":"context-and-retrieval/retrieval-metrics-and-vector-db-shape/s06-06-write-recall-at-k"},{"id":"context-and-retrieval/retrieval-metrics-and-vector-db-shape/s07-07-checkpoint"}]}]},{"slug":"production-tradeoffs","lessons":[{"slug":"prompt-caching-correctly","steps":[{"id":"production-tradeoffs/prompt-caching-correctly/s01-01-intro"},{"id":"production-tradeoffs/prompt-caching-correctly/s02-02-which-piece-caches"},{"id":"production-tradeoffs/prompt-caching-correctly/s03-03-the-cache-breakpoints"},{"id":"production-tradeoffs/prompt-caching-correctly/s04-04-predict-the-savings"},{"id":"production-tradeoffs/prompt-caching-correctly/s05-05-fill-the-cache-control"},{"id":"production-tradeoffs/prompt-caching-correctly/s06-06-fix-the-cache-buster"},{"id":"production-tradeoffs/prompt-caching-correctly/s07-07-fix-the-ttl-default"},{"id":"production-tradeoffs/prompt-caching-correctly/s08-08-write-the-cost-estimator"},{"id":"production-tradeoffs/prompt-caching-correctly/s09-09-checkpoint"}]},{"slug":"read-the-token-bill","steps":[{"id":"production-tradeoffs/read-the-token-bill/s01-01-intro"},{"id":"production-tradeoffs/read-the-token-bill/s02-02-which-prompt-costs-more"},{"id":"production-tradeoffs/read-the-token-bill/s03-03-the-shape-of-a-bill"},{"id":"production-tradeoffs/read-the-token-bill/s04-04-predict-the-monthly-spend"},{"id":"production-tradeoffs/read-the-token-bill/s05-05-fill-the-cost-formula"},{"id":"production-tradeoffs/read-the-token-bill/s06-06-fix-the-pricing-ratio-error"},{"id":"production-tradeoffs/read-the-token-bill/s07-07-fix-the-units-error"},{"id":"production-tradeoffs/read-the-token-bill/s08-08-write-the-cost-estimator"},{"id":"production-tradeoffs/read-the-token-bill/s09-09-checkpoint"}]},{"slug":"the-model-price-war","steps":[{"id":"production-tradeoffs/the-model-price-war/s01-01-the-price-curve"},{"id":"production-tradeoffs/the-model-price-war/s02-02-three-bets-and-how-they-aged"},{"id":"production-tradeoffs/the-model-price-war/s03-03-which-startup-survived"},{"id":"production-tradeoffs/the-model-price-war/s04-04-the-incumbent-trap"},{"id":"production-tradeoffs/the-model-price-war/s05-05-features-now-viable"},{"id":"production-tradeoffs/the-model-price-war/s06-06-pricing-for-a-war-you-cant-predict"},{"id":"production-tradeoffs/the-model-price-war/s07-07-write-the-cost-model"},{"id":"production-tradeoffs/the-model-price-war/s08-08-checkpoint"}]},{"slug":"batch-realtime-costs","steps":[{"id":"production-tradeoffs/batch-realtime-costs/s01-01-who-is-waiting"},{"id":"production-tradeoffs/batch-realtime-costs/s02-02-which-lane"},{"id":"production-tradeoffs/batch-realtime-costs/s03-03-predict-the-bill"},{"id":"production-tradeoffs/batch-realtime-costs/s04-04-fill-the-miss-rate"},{"id":"production-tradeoffs/batch-realtime-costs/s05-05-fix-the-free-discount"},{"id":"production-tradeoffs/batch-realtime-costs/s06-06-write-monthly-bill"},{"id":"production-tradeoffs/batch-realtime-costs/s07-07-checkpoint"}]}]},{"slug":"debugging-output","lessons":[{"slug":"read-the-trace-not-the-chat","steps":[{"id":"debugging-output/read-the-trace-not-the-chat/s01-01-intro"},{"id":"debugging-output/read-the-trace-not-the-chat/s02-02-where-to-look-first"},{"id":"debugging-output/read-the-trace-not-the-chat/s03-03-the-four-failure-classes"},{"id":"debugging-output/read-the-trace-not-the-chat/s04-04-predict-the-bad-turn"},{"id":"debugging-output/read-the-trace-not-the-chat/s05-05-fill-the-find-bad-turn"},{"id":"debugging-output/read-the-trace-not-the-chat/s06-06-fix-the-fix-the-symptom"},{"id":"debugging-output/read-the-trace-not-the-chat/s07-07-fix-the-blame-the-model"},{"id":"debugging-output/read-the-trace-not-the-chat/s08-08-write-the-trace-summary"},{"id":"debugging-output/read-the-trace-not-the-chat/s09-09-checkpoint"}]},{"slug":"the-four-breakage-classes","steps":[{"id":"debugging-output/the-four-breakage-classes/s01-01-intro"},{"id":"debugging-output/the-four-breakage-classes/s02-02-classify-the-refund-bug"},{"id":"debugging-output/the-four-breakage-classes/s03-03-the-trace-anatomy"},{"id":"debugging-output/the-four-breakage-classes/s04-04-predict-the-class"},{"id":"debugging-output/the-four-breakage-classes/s05-05-fill-the-class-name"},{"id":"debugging-output/the-four-breakage-classes/s06-06-fix-the-misclassification"},{"id":"debugging-output/the-four-breakage-classes/s07-07-fix-the-parse-mangle"},{"id":"debugging-output/the-four-breakage-classes/s08-08-write-the-classifier"},{"id":"debugging-output/the-four-breakage-classes/s09-09-checkpoint"}]},{"slug":"five-real-postmortems","steps":[{"id":"debugging-output/five-real-postmortems/s01-01-the-postmortem-template"},{"id":"debugging-output/five-real-postmortems/s02-02-air-canada-refund-lawsuit"},{"id":"debugging-output/five-real-postmortems/s03-03-dpd-and-nyc-mycity"},{"id":"debugging-output/five-real-postmortems/s04-04-classify-the-five"},{"id":"debugging-output/five-real-postmortems/s05-05-recruiter-json-mangle"},{"id":"debugging-output/five-real-postmortems/s06-06-glean-style-retrieval-miss"},{"id":"debugging-output/five-real-postmortems/s07-07-which-fix-catches-the-most"},{"id":"debugging-output/five-real-postmortems/s08-08-write-the-postmortem"},{"id":"debugging-output/five-real-postmortems/s09-09-checkpoint"}]},{"slug":"prediction-failure-triage","steps":[{"id":"debugging-output/prediction-failure-triage/s01-01-reproduce-classify-route"},{"id":"debugging-output/prediction-failure-triage/s02-02-first-move"},{"id":"debugging-output/prediction-failure-triage/s03-03-predict-the-route"},{"id":"debugging-output/prediction-failure-triage/s04-04-fill-the-owners"},{"id":"debugging-output/prediction-failure-triage/s05-05-fix-the-paraphrase-repro"},{"id":"debugging-output/prediction-failure-triage/s06-06-write-the-router"},{"id":"debugging-output/prediction-failure-triage/s07-07-checkpoint"}]}]},{"slug":"capstone","lessons":[{"slug":"pick-a-project-that-ships","steps":[{"id":"capstone/pick-a-project-that-ships/s01-01-the-builders-graveyard"},{"id":"capstone/pick-a-project-that-ships/s02-02-which-project-survives-contact-with-reality"},{"id":"capstone/pick-a-project-that-ships/s03-03-the-three-shapes-that-ship"},{"id":"capstone/pick-a-project-that-ships/s04-04-the-wedge-checklist"},{"id":"capstone/pick-a-project-that-ships/s05-05-spot-the-missing-wedge"},{"id":"capstone/pick-a-project-that-ships/s06-06-scope-down-the-capstone"},{"id":"capstone/pick-a-project-that-ships/s07-07-checkpoint"}]},{"slug":"build-a-cli-agent","steps":[{"id":"capstone/build-a-cli-agent/s01-01-intro"},{"id":"capstone/build-a-cli-agent/s02-02-which-piece-is-missing"},{"id":"capstone/build-a-cli-agent/s03-03-the-tool-loop"},{"id":"capstone/build-a-cli-agent/s04-04-predict-the-final-answer"},{"id":"capstone/build-a-cli-agent/s05-05-fill-the-stop-check"},{"id":"capstone/build-a-cli-agent/s06-06-fix-the-tool-dispatch"},{"id":"capstone/build-a-cli-agent/s07-07-fix-the-message-append"},{"id":"capstone/build-a-cli-agent/s08-08-the-logging-pattern"},{"id":"capstone/build-a-cli-agent/s09-09-write-the-tool-runner"},{"id":"capstone/build-a-cli-agent/s10-10-fix-the-loop-exit"},{"id":"capstone/build-a-cli-agent/s11-11-write-the-agent"},{"id":"capstone/build-a-cli-agent/s12-12-checkpoint"}]},{"slug":"wire-the-real-model","steps":[{"id":"capstone/wire-the-real-model/s01-01-intro"},{"id":"capstone/wire-the-real-model/s02-02-where-the-key-lives"},{"id":"capstone/wire-the-real-model/s03-03-the-sdk-response-shape"},{"id":"capstone/wire-the-real-model/s04-04-predict-the-block-type"},{"id":"capstone/wire-the-real-model/s05-05-fill-the-key-load"},{"id":"capstone/wire-the-real-model/s06-06-fix-the-hardcoded-key"},{"id":"capstone/wire-the-real-model/s07-07-fix-the-block-access"},{"id":"capstone/wire-the-real-model/s08-08-write-the-shape-adapter"},{"id":"capstone/wire-the-real-model/s09-09-checkpoint"}]},{"slug":"validate-tool-inputs","steps":[{"id":"capstone/validate-tool-inputs/s01-01-intro"},{"id":"capstone/validate-tool-inputs/s02-02-which-input-needs-validation"},{"id":"capstone/validate-tool-inputs/s03-03-the-validator-surface"},{"id":"capstone/validate-tool-inputs/s04-04-predict-the-error"},{"id":"capstone/validate-tool-inputs/s05-05-fill-the-validate-call"},{"id":"capstone/validate-tool-inputs/s06-06-fix-the-untyped-tool"},{"id":"capstone/validate-tool-inputs/s07-07-fix-the-error-leak"},{"id":"capstone/validate-tool-inputs/s08-08-write-the-validator"},{"id":"capstone/validate-tool-inputs/s09-09-checkpoint"}]},{"slug":"add-evals-and-traces","steps":[{"id":"capstone/add-evals-and-traces/s01-01-intro"},{"id":"capstone/add-evals-and-traces/s02-02-which-eval-fits"},{"id":"capstone/add-evals-and-traces/s03-03-the-trace-shape"},{"id":"capstone/add-evals-and-traces/s04-04-predict-the-pass-rate"},{"id":"capstone/add-evals-and-traces/s05-05-fill-the-trace-append"},{"id":"capstone/add-evals-and-traces/s06-06-fix-the-trace-mutation"},{"id":"capstone/add-evals-and-traces/s07-07-fix-the-tautological-eval"},{"id":"capstone/add-evals-and-traces/s08-08-write-the-eval-runner"},{"id":"capstone/add-evals-and-traces/s09-09-checkpoint"}]},{"slug":"wire-an-mcp-tool","steps":[{"id":"capstone/wire-an-mcp-tool/s01-01-intro"},{"id":"capstone/wire-an-mcp-tool/s02-02-when-to-use-mcp"},{"id":"capstone/wire-an-mcp-tool/s03-03-the-mcp-protocol"},{"id":"capstone/wire-an-mcp-tool/s04-04-predict-the-tool-list"},{"id":"capstone/wire-an-mcp-tool/s05-05-fill-the-tools-call"},{"id":"capstone/wire-an-mcp-tool/s06-06-fix-the-result-shape"},{"id":"capstone/wire-an-mcp-tool/s07-07-fix-the-iserror-flag"},{"id":"capstone/wire-an-mcp-tool/s08-08-write-the-mcp-bridge"},{"id":"capstone/wire-an-mcp-tool/s09-09-checkpoint"}]},{"slug":"portfolio-ml-system-option","steps":[{"id":"capstone/portfolio-ml-system-option/s01-01-the-other-capstone"},{"id":"capstone/portfolio-ml-system-option/s02-02-what-reviewers-open"},{"id":"capstone/portfolio-ml-system-option/s03-03-predict-the-gate"},{"id":"capstone/portfolio-ml-system-option/s04-04-fill-the-gate"},{"id":"capstone/portfolio-ml-system-option/s05-05-fix-the-train-accuracy-gate"},{"id":"capstone/portfolio-ml-system-option/s06-06-write-the-scope-check"},{"id":"capstone/portfolio-ml-system-option/s07-07-checkpoint"}]}]},{"slug":"agent-harnesses","lessons":[{"slug":"project-workspaces-not-product-names","steps":[{"id":"agent-harnesses/project-workspaces-not-product-names/s01-01-intro"}]},{"slug":"what-a-harness-is","steps":[{"id":"agent-harnesses/what-a-harness-is/s01-01-intro"},{"id":"agent-harnesses/what-a-harness-is/s02-02-which-is-a-harness"},{"id":"agent-harnesses/what-a-harness-is/s03-03-the-four-layers"},{"id":"agent-harnesses/what-a-harness-is/s04-04-predict-the-layer"},{"id":"agent-harnesses/what-a-harness-is/s05-05-fill-the-dispatch"},{"id":"agent-harnesses/what-a-harness-is/s06-06-fix-the-no-retry"},{"id":"agent-harnesses/what-a-harness-is/s07-07-fix-the-hardcoded-registry"},{"id":"agent-harnesses/what-a-harness-is/s08-08-write-mini-harness"},{"id":"agent-harnesses/what-a-harness-is/s09-09-checkpoint"}]},{"slug":"building-a-harness","steps":[{"id":"agent-harnesses/building-a-harness/s01-01-intro"},{"id":"agent-harnesses/building-a-harness/s02-02-which-files-belong"},{"id":"agent-harnesses/building-a-harness/s03-03-the-build-order"},{"id":"agent-harnesses/building-a-harness/s04-04-predict-the-failed-layer"},{"id":"agent-harnesses/building-a-harness/s05-05-fill-the-harness-spec"},{"id":"agent-harnesses/building-a-harness/s06-06-fix-the-prompt-policy"},{"id":"agent-harnesses/building-a-harness/s07-07-fix-the-uncapped-allowlist"},{"id":"agent-harnesses/building-a-harness/s08-08-write-build-harness-run"},{"id":"agent-harnesses/building-a-harness/s09-09-checkpoint"}]},{"slug":"architecting-an-ai-native-workflow","steps":[{"id":"agent-harnesses/architecting-an-ai-native-workflow/s01-01-intro"},{"id":"agent-harnesses/architecting-an-ai-native-workflow/s02-02-which-workflow-fits"},{"id":"agent-harnesses/architecting-an-ai-native-workflow/s03-03-mapping-the-workflow"},{"id":"agent-harnesses/architecting-an-ai-native-workflow/s04-04-predict-the-readiness-score"},{"id":"agent-harnesses/architecting-an-ai-native-workflow/s05-05-fill-the-required-fields"},{"id":"agent-harnesses/architecting-an-ai-native-workflow/s06-06-fix-the-implicit-policy"},{"id":"agent-harnesses/architecting-an-ai-native-workflow/s07-07-fix-the-wrong-metric"},{"id":"agent-harnesses/architecting-an-ai-native-workflow/s08-08-write-the-workflow-validator"},{"id":"agent-harnesses/architecting-an-ai-native-workflow/s09-09-checkpoint"}]},{"slug":"five-industries-walked-through","steps":[{"id":"agent-harnesses/five-industries-walked-through/s01-01-the-case-study-method"},{"id":"agent-harnesses/five-industries-walked-through/s02-02-home-services"},{"id":"agent-harnesses/five-industries-walked-through/s03-03-which-task-belongs-to-the-agent"},{"id":"agent-harnesses/five-industries-walked-through/s04-04-insurance-brokerage"},{"id":"agent-harnesses/five-industries-walked-through/s05-05-recruiting-firm"},{"id":"agent-harnesses/five-industries-walked-through/s06-06-which-industry-wedges-fastest"},{"id":"agent-harnesses/five-industries-walked-through/s07-07-the-incumbent-trap"},{"id":"agent-harnesses/five-industries-walked-through/s08-08-write-the-process-debt-audit"},{"id":"agent-harnesses/five-industries-walked-through/s09-09-checkpoint"}]},{"slug":"incident-runbook-from-the-repo","steps":[{"id":"agent-harnesses/incident-runbook-from-the-repo/s01-01-intro"},{"id":"agent-harnesses/incident-runbook-from-the-repo/s02-02-which-is-a-runbook"},{"id":"agent-harnesses/incident-runbook-from-the-repo/s03-03-detect-decide-writeback"},{"id":"agent-harnesses/incident-runbook-from-the-repo/s04-04-predict-the-decision"},{"id":"agent-harnesses/incident-runbook-from-the-repo/s05-05-fill-the-decision-rule"},{"id":"agent-harnesses/incident-runbook-from-the-repo/s06-06-fix-the-wiki-page"},{"id":"agent-harnesses/incident-runbook-from-the-repo/s07-07-fix-the-unnamed-human"},{"id":"agent-harnesses/incident-runbook-from-the-repo/s08-08-write-the-runbook"},{"id":"agent-harnesses/incident-runbook-from-the-repo/s09-09-checkpoint"}]}]},{"slug":"ai-image-generation","lessons":[{"slug":"the-image-model-landscape","steps":[{"id":"ai-image-generation/the-image-model-landscape/s01-01-the-six-families"},{"id":"ai-image-generation/the-image-model-landscape/s02-02-flux-vs-midjourney"},{"id":"ai-image-generation/the-image-model-landscape/s03-03-pick-the-model"},{"id":"ai-image-generation/the-image-model-landscape/s04-04-nano-banana-and-the-batch-economics"},{"id":"ai-image-generation/the-image-model-landscape/s05-05-text-in-image"},{"id":"ai-image-generation/the-image-model-landscape/s06-06-which-model-for-text"},{"id":"ai-image-generation/the-image-model-landscape/s07-07-the-decision-tree"},{"id":"ai-image-generation/the-image-model-landscape/s08-08-write-pick-image-model"},{"id":"ai-image-generation/the-image-model-landscape/s09-09-checkpoint"}]},{"slug":"prompting-for-real-output","steps":[{"id":"ai-image-generation/prompting-for-real-output/s01-01-why-the-girl-with-red-hair-fails"},{"id":"ai-image-generation/prompting-for-real-output/s02-02-the-eight-knobs"},{"id":"ai-image-generation/prompting-for-real-output/s03-03-fix-the-vague-prompt"},{"id":"ai-image-generation/prompting-for-real-output/s04-04-controlnet-and-reference"},{"id":"ai-image-generation/prompting-for-real-output/s05-05-which-knob-is-missing"},{"id":"ai-image-generation/prompting-for-real-output/s06-06-failure-modes"},{"id":"ai-image-generation/prompting-for-real-output/s07-07-write-score-image-prompt"},{"id":"ai-image-generation/prompting-for-real-output/s08-08-checkpoint"}]},{"slug":"the-image-pipeline","steps":[{"id":"ai-image-generation/the-image-pipeline/s01-01-the-six-stages"},{"id":"ai-image-generation/the-image-pipeline/s02-02-batch-and-filter"},{"id":"ai-image-generation/the-image-pipeline/s03-03-which-stage-is-broken"},{"id":"ai-image-generation/the-image-pipeline/s04-04-format-and-platform"},{"id":"ai-image-generation/the-image-pipeline/s05-05-fill-the-pipeline"},{"id":"ai-image-generation/the-image-pipeline/s06-06-write-cost-for-batch"},{"id":"ai-image-generation/the-image-pipeline/s07-07-checkpoint"}]}]},{"slug":"ai-video-generation","lessons":[{"slug":"the-video-model-lineup","steps":[{"id":"ai-video-generation/the-video-model-lineup/s01-01-the-landscape"},{"id":"ai-video-generation/the-video-model-lineup/s02-02-sora-and-veo"},{"id":"ai-video-generation/the-video-model-lineup/s03-03-higgsfield-and-camera-control"},{"id":"ai-video-generation/the-video-model-lineup/s04-04-the-second-wave"},{"id":"ai-video-generation/the-video-model-lineup/s05-05-text-vs-image-vs-video"},{"id":"ai-video-generation/the-video-model-lineup/s06-06-which-lane"},{"id":"ai-video-generation/the-video-model-lineup/s07-07-pick-the-model"},{"id":"ai-video-generation/the-video-model-lineup/s08-08-write-pick-video-model"},{"id":"ai-video-generation/the-video-model-lineup/s09-09-checkpoint"}]},{"slug":"camera-control-and-motion","steps":[{"id":"ai-video-generation/camera-control-and-motion/s01-01-the-static-camera-problem"},{"id":"ai-video-generation/camera-control-and-motion/s02-02-shot-vocabulary"},{"id":"ai-video-generation/camera-control-and-motion/s03-03-which-shot-is-which"},{"id":"ai-video-generation/camera-control-and-motion/s04-04-camera-moves"},{"id":"ai-video-generation/camera-control-and-motion/s05-05-the-i2v-keyframe-pattern"},{"id":"ai-video-generation/camera-control-and-motion/s06-06-spot-the-generic-prompt"},{"id":"ai-video-generation/camera-control-and-motion/s07-07-write-audit-shot-list"},{"id":"ai-video-generation/camera-control-and-motion/s08-08-checkpoint"}]},{"slug":"the-cost-math","steps":[{"id":"ai-video-generation/the-cost-math/s01-01-the-unit-economics"},{"id":"ai-video-generation/the-cost-math/s02-02-the-retake-rate-reality"},{"id":"ai-video-generation/the-cost-math/s03-03-which-tier-for-this-budget"},{"id":"ai-video-generation/the-cost-math/s04-04-the-60-second-promo"},{"id":"ai-video-generation/the-cost-math/s05-05-write-cost-per-minute"},{"id":"ai-video-generation/the-cost-math/s06-06-checkpoint"}]}]},{"slug":"programmatic-design","lessons":[{"slug":"why-programmatic","steps":[{"id":"programmatic-design/why-programmatic/s01-01-intro"},{"id":"programmatic-design/why-programmatic/s02-02-the-three-jobs"},{"id":"programmatic-design/why-programmatic/s03-03-which-task-is-code"},{"id":"programmatic-design/why-programmatic/s04-04-parametric-vs-one-shot"},{"id":"programmatic-design/why-programmatic/s05-05-the-classifier"},{"id":"programmatic-design/why-programmatic/s06-06-write-classify-video-task"},{"id":"programmatic-design/why-programmatic/s07-07-checkpoint"}]},{"slug":"hyperframes-and-remotion","steps":[{"id":"programmatic-design/hyperframes-and-remotion/s01-01-the-two-tools"},{"id":"programmatic-design/hyperframes-and-remotion/s02-02-hyperframes-tour"},{"id":"programmatic-design/hyperframes-and-remotion/s03-03-hyperframes-cli"},{"id":"programmatic-design/hyperframes-and-remotion/s04-04-remotion-tour"},{"id":"programmatic-design/hyperframes-and-remotion/s05-05-the-decision-tree"},{"id":"programmatic-design/hyperframes-and-remotion/s06-06-pick-the-tool"},{"id":"programmatic-design/hyperframes-and-remotion/s07-07-claude-design-html"},{"id":"programmatic-design/hyperframes-and-remotion/s08-08-write-pick-tool"},{"id":"programmatic-design/hyperframes-and-remotion/s09-09-checkpoint"}]},{"slug":"the-ai-native-design-pipeline","steps":[{"id":"programmatic-design/the-ai-native-design-pipeline/s01-01-the-seven-steps"},{"id":"programmatic-design/the-ai-native-design-pipeline/s02-02-where-ai-fits-each-step"},{"id":"programmatic-design/the-ai-native-design-pipeline/s03-03-which-model-which-step"},{"id":"programmatic-design/the-ai-native-design-pipeline/s04-04-website-to-hyperframes"},{"id":"programmatic-design/the-ai-native-design-pipeline/s05-05-the-cost-model"},{"id":"programmatic-design/the-ai-native-design-pipeline/s06-06-score-the-pipeline"},{"id":"programmatic-design/the-ai-native-design-pipeline/s07-07-write-score-pipeline"},{"id":"programmatic-design/the-ai-native-design-pipeline/s08-08-checkpoint"}]}]},{"slug":"harness-engineering","lessons":[{"slug":"the-harness-engineering-mindset","steps":[{"id":"harness-engineering/the-harness-engineering-mindset/s01-01-the-model-is-only-one-input"},{"id":"harness-engineering/the-harness-engineering-mindset/s02-02-the-six-pieces-of-a-harness"},{"id":"harness-engineering/the-harness-engineering-mindset/s03-03-which-piece-is-missing"},{"id":"harness-engineering/the-harness-engineering-mindset/s04-04-the-skill-issue-reframe"},{"id":"harness-engineering/the-harness-engineering-mindset/s05-05-pick-the-fix"},{"id":"harness-engineering/the-harness-engineering-mindset/s06-06-the-harness-gap"},{"id":"harness-engineering/the-harness-engineering-mindset/s07-07-write-the-harness-inventory"},{"id":"harness-engineering/the-harness-engineering-mindset/s08-08-checkpoint"}]},{"slug":"the-ratchet","steps":[{"id":"harness-engineering/the-ratchet/s01-01-failures-are-signals-not-flukes"},{"id":"harness-engineering/the-ratchet/s02-02-every-line-traces-to-a-failure"},{"id":"harness-engineering/the-ratchet/s03-03-which-rule-earned-its-line"},{"id":"harness-engineering/the-ratchet/s04-04-working-backwards-from-behavior"},{"id":"harness-engineering/the-ratchet/s05-05-the-ratchet-log"},{"id":"harness-engineering/the-ratchet/s06-06-spot-the-cruft"},{"id":"harness-engineering/the-ratchet/s07-07-write-the-ratchet-update"},{"id":"harness-engineering/the-ratchet/s08-08-audit-the-ratchet"},{"id":"harness-engineering/the-ratchet/s09-09-checkpoint"}]},{"slug":"context-engineering","steps":[{"id":"harness-engineering/context-engineering/s01-01-the-context-rot"},{"id":"harness-engineering/context-engineering/s02-02-compaction"},{"id":"harness-engineering/context-engineering/s03-03-tool-call-offloading"},{"id":"harness-engineering/context-engineering/s04-04-progressive-disclosure"},{"id":"harness-engineering/context-engineering/s05-05-which-technique-fits"},{"id":"harness-engineering/context-engineering/s06-06-the-memory-hierarchy"},{"id":"harness-engineering/context-engineering/s07-07-classify-the-data"},{"id":"harness-engineering/context-engineering/s08-08-write-the-context-budget"},{"id":"harness-engineering/context-engineering/s09-09-checkpoint"}]},{"slug":"long-horizon-execution","steps":[{"id":"harness-engineering/long-horizon-execution/s01-01-the-40-step-problem"},{"id":"harness-engineering/long-horizon-execution/s02-02-loops-intercepting-early-stops"},{"id":"harness-engineering/long-horizon-execution/s03-03-planning-as-a-separate-step"},{"id":"harness-engineering/long-horizon-execution/s04-04-splits-generation-vs-evaluation"},{"id":"harness-engineering/long-horizon-execution/s05-05-which-pattern-fixes-the-failure"},{"id":"harness-engineering/long-horizon-execution/s06-06-hooks-as-the-enforcement-layer"},{"id":"harness-engineering/long-horizon-execution/s07-07-the-type-check-backpressure-pattern"},{"id":"harness-engineering/long-horizon-execution/s08-08-write-the-hook-router"},{"id":"harness-engineering/long-horizon-execution/s09-09-write-the-completion-guard"},{"id":"harness-engineering/long-horizon-execution/s10-10-checkpoint"}]},{"slug":"the-haas-shift","steps":[{"id":"harness-engineering/the-haas-shift/s01-01-llm-apis-to-harness-apis"},{"id":"harness-engineering/the-haas-shift/s02-02-the-convergence"},{"id":"harness-engineering/the-haas-shift/s03-03-which-haas-fits"},{"id":"harness-engineering/the-haas-shift/s04-04-harnesses-dont-shrink-they-move"},{"id":"harness-engineering/the-haas-shift/s05-05-the-overfitting-feedback-loop"},{"id":"harness-engineering/the-haas-shift/s06-06-mcp-security-as-prompt-injection"},{"id":"harness-engineering/the-haas-shift/s07-07-which-component-is-debt"},{"id":"harness-engineering/the-haas-shift/s08-08-write-the-build-vs-buy"},{"id":"harness-engineering/the-haas-shift/s09-09-checkpoint"}]},{"slug":"pipeline-boundaries","steps":[{"id":"harness-engineering/pipeline-boundaries/s01-01-the-boundary-is-an-artifact"},{"id":"harness-engineering/pipeline-boundaries/s02-02-spot-the-risky-handoff"},{"id":"harness-engineering/pipeline-boundaries/s03-03-predict-the-gate"},{"id":"harness-engineering/pipeline-boundaries/s04-04-fill-the-gate"},{"id":"harness-engineering/pipeline-boundaries/s05-05-fix-the-overtrust"},{"id":"harness-engineering/pipeline-boundaries/s06-06-write-the-advance-check"},{"id":"harness-engineering/pipeline-boundaries/s07-07-checkpoint"}]}]},{"slug":"intro-to-terminal","lessons":[{"slug":"what-the-terminal-is","steps":[{"id":"intro-to-terminal/what-the-terminal-is/s01-01-not-a-cockpit"},{"id":"intro-to-terminal/what-the-terminal-is/s02-02-what-it-actually-is"},{"id":"intro-to-terminal/what-the-terminal-is/s03-03-open-it"},{"id":"intro-to-terminal/what-the-terminal-is/s04-04-which-app"},{"id":"intro-to-terminal/what-the-terminal-is/s05-05-the-prompt"},{"id":"intro-to-terminal/what-the-terminal-is/s06-06-what-a-command-is"},{"id":"intro-to-terminal/what-the-terminal-is/s07-07-checkpoint"}]},{"slug":"moving-around","steps":[{"id":"intro-to-terminal/moving-around/s01-01-the-filesystem-is-a-tree"},{"id":"intro-to-terminal/moving-around/s02-02-pwd-and-ls"},{"id":"intro-to-terminal/moving-around/s03-03-where-am-i"},{"id":"intro-to-terminal/moving-around/s04-04-read-this-listing"},{"id":"intro-to-terminal/moving-around/s05-05-cd"},{"id":"intro-to-terminal/moving-around/s06-06-follow-the-moves"},{"id":"intro-to-terminal/moving-around/s07-07-pick-the-command"},{"id":"intro-to-terminal/moving-around/s08-08-checkpoint"}]},{"slug":"making-things","steps":[{"id":"intro-to-terminal/making-things/s01-01-mkdir-and-touch"},{"id":"intro-to-terminal/making-things/s02-02-folder-or-file"},{"id":"intro-to-terminal/making-things/s03-03-cat-and-echo"},{"id":"intro-to-terminal/making-things/s04-04-reading-a-file"},{"id":"intro-to-terminal/making-things/s05-05-rm-carefully"},{"id":"intro-to-terminal/making-things/s06-06-the-no-undo-rule"},{"id":"intro-to-terminal/making-things/s07-07-string-it-together"},{"id":"intro-to-terminal/making-things/s08-08-checkpoint"}]}]},{"slug":"intro-to-claude-cli","lessons":[{"slug":"what-the-claude-cli-is","steps":[{"id":"intro-to-claude-cli/what-the-claude-cli-is/s01-01-the-glass-is-gone"},{"id":"intro-to-claude-cli/what-the-claude-cli-is/s02-02-chat-vs-cli"},{"id":"intro-to-claude-cli/what-the-claude-cli-is/s03-03-which-tool"},{"id":"intro-to-claude-cli/what-the-claude-cli-is/s04-04-the-agent-loop"},{"id":"intro-to-claude-cli/what-the-claude-cli-is/s05-05-read-the-loop"},{"id":"intro-to-claude-cli/what-the-claude-cli-is/s06-06-permission-and-limits"},{"id":"intro-to-claude-cli/what-the-claude-cli-is/s07-07-checkpoint"}]},{"slug":"install-and-sign-in","steps":[{"id":"intro-to-claude-cli/install-and-sign-in/s01-01-two-ways-to-install"},{"id":"intro-to-claude-cli/install-and-sign-in/s02-02-run-the-installer"},{"id":"intro-to-claude-cli/install-and-sign-in/s03-03-install-check"},{"id":"intro-to-claude-cli/install-and-sign-in/s04-04-sign-in"},{"id":"intro-to-claude-cli/install-and-sign-in/s05-05-what-sign-in-did"},{"id":"intro-to-claude-cli/install-and-sign-in/s06-06-auth-check"},{"id":"intro-to-claude-cli/install-and-sign-in/s07-07-account-not-api-key"},{"id":"intro-to-claude-cli/install-and-sign-in/s08-08-checkpoint"}]},{"slug":"your-first-session","steps":[{"id":"intro-to-claude-cli/your-first-session/s01-01-start-in-a-folder"},{"id":"intro-to-claude-cli/your-first-session/s02-02-your-first-instruction"},{"id":"intro-to-claude-cli/your-first-session/s03-03-watch-the-loop"},{"id":"intro-to-claude-cli/your-first-session/s04-04-read-what-it-did"},{"id":"intro-to-claude-cli/your-first-session/s05-05-one-shot-or-interactive"},{"id":"intro-to-claude-cli/your-first-session/s06-06-chat-or-cli-decision"},{"id":"intro-to-claude-cli/your-first-session/s07-07-where-this-goes"},{"id":"intro-to-claude-cli/your-first-session/s08-08-checkpoint"}]}]},{"slug":"intro-to-codex-cli","lessons":[{"slug":"another-tool-same-idea","steps":[{"id":"intro-to-codex-cli/another-tool-same-idea/s01-01-why-a-second-tool"},{"id":"intro-to-codex-cli/another-tool-same-idea/s02-02-what-carries-over"},{"id":"intro-to-codex-cli/another-tool-same-idea/s03-03-what-carries-over-check"},{"id":"intro-to-codex-cli/another-tool-same-idea/s04-04-what-is-different"},{"id":"intro-to-codex-cli/another-tool-same-idea/s05-05-spot-the-difference"},{"id":"intro-to-codex-cli/another-tool-same-idea/s06-06-when-to-reach-for-which"},{"id":"intro-to-codex-cli/another-tool-same-idea/s07-07-checkpoint"}]},{"slug":"install-and-sign-in","steps":[{"id":"intro-to-codex-cli/install-and-sign-in/s01-01-the-install-paths"},{"id":"intro-to-codex-cli/install-and-sign-in/s02-02-installing-it"},{"id":"intro-to-codex-cli/install-and-sign-in/s03-03-verify-it"},{"id":"intro-to-codex-cli/install-and-sign-in/s04-04-install-check"},{"id":"intro-to-codex-cli/install-and-sign-in/s05-05-sign-in"},{"id":"intro-to-codex-cli/install-and-sign-in/s06-06-account-vs-api-key"},{"id":"intro-to-codex-cli/install-and-sign-in/s07-07-auth-check"},{"id":"intro-to-codex-cli/install-and-sign-in/s08-08-checkpoint"}]},{"slug":"your-first-session","steps":[{"id":"intro-to-codex-cli/your-first-session/s01-01-start-and-instruct"},{"id":"intro-to-codex-cli/your-first-session/s02-02-the-loop-again"},{"id":"intro-to-codex-cli/your-first-session/s03-03-read-what-it-did"},{"id":"intro-to-codex-cli/your-first-session/s04-04-usage-patterns"},{"id":"intro-to-codex-cli/your-first-session/s05-05-usage-scenario"},{"id":"intro-to-codex-cli/your-first-session/s06-06-running-both"},{"id":"intro-to-codex-cli/your-first-session/s07-07-where-this-goes"},{"id":"intro-to-codex-cli/your-first-session/s08-08-checkpoint"}]}]},{"slug":"team-skills","lessons":[{"slug":"what-a-skill-is","steps":[{"id":"team-skills/what-a-skill-is/s01-01-the-re-explaining-problem"},{"id":"team-skills/what-a-skill-is/s02-02-a-skill-defined"},{"id":"team-skills/what-a-skill-is/s03-03-a-real-skill"},{"id":"team-skills/what-a-skill-is/s04-04-what-a-skill-is-check"},{"id":"team-skills/what-a-skill-is/s05-05-skill-vs-prompt-vs-agent"},{"id":"team-skills/what-a-skill-is/s06-06-skill-or-agent"},{"id":"team-skills/what-a-skill-is/s07-07-checkpoint"}]},{"slug":"skills-as-a-team-thing","steps":[{"id":"team-skills/skills-as-a-team-thing/s01-01-the-team-problem"},{"id":"team-skills/skills-as-a-team-thing/s02-02-org-wide-skills"},{"id":"team-skills/skills-as-a-team-thing/s03-03-sharing-and-the-directory"},{"id":"team-skills/skills-as-a-team-thing/s04-04-deployment-check"},{"id":"team-skills/skills-as-a-team-thing/s05-05-collaborating-through-skills"},{"id":"team-skills/skills-as-a-team-thing/s06-06-sharing-scenario"},{"id":"team-skills/skills-as-a-team-thing/s07-07-checkpoint"}]},{"slug":"role-playbooks","steps":[{"id":"team-skills/role-playbooks/s01-01-hr-skills"},{"id":"team-skills/role-playbooks/s02-02-legal-skills"},{"id":"team-skills/role-playbooks/s03-03-operations-skills"},{"id":"team-skills/role-playbooks/s04-04-match-the-skill"},{"id":"team-skills/role-playbooks/s05-05-skill-or-one-off"},{"id":"team-skills/role-playbooks/s06-06-skill-or-one-off-check"},{"id":"team-skills/role-playbooks/s07-07-checkpoint"}]},{"slug":"governance-and-trust","steps":[{"id":"team-skills/governance-and-trust/s01-01-a-skill-can-do-real-things"},{"id":"team-skills/governance-and-trust/s02-02-treat-it-like-software"},{"id":"team-skills/governance-and-trust/s03-03-evaluate-before-you-deploy"},{"id":"team-skills/governance-and-trust/s04-04-access-control"},{"id":"team-skills/governance-and-trust/s05-05-governance-scenario"},{"id":"team-skills/governance-and-trust/s06-06-a-rollout-checklist"},{"id":"team-skills/governance-and-trust/s07-07-checkpoint"}]}]},{"slug":"dataframes-numpy-pandas","lessons":[{"slug":"ml-package-map","steps":[{"id":"dataframes-numpy-pandas/ml-package-map/s01-01-intro"},{"id":"dataframes-numpy-pandas/ml-package-map/s02-02-match-the-tool"},{"id":"dataframes-numpy-pandas/ml-package-map/s03-03-predict-sys-modules"},{"id":"dataframes-numpy-pandas/ml-package-map/s04-04-fill-the-registry-key"},{"id":"dataframes-numpy-pandas/ml-package-map/s05-05-fix-the-swapped-map"},{"id":"dataframes-numpy-pandas/ml-package-map/s06-06-write-find-unused"},{"id":"dataframes-numpy-pandas/ml-package-map/s07-07-checkpoint"}]},{"slug":"array-and-series-shapes","steps":[{"id":"dataframes-numpy-pandas/array-and-series-shapes/s01-01-intro"},{"id":"dataframes-numpy-pandas/array-and-series-shapes/s02-02-choose-the-risk"},{"id":"dataframes-numpy-pandas/array-and-series-shapes/s03-03-predict-the-checks"},{"id":"dataframes-numpy-pandas/array-and-series-shapes/s04-04-fill-the-return"},{"id":"dataframes-numpy-pandas/array-and-series-shapes/s05-05-fix-the-overtrust"},{"id":"dataframes-numpy-pandas/array-and-series-shapes/s06-06-write-count-ready"},{"id":"dataframes-numpy-pandas/array-and-series-shapes/s07-07-checkpoint"}]},{"slug":"dataframe-selection-and-cleaning","steps":[{"id":"dataframes-numpy-pandas/dataframe-selection-and-cleaning/s01-01-intro"},{"id":"dataframes-numpy-pandas/dataframe-selection-and-cleaning/s02-02-choose-the-risk"},{"id":"dataframes-numpy-pandas/dataframe-selection-and-cleaning/s03-03-predict-the-checks"},{"id":"dataframes-numpy-pandas/dataframe-selection-and-cleaning/s04-04-fill-the-return"},{"id":"dataframes-numpy-pandas/dataframe-selection-and-cleaning/s05-05-fix-the-overtrust"},{"id":"dataframes-numpy-pandas/dataframe-selection-and-cleaning/s06-06-write-count-ready"},{"id":"dataframes-numpy-pandas/dataframe-selection-and-cleaning/s07-07-checkpoint"}]},{"slug":"missing-values-and-types","steps":[{"id":"dataframes-numpy-pandas/missing-values-and-types/s01-01-intro"},{"id":"dataframes-numpy-pandas/missing-values-and-types/s02-02-choose-the-risk"},{"id":"dataframes-numpy-pandas/missing-values-and-types/s03-03-predict-the-checks"},{"id":"dataframes-numpy-pandas/missing-values-and-types/s04-04-fill-the-return"},{"id":"dataframes-numpy-pandas/missing-values-and-types/s05-05-fix-the-overtrust"},{"id":"dataframes-numpy-pandas/missing-values-and-types/s06-06-write-count-ready"},{"id":"dataframes-numpy-pandas/missing-values-and-types/s07-07-checkpoint"}]},{"slug":"groupby-joins-and-features","steps":[{"id":"dataframes-numpy-pandas/groupby-joins-and-features/s01-01-intro"},{"id":"dataframes-numpy-pandas/groupby-joins-and-features/s02-02-choose-the-risk"},{"id":"dataframes-numpy-pandas/groupby-joins-and-features/s03-03-predict-the-checks"},{"id":"dataframes-numpy-pandas/groupby-joins-and-features/s04-04-fill-the-return"},{"id":"dataframes-numpy-pandas/groupby-joins-and-features/s05-05-fix-the-overtrust"},{"id":"dataframes-numpy-pandas/groupby-joins-and-features/s06-06-write-count-ready"},{"id":"dataframes-numpy-pandas/groupby-joins-and-features/s07-07-checkpoint"}]},{"slug":"mission-api-to-dataframe","steps":[{"id":"dataframes-numpy-pandas/mission-api-to-dataframe/s01-01-intro"},{"id":"dataframes-numpy-pandas/mission-api-to-dataframe/s02-02-choose-the-risk"},{"id":"dataframes-numpy-pandas/mission-api-to-dataframe/s03-03-predict-the-checks"},{"id":"dataframes-numpy-pandas/mission-api-to-dataframe/s04-04-fill-the-return"},{"id":"dataframes-numpy-pandas/mission-api-to-dataframe/s05-05-fix-the-overtrust"},{"id":"dataframes-numpy-pandas/mission-api-to-dataframe/s06-06-write-count-ready"},{"id":"dataframes-numpy-pandas/mission-api-to-dataframe/s07-07-checkpoint"}]}]},{"slug":"sql-for-ml-datasets","lessons":[{"slug":"select-filter-aggregate","steps":[{"id":"sql-for-ml-datasets/select-filter-aggregate/s01-01-intro"},{"id":"sql-for-ml-datasets/select-filter-aggregate/s02-02-choose-the-risk"},{"id":"sql-for-ml-datasets/select-filter-aggregate/s03-03-predict-the-checks"},{"id":"sql-for-ml-datasets/select-filter-aggregate/s04-04-fill-the-return"},{"id":"sql-for-ml-datasets/select-filter-aggregate/s05-05-fix-the-overtrust"},{"id":"sql-for-ml-datasets/select-filter-aggregate/s06-06-write-count-ready"},{"id":"sql-for-ml-datasets/select-filter-aggregate/s07-07-checkpoint"}]},{"slug":"joins-and-label-windows","steps":[{"id":"sql-for-ml-datasets/joins-and-label-windows/s01-01-intro"},{"id":"sql-for-ml-datasets/joins-and-label-windows/s02-02-choose-the-risk"},{"id":"sql-for-ml-datasets/joins-and-label-windows/s03-03-predict-the-checks"},{"id":"sql-for-ml-datasets/joins-and-label-windows/s04-04-fill-the-return"},{"id":"sql-for-ml-datasets/joins-and-label-windows/s05-05-fix-the-overtrust"},{"id":"sql-for-ml-datasets/joins-and-label-windows/s06-06-write-count-ready"},{"id":"sql-for-ml-datasets/joins-and-label-windows/s07-07-checkpoint"}]},{"slug":"sql-quality-checks","steps":[{"id":"sql-for-ml-datasets/sql-quality-checks/s01-01-intro"},{"id":"sql-for-ml-datasets/sql-quality-checks/s02-02-choose-the-risk"},{"id":"sql-for-ml-datasets/sql-quality-checks/s03-03-predict-the-checks"},{"id":"sql-for-ml-datasets/sql-quality-checks/s04-04-fill-the-return"},{"id":"sql-for-ml-datasets/sql-quality-checks/s05-05-fix-the-overtrust"},{"id":"sql-for-ml-datasets/sql-quality-checks/s06-06-write-count-ready"},{"id":"sql-for-ml-datasets/sql-quality-checks/s07-07-checkpoint"}]},{"slug":"mission-sql-feature-query-lab","steps":[{"id":"sql-for-ml-datasets/mission-sql-feature-query-lab/s01-01-intro"},{"id":"sql-for-ml-datasets/mission-sql-feature-query-lab/s02-02-choose-the-risk"},{"id":"sql-for-ml-datasets/mission-sql-feature-query-lab/s03-03-predict-the-checks"},{"id":"sql-for-ml-datasets/mission-sql-feature-query-lab/s04-04-fill-the-return"},{"id":"sql-for-ml-datasets/mission-sql-feature-query-lab/s05-05-fix-the-overtrust"},{"id":"sql-for-ml-datasets/mission-sql-feature-query-lab/s06-06-write-count-ready"},{"id":"sql-for-ml-datasets/mission-sql-feature-query-lab/s07-07-checkpoint"}]}]},{"slug":"dataset-pipelines","lessons":[{"slug":"csv-jsonl-parquet-tradeoffs","steps":[{"id":"dataset-pipelines/csv-jsonl-parquet-tradeoffs/s01-01-intro"},{"id":"dataset-pipelines/csv-jsonl-parquet-tradeoffs/s02-02-choose-the-risk"},{"id":"dataset-pipelines/csv-jsonl-parquet-tradeoffs/s03-03-predict-the-checks"},{"id":"dataset-pipelines/csv-jsonl-parquet-tradeoffs/s04-04-fill-the-return"},{"id":"dataset-pipelines/csv-jsonl-parquet-tradeoffs/s05-05-fix-the-overtrust"},{"id":"dataset-pipelines/csv-jsonl-parquet-tradeoffs/s06-06-write-count-ready"},{"id":"dataset-pipelines/csv-jsonl-parquet-tradeoffs/s07-07-checkpoint"}]},{"slug":"pagination-retries-checkpoints","steps":[{"id":"dataset-pipelines/pagination-retries-checkpoints/s01-01-intro"},{"id":"dataset-pipelines/pagination-retries-checkpoints/s02-02-choose-the-risk"},{"id":"dataset-pipelines/pagination-retries-checkpoints/s03-03-predict-the-checks"},{"id":"dataset-pipelines/pagination-retries-checkpoints/s04-04-fill-the-return"},{"id":"dataset-pipelines/pagination-retries-checkpoints/s05-05-fix-the-overtrust"},{"id":"dataset-pipelines/pagination-retries-checkpoints/s06-06-write-count-ready"},{"id":"dataset-pipelines/pagination-retries-checkpoints/s07-07-checkpoint"}]},{"slug":"schema-drift-and-contracts","steps":[{"id":"dataset-pipelines/schema-drift-and-contracts/s01-01-intro"},{"id":"dataset-pipelines/schema-drift-and-contracts/s02-02-choose-the-risk"},{"id":"dataset-pipelines/schema-drift-and-contracts/s03-03-predict-the-checks"},{"id":"dataset-pipelines/schema-drift-and-contracts/s04-04-fill-the-return"},{"id":"dataset-pipelines/schema-drift-and-contracts/s05-05-fix-the-overtrust"},{"id":"dataset-pipelines/schema-drift-and-contracts/s06-06-write-count-ready"},{"id":"dataset-pipelines/schema-drift-and-contracts/s07-07-checkpoint"}]},{"slug":"pipeline-orchestration-shape","steps":[{"id":"dataset-pipelines/pipeline-orchestration-shape/s01-01-intro"},{"id":"dataset-pipelines/pipeline-orchestration-shape/s02-02-choose-the-risk"},{"id":"dataset-pipelines/pipeline-orchestration-shape/s03-03-predict-the-checks"},{"id":"dataset-pipelines/pipeline-orchestration-shape/s04-04-fill-the-return"},{"id":"dataset-pipelines/pipeline-orchestration-shape/s05-05-fix-the-overtrust"},{"id":"dataset-pipelines/pipeline-orchestration-shape/s06-06-write-count-ready"},{"id":"dataset-pipelines/pipeline-orchestration-shape/s07-07-checkpoint"}]},{"slug":"mission-api-to-dataset-pipeline","steps":[{"id":"dataset-pipelines/mission-api-to-dataset-pipeline/s01-01-intro"},{"id":"dataset-pipelines/mission-api-to-dataset-pipeline/s02-02-choose-the-risk"},{"id":"dataset-pipelines/mission-api-to-dataset-pipeline/s03-03-predict-the-checks"},{"id":"dataset-pipelines/mission-api-to-dataset-pipeline/s04-04-fill-the-return"},{"id":"dataset-pipelines/mission-api-to-dataset-pipeline/s05-05-fix-the-overtrust"},{"id":"dataset-pipelines/mission-api-to-dataset-pipeline/s06-06-write-count-ready"},{"id":"dataset-pipelines/mission-api-to-dataset-pipeline/s07-07-checkpoint"}]}]},{"slug":"ml-math-and-stats","lessons":[{"slug":"vectors-matrices-dot-products","steps":[{"id":"ml-math-and-stats/vectors-matrices-dot-products/s01-01-intro"},{"id":"ml-math-and-stats/vectors-matrices-dot-products/s02-02-choose-the-risk"},{"id":"ml-math-and-stats/vectors-matrices-dot-products/s03-03-predict-the-checks"},{"id":"ml-math-and-stats/vectors-matrices-dot-products/s04-04-fill-the-return"},{"id":"ml-math-and-stats/vectors-matrices-dot-products/s05-05-fix-the-overtrust"},{"id":"ml-math-and-stats/vectors-matrices-dot-products/s06-06-write-count-ready"},{"id":"ml-math-and-stats/vectors-matrices-dot-products/s07-07-checkpoint"}]},{"slug":"probability-and-baselines","steps":[{"id":"ml-math-and-stats/probability-and-baselines/s01-01-intro"},{"id":"ml-math-and-stats/probability-and-baselines/s02-02-choose-the-risk"},{"id":"ml-math-and-stats/probability-and-baselines/s03-03-predict-the-checks"},{"id":"ml-math-and-stats/probability-and-baselines/s04-04-fill-the-return"},{"id":"ml-math-and-stats/probability-and-baselines/s05-05-fix-the-overtrust"},{"id":"ml-math-and-stats/probability-and-baselines/s06-06-write-count-ready"},{"id":"ml-math-and-stats/probability-and-baselines/s07-07-checkpoint"}]},{"slug":"distributions-sampling-variance","steps":[{"id":"ml-math-and-stats/distributions-sampling-variance/s01-01-intro"},{"id":"ml-math-and-stats/distributions-sampling-variance/s02-02-choose-the-risk"},{"id":"ml-math-and-stats/distributions-sampling-variance/s03-03-predict-the-checks"},{"id":"ml-math-and-stats/distributions-sampling-variance/s04-04-fill-the-return"},{"id":"ml-math-and-stats/distributions-sampling-variance/s05-05-fix-the-overtrust"},{"id":"ml-math-and-stats/distributions-sampling-variance/s06-06-write-variance"},{"id":"ml-math-and-stats/distributions-sampling-variance/s07-07-checkpoint"}]},{"slug":"bias-variance-and-leakage","steps":[{"id":"ml-math-and-stats/bias-variance-and-leakage/s01-01-intro"},{"id":"ml-math-and-stats/bias-variance-and-leakage/s02-02-choose-the-risk"},{"id":"ml-math-and-stats/bias-variance-and-leakage/s03-03-predict-the-checks"},{"id":"ml-math-and-stats/bias-variance-and-leakage/s04-04-fill-the-return"},{"id":"ml-math-and-stats/bias-variance-and-leakage/s05-05-fix-the-overtrust"},{"id":"ml-math-and-stats/bias-variance-and-leakage/s06-06-write-diagnose"},{"id":"ml-math-and-stats/bias-variance-and-leakage/s07-07-checkpoint"}]},{"slug":"mission-statistical-sanity-check","steps":[{"id":"ml-math-and-stats/mission-statistical-sanity-check/s01-01-intro"},{"id":"ml-math-and-stats/mission-statistical-sanity-check/s02-02-choose-the-risk"},{"id":"ml-math-and-stats/mission-statistical-sanity-check/s03-03-predict-the-checks"},{"id":"ml-math-and-stats/mission-statistical-sanity-check/s04-04-fill-the-return"},{"id":"ml-math-and-stats/mission-statistical-sanity-check/s05-05-fix-the-overtrust"},{"id":"ml-math-and-stats/mission-statistical-sanity-check/s06-06-write-count-ready"},{"id":"ml-math-and-stats/mission-statistical-sanity-check/s07-07-checkpoint"}]}]},{"slug":"supervised-learning-workflows","lessons":[{"slug":"labels-features-splits","steps":[{"id":"supervised-learning-workflows/labels-features-splits/s01-01-intro"},{"id":"supervised-learning-workflows/labels-features-splits/s02-02-choose-the-risk"},{"id":"supervised-learning-workflows/labels-features-splits/s03-03-predict-the-checks"},{"id":"supervised-learning-workflows/labels-features-splits/s04-04-fill-the-return"},{"id":"supervised-learning-workflows/labels-features-splits/s05-05-fix-the-overtrust"},{"id":"supervised-learning-workflows/labels-features-splits/s06-06-write-split-audit"},{"id":"supervised-learning-workflows/labels-features-splits/s07-07-checkpoint"}]},{"slug":"baselines-before-fancy-models","steps":[{"id":"supervised-learning-workflows/baselines-before-fancy-models/s01-01-intro"},{"id":"supervised-learning-workflows/baselines-before-fancy-models/s02-02-choose-the-risk"},{"id":"supervised-learning-workflows/baselines-before-fancy-models/s03-03-predict-the-checks"},{"id":"supervised-learning-workflows/baselines-before-fancy-models/s04-04-fill-the-return"},{"id":"supervised-learning-workflows/baselines-before-fancy-models/s05-05-fix-the-overtrust"},{"id":"supervised-learning-workflows/baselines-before-fancy-models/s06-06-write-baseline-comparison"},{"id":"supervised-learning-workflows/baselines-before-fancy-models/s07-07-checkpoint"}]},{"slug":"training-and-prediction-loop","steps":[{"id":"supervised-learning-workflows/training-and-prediction-loop/s01-01-intro"},{"id":"supervised-learning-workflows/training-and-prediction-loop/s02-02-choose-the-risk"},{"id":"supervised-learning-workflows/training-and-prediction-loop/s03-03-predict-the-checks"},{"id":"supervised-learning-workflows/training-and-prediction-loop/s04-04-fill-the-return"},{"id":"supervised-learning-workflows/training-and-prediction-loop/s05-05-fix-the-overtrust"},{"id":"supervised-learning-workflows/training-and-prediction-loop/s06-06-write-train"},{"id":"supervised-learning-workflows/training-and-prediction-loop/s07-07-checkpoint"}]},{"slug":"overfitting-and-regularization","steps":[{"id":"supervised-learning-workflows/overfitting-and-regularization/s01-01-intro"},{"id":"supervised-learning-workflows/overfitting-and-regularization/s02-02-choose-the-risk"},{"id":"supervised-learning-workflows/overfitting-and-regularization/s03-03-predict-the-checks"},{"id":"supervised-learning-workflows/overfitting-and-regularization/s04-04-fill-the-return"},{"id":"supervised-learning-workflows/overfitting-and-regularization/s05-05-fix-the-overtrust"},{"id":"supervised-learning-workflows/overfitting-and-regularization/s06-06-write-overfit-audit"},{"id":"supervised-learning-workflows/overfitting-and-regularization/s07-07-checkpoint"}]},{"slug":"mission-baseline-model-showdown","steps":[{"id":"supervised-learning-workflows/mission-baseline-model-showdown/s01-01-intro"},{"id":"supervised-learning-workflows/mission-baseline-model-showdown/s02-02-choose-the-risk"},{"id":"supervised-learning-workflows/mission-baseline-model-showdown/s03-03-predict-the-checks"},{"id":"supervised-learning-workflows/mission-baseline-model-showdown/s04-04-fill-the-return"},{"id":"supervised-learning-workflows/mission-baseline-model-showdown/s05-05-fix-the-overtrust"},{"id":"supervised-learning-workflows/mission-baseline-model-showdown/s06-06-write-classifier-brief"},{"id":"supervised-learning-workflows/mission-baseline-model-showdown/s07-07-checkpoint"}]}]},{"slug":"unsupervised-learning-and-embeddings","lessons":[{"slug":"clustering-without-labels","steps":[{"id":"unsupervised-learning-and-embeddings/clustering-without-labels/s01-01-intro"},{"id":"unsupervised-learning-and-embeddings/clustering-without-labels/s02-02-choose-the-risk"},{"id":"unsupervised-learning-and-embeddings/clustering-without-labels/s03-03-predict-the-checks"},{"id":"unsupervised-learning-and-embeddings/clustering-without-labels/s04-04-fill-the-return"},{"id":"unsupervised-learning-and-embeddings/clustering-without-labels/s05-05-fix-the-overtrust"},{"id":"unsupervised-learning-and-embeddings/clustering-without-labels/s06-06-write-cluster-summary"},{"id":"unsupervised-learning-and-embeddings/clustering-without-labels/s07-07-checkpoint"}]},{"slug":"dimensionality-and-distance","steps":[{"id":"unsupervised-learning-and-embeddings/dimensionality-and-distance/s01-01-intro"},{"id":"unsupervised-learning-and-embeddings/dimensionality-and-distance/s02-02-choose-the-risk"},{"id":"unsupervised-learning-and-embeddings/dimensionality-and-distance/s03-03-predict-the-checks"},{"id":"unsupervised-learning-and-embeddings/dimensionality-and-distance/s04-04-fill-the-return"},{"id":"unsupervised-learning-and-embeddings/dimensionality-and-distance/s05-05-fix-the-overtrust"},{"id":"unsupervised-learning-and-embeddings/dimensionality-and-distance/s06-06-write-euclidean"},{"id":"unsupervised-learning-and-embeddings/dimensionality-and-distance/s07-07-checkpoint"}]},{"slug":"embeddings-as-features","steps":[{"id":"unsupervised-learning-and-embeddings/embeddings-as-features/s01-01-intro"},{"id":"unsupervised-learning-and-embeddings/embeddings-as-features/s02-02-choose-the-risk"},{"id":"unsupervised-learning-and-embeddings/embeddings-as-features/s03-03-predict-the-checks"},{"id":"unsupervised-learning-and-embeddings/embeddings-as-features/s04-04-fill-the-return"},{"id":"unsupervised-learning-and-embeddings/embeddings-as-features/s05-05-fix-the-overtrust"},{"id":"unsupervised-learning-and-embeddings/embeddings-as-features/s06-06-write-retrieval-receipt"},{"id":"unsupervised-learning-and-embeddings/embeddings-as-features/s07-07-checkpoint"}]},{"slug":"mission-tiny-recommender","steps":[{"id":"unsupervised-learning-and-embeddings/mission-tiny-recommender/s01-01-intro"},{"id":"unsupervised-learning-and-embeddings/mission-tiny-recommender/s02-02-choose-the-risk"},{"id":"unsupervised-learning-and-embeddings/mission-tiny-recommender/s03-03-predict-the-checks"},{"id":"unsupervised-learning-and-embeddings/mission-tiny-recommender/s04-04-fill-the-return"},{"id":"unsupervised-learning-and-embeddings/mission-tiny-recommender/s05-05-fix-the-overtrust"},{"id":"unsupervised-learning-and-embeddings/mission-tiny-recommender/s06-06-write-recommendation-card"},{"id":"unsupervised-learning-and-embeddings/mission-tiny-recommender/s07-07-checkpoint"}]}]},{"slug":"metrics-and-error-analysis","lessons":[{"slug":"confusion-matrix","steps":[{"id":"metrics-and-error-analysis/confusion-matrix/s01-01-intro"},{"id":"metrics-and-error-analysis/confusion-matrix/s02-02-choose-the-risk"},{"id":"metrics-and-error-analysis/confusion-matrix/s03-03-predict-the-checks"},{"id":"metrics-and-error-analysis/confusion-matrix/s04-04-fill-the-return"},{"id":"metrics-and-error-analysis/confusion-matrix/s05-05-fix-the-overtrust"},{"id":"metrics-and-error-analysis/confusion-matrix/s06-06-write-count-ready"},{"id":"metrics-and-error-analysis/confusion-matrix/s07-07-checkpoint"}]},{"slug":"precision-recall-thresholds","steps":[{"id":"metrics-and-error-analysis/precision-recall-thresholds/s01-01-intro"},{"id":"metrics-and-error-analysis/precision-recall-thresholds/s02-02-choose-the-risk"},{"id":"metrics-and-error-analysis/precision-recall-thresholds/s03-03-predict-the-checks"},{"id":"metrics-and-error-analysis/precision-recall-thresholds/s04-04-fill-the-return"},{"id":"metrics-and-error-analysis/precision-recall-thresholds/s05-05-fix-the-overtrust"},{"id":"metrics-and-error-analysis/precision-recall-thresholds/s06-06-write-count-ready"},{"id":"metrics-and-error-analysis/precision-recall-thresholds/s07-07-checkpoint"}]},{"slug":"slice-based-error-analysis","steps":[{"id":"metrics-and-error-analysis/slice-based-error-analysis/s01-01-intro"},{"id":"metrics-and-error-analysis/slice-based-error-analysis/s02-02-choose-the-risk"},{"id":"metrics-and-error-analysis/slice-based-error-analysis/s03-03-predict-the-checks"},{"id":"metrics-and-error-analysis/slice-based-error-analysis/s04-04-fill-the-return"},{"id":"metrics-and-error-analysis/slice-based-error-analysis/s05-05-fix-the-overtrust"},{"id":"metrics-and-error-analysis/slice-based-error-analysis/s06-06-write-count-ready"},{"id":"metrics-and-error-analysis/slice-based-error-analysis/s07-07-checkpoint"}]},{"slug":"regression-metrics-and-residuals","steps":[{"id":"metrics-and-error-analysis/regression-metrics-and-residuals/s01-01-intro"},{"id":"metrics-and-error-analysis/regression-metrics-and-residuals/s02-02-choose-the-risk"},{"id":"metrics-and-error-analysis/regression-metrics-and-residuals/s03-03-predict-the-checks"},{"id":"metrics-and-error-analysis/regression-metrics-and-residuals/s04-04-fill-the-return"},{"id":"metrics-and-error-analysis/regression-metrics-and-residuals/s05-05-fix-the-overtrust"},{"id":"metrics-and-error-analysis/regression-metrics-and-residuals/s06-06-write-count-ready"},{"id":"metrics-and-error-analysis/regression-metrics-and-residuals/s07-07-checkpoint"}]},{"slug":"mission-confusion-matrix-triage","steps":[{"id":"metrics-and-error-analysis/mission-confusion-matrix-triage/s01-01-intro"},{"id":"metrics-and-error-analysis/mission-confusion-matrix-triage/s02-02-choose-the-risk"},{"id":"metrics-and-error-analysis/mission-confusion-matrix-triage/s03-03-predict-the-checks"},{"id":"metrics-and-error-analysis/mission-confusion-matrix-triage/s04-04-fill-the-return"},{"id":"metrics-and-error-analysis/mission-confusion-matrix-triage/s05-05-fix-the-overtrust"},{"id":"metrics-and-error-analysis/mission-confusion-matrix-triage/s06-06-write-count-ready"},{"id":"metrics-and-error-analysis/mission-confusion-matrix-triage/s07-07-checkpoint"}]}]},{"slug":"pytorch-tensors-and-autograd","lessons":[{"slug":"tensors-and-shapes","steps":[{"id":"pytorch-tensors-and-autograd/tensors-and-shapes/s01-01-intro"},{"id":"pytorch-tensors-and-autograd/tensors-and-shapes/s02-02-choose-the-risk"},{"id":"pytorch-tensors-and-autograd/tensors-and-shapes/s03-03-predict-the-checks"},{"id":"pytorch-tensors-and-autograd/tensors-and-shapes/s04-04-fill-the-return"},{"id":"pytorch-tensors-and-autograd/tensors-and-shapes/s05-05-fix-the-overtrust"},{"id":"pytorch-tensors-and-autograd/tensors-and-shapes/s06-06-write-count-ready"},{"id":"pytorch-tensors-and-autograd/tensors-and-shapes/s07-07-checkpoint"}]},{"slug":"broadcasting-and-vectorization","steps":[{"id":"pytorch-tensors-and-autograd/broadcasting-and-vectorization/s01-01-intro"},{"id":"pytorch-tensors-and-autograd/broadcasting-and-vectorization/s02-02-choose-the-risk"},{"id":"pytorch-tensors-and-autograd/broadcasting-and-vectorization/s03-03-predict-the-checks"},{"id":"pytorch-tensors-and-autograd/broadcasting-and-vectorization/s04-04-fill-the-return"},{"id":"pytorch-tensors-and-autograd/broadcasting-and-vectorization/s05-05-fix-the-overtrust"},{"id":"pytorch-tensors-and-autograd/broadcasting-and-vectorization/s06-06-write-count-ready"},{"id":"pytorch-tensors-and-autograd/broadcasting-and-vectorization/s07-07-checkpoint"}]},{"slug":"autograd-mental-model","steps":[{"id":"pytorch-tensors-and-autograd/autograd-mental-model/s01-01-intro"},{"id":"pytorch-tensors-and-autograd/autograd-mental-model/s02-02-choose-the-risk"},{"id":"pytorch-tensors-and-autograd/autograd-mental-model/s03-03-predict-the-checks"},{"id":"pytorch-tensors-and-autograd/autograd-mental-model/s04-04-fill-the-return"},{"id":"pytorch-tensors-and-autograd/autograd-mental-model/s05-05-fix-the-overtrust"},{"id":"pytorch-tensors-and-autograd/autograd-mental-model/s06-06-write-count-ready"},{"id":"pytorch-tensors-and-autograd/autograd-mental-model/s07-07-checkpoint"}]},{"slug":"mission-tensor-playground","steps":[{"id":"pytorch-tensors-and-autograd/mission-tensor-playground/s01-01-intro"},{"id":"pytorch-tensors-and-autograd/mission-tensor-playground/s02-02-choose-the-risk"},{"id":"pytorch-tensors-and-autograd/mission-tensor-playground/s03-03-predict-the-checks"},{"id":"pytorch-tensors-and-autograd/mission-tensor-playground/s04-04-fill-the-return"},{"id":"pytorch-tensors-and-autograd/mission-tensor-playground/s05-05-fix-the-overtrust"},{"id":"pytorch-tensors-and-autograd/mission-tensor-playground/s06-06-write-count-ready"},{"id":"pytorch-tensors-and-autograd/mission-tensor-playground/s07-07-checkpoint"}]}]},{"slug":"training-loops-and-optimizers","lessons":[{"slug":"loss-forward-backward-step","steps":[{"id":"training-loops-and-optimizers/loss-forward-backward-step/s01-01-intro"},{"id":"training-loops-and-optimizers/loss-forward-backward-step/s02-02-choose-the-risk"},{"id":"training-loops-and-optimizers/loss-forward-backward-step/s03-03-predict-the-checks"},{"id":"training-loops-and-optimizers/loss-forward-backward-step/s04-04-fill-the-return"},{"id":"training-loops-and-optimizers/loss-forward-backward-step/s05-05-fix-the-overtrust"},{"id":"training-loops-and-optimizers/loss-forward-backward-step/s06-06-write-count-ready"},{"id":"training-loops-and-optimizers/loss-forward-backward-step/s07-07-checkpoint"}]},{"slug":"gradient-descent-by-hand","steps":[{"id":"training-loops-and-optimizers/gradient-descent-by-hand/s01-01-intro"},{"id":"training-loops-and-optimizers/gradient-descent-by-hand/s02-02-choose-the-risk"},{"id":"training-loops-and-optimizers/gradient-descent-by-hand/s03-03-predict-the-checks"},{"id":"training-loops-and-optimizers/gradient-descent-by-hand/s04-04-fill-the-return"},{"id":"training-loops-and-optimizers/gradient-descent-by-hand/s05-05-fix-the-overtrust"},{"id":"training-loops-and-optimizers/gradient-descent-by-hand/s06-06-write-count-ready"},{"id":"training-loops-and-optimizers/gradient-descent-by-hand/s07-07-checkpoint"}]},{"slug":"optimizers-and-schedulers","steps":[{"id":"training-loops-and-optimizers/optimizers-and-schedulers/s01-01-intro"},{"id":"training-loops-and-optimizers/optimizers-and-schedulers/s02-02-choose-the-risk"},{"id":"training-loops-and-optimizers/optimizers-and-schedulers/s03-03-predict-the-checks"},{"id":"training-loops-and-optimizers/optimizers-and-schedulers/s04-04-fill-the-return"},{"id":"training-loops-and-optimizers/optimizers-and-schedulers/s05-05-fix-the-overtrust"},{"id":"training-loops-and-optimizers/optimizers-and-schedulers/s06-06-write-count-ready"},{"id":"training-loops-and-optimizers/optimizers-and-schedulers/s07-07-checkpoint"}]},{"slug":"checkpoints-and-reproducibility","steps":[{"id":"training-loops-and-optimizers/checkpoints-and-reproducibility/s01-01-intro"},{"id":"training-loops-and-optimizers/checkpoints-and-reproducibility/s02-02-choose-the-risk"},{"id":"training-loops-and-optimizers/checkpoints-and-reproducibility/s03-03-predict-the-checks"},{"id":"training-loops-and-optimizers/checkpoints-and-reproducibility/s04-04-fill-the-return"},{"id":"training-loops-and-optimizers/checkpoints-and-reproducibility/s05-05-fix-the-overtrust"},{"id":"training-loops-and-optimizers/checkpoints-and-reproducibility/s06-06-write-count-ready"},{"id":"training-loops-and-optimizers/checkpoints-and-reproducibility/s07-07-checkpoint"}]},{"slug":"mission-overfit-then-recover","steps":[{"id":"training-loops-and-optimizers/mission-overfit-then-recover/s01-01-intro"},{"id":"training-loops-and-optimizers/mission-overfit-then-recover/s02-02-choose-the-risk"},{"id":"training-loops-and-optimizers/mission-overfit-then-recover/s03-03-predict-the-checks"},{"id":"training-loops-and-optimizers/mission-overfit-then-recover/s04-04-fill-the-return"},{"id":"training-loops-and-optimizers/mission-overfit-then-recover/s05-05-fix-the-overtrust"},{"id":"training-loops-and-optimizers/mission-overfit-then-recover/s06-06-write-count-ready"},{"id":"training-loops-and-optimizers/mission-overfit-then-recover/s07-07-checkpoint"}]}]},{"slug":"deep-learning-architectures","lessons":[{"slug":"cnns-and-local-patterns","steps":[{"id":"deep-learning-architectures/cnns-and-local-patterns/s01-01-intro"},{"id":"deep-learning-architectures/cnns-and-local-patterns/s02-02-choose-the-risk"},{"id":"deep-learning-architectures/cnns-and-local-patterns/s03-03-predict-the-checks"},{"id":"deep-learning-architectures/cnns-and-local-patterns/s04-04-fill-the-return"},{"id":"deep-learning-architectures/cnns-and-local-patterns/s05-05-fix-the-overtrust"},{"id":"deep-learning-architectures/cnns-and-local-patterns/s06-06-write-count-ready"},{"id":"deep-learning-architectures/cnns-and-local-patterns/s07-07-checkpoint"}]},{"slug":"tokenizers-and-context-budget","steps":[{"id":"deep-learning-architectures/tokenizers-and-context-budget/s01-01-intro"},{"id":"deep-learning-architectures/tokenizers-and-context-budget/s02-02-choose-the-risk"},{"id":"deep-learning-architectures/tokenizers-and-context-budget/s03-03-predict-the-checks"},{"id":"deep-learning-architectures/tokenizers-and-context-budget/s04-04-fill-the-return"},{"id":"deep-learning-architectures/tokenizers-and-context-budget/s05-05-fix-the-overtrust"},{"id":"deep-learning-architectures/tokenizers-and-context-budget/s06-06-write-count-ready"},{"id":"deep-learning-architectures/tokenizers-and-context-budget/s07-07-checkpoint"}]},{"slug":"attention-and-transformer-blocks","steps":[{"id":"deep-learning-architectures/attention-and-transformer-blocks/s01-01-intro"},{"id":"deep-learning-architectures/attention-and-transformer-blocks/s02-02-choose-the-risk"},{"id":"deep-learning-architectures/attention-and-transformer-blocks/s03-03-predict-the-checks"},{"id":"deep-learning-architectures/attention-and-transformer-blocks/s04-04-fill-the-return"},{"id":"deep-learning-architectures/attention-and-transformer-blocks/s05-05-fix-the-overtrust"},{"id":"deep-learning-architectures/attention-and-transformer-blocks/s06-06-write-count-ready"},{"id":"deep-learning-architectures/attention-and-transformer-blocks/s07-07-checkpoint"}]},{"slug":"decoding-kv-cache-quantization","steps":[{"id":"deep-learning-architectures/decoding-kv-cache-quantization/s01-01-intro"},{"id":"deep-learning-architectures/decoding-kv-cache-quantization/s02-02-choose-the-risk"},{"id":"deep-learning-architectures/decoding-kv-cache-quantization/s03-03-predict-the-checks"},{"id":"deep-learning-architectures/decoding-kv-cache-quantization/s04-04-fill-the-return"},{"id":"deep-learning-architectures/decoding-kv-cache-quantization/s05-05-fix-the-overtrust"},{"id":"deep-learning-architectures/decoding-kv-cache-quantization/s06-06-write-count-ready"},{"id":"deep-learning-architectures/decoding-kv-cache-quantization/s07-07-checkpoint"}]},{"slug":"mission-architecture-tradeoff-note","steps":[{"id":"deep-learning-architectures/mission-architecture-tradeoff-note/s01-01-intro"},{"id":"deep-learning-architectures/mission-architecture-tradeoff-note/s02-02-choose-the-risk"},{"id":"deep-learning-architectures/mission-architecture-tradeoff-note/s03-03-predict-the-checks"},{"id":"deep-learning-architectures/mission-architecture-tradeoff-note/s04-04-fill-the-return"},{"id":"deep-learning-architectures/mission-architecture-tradeoff-note/s05-05-fix-the-overtrust"},{"id":"deep-learning-architectures/mission-architecture-tradeoff-note/s06-06-write-count-ready"},{"id":"deep-learning-architectures/mission-architecture-tradeoff-note/s07-07-checkpoint"}]}]},{"slug":"feature-experiments-registries","lessons":[{"slug":"feature-pipeline-contracts","steps":[{"id":"feature-experiments-registries/feature-pipeline-contracts/s01-01-intro"},{"id":"feature-experiments-registries/feature-pipeline-contracts/s02-02-choose-the-risk"},{"id":"feature-experiments-registries/feature-pipeline-contracts/s03-03-predict-the-checks"},{"id":"feature-experiments-registries/feature-pipeline-contracts/s04-04-fill-the-return"},{"id":"feature-experiments-registries/feature-pipeline-contracts/s05-05-fix-the-overtrust"},{"id":"feature-experiments-registries/feature-pipeline-contracts/s06-06-write-count-ready"},{"id":"feature-experiments-registries/feature-pipeline-contracts/s07-07-checkpoint"}]},{"slug":"train-inference-skew","steps":[{"id":"feature-experiments-registries/train-inference-skew/s01-01-intro"},{"id":"feature-experiments-registries/train-inference-skew/s02-02-choose-the-risk"},{"id":"feature-experiments-registries/train-inference-skew/s03-03-predict-the-checks"},{"id":"feature-experiments-registries/train-inference-skew/s04-04-fill-the-return"},{"id":"feature-experiments-registries/train-inference-skew/s05-05-fix-the-overtrust"},{"id":"feature-experiments-registries/train-inference-skew/s06-06-write-count-ready"},{"id":"feature-experiments-registries/train-inference-skew/s07-07-checkpoint"}]},{"slug":"experiment-tracker-lite","steps":[{"id":"feature-experiments-registries/experiment-tracker-lite/s01-01-intro"},{"id":"feature-experiments-registries/experiment-tracker-lite/s02-02-choose-the-risk"},{"id":"feature-experiments-registries/experiment-tracker-lite/s03-03-predict-the-checks"},{"id":"feature-experiments-registries/experiment-tracker-lite/s04-04-fill-the-return"},{"id":"feature-experiments-registries/experiment-tracker-lite/s05-05-fix-the-overtrust"},{"id":"feature-experiments-registries/experiment-tracker-lite/s06-06-write-count-ready"},{"id":"feature-experiments-registries/experiment-tracker-lite/s07-07-checkpoint"}]},{"slug":"model-registry-shape","steps":[{"id":"feature-experiments-registries/model-registry-shape/s01-01-intro"},{"id":"feature-experiments-registries/model-registry-shape/s02-02-choose-the-risk"},{"id":"feature-experiments-registries/model-registry-shape/s03-03-predict-the-checks"},{"id":"feature-experiments-registries/model-registry-shape/s04-04-fill-the-return"},{"id":"feature-experiments-registries/model-registry-shape/s05-05-fix-the-overtrust"},{"id":"feature-experiments-registries/model-registry-shape/s06-06-write-count-ready"},{"id":"feature-experiments-registries/model-registry-shape/s07-07-checkpoint"}]},{"slug":"mission-feature-pipeline-and-tracker","steps":[{"id":"feature-experiments-registries/mission-feature-pipeline-and-tracker/s01-01-intro"},{"id":"feature-experiments-registries/mission-feature-pipeline-and-tracker/s02-02-choose-the-risk"},{"id":"feature-experiments-registries/mission-feature-pipeline-and-tracker/s03-03-predict-the-checks"},{"id":"feature-experiments-registries/mission-feature-pipeline-and-tracker/s04-04-fill-the-return"},{"id":"feature-experiments-registries/mission-feature-pipeline-and-tracker/s05-05-fix-the-overtrust"},{"id":"feature-experiments-registries/mission-feature-pipeline-and-tracker/s06-06-write-count-ready"},{"id":"feature-experiments-registries/mission-feature-pipeline-and-tracker/s07-07-checkpoint"}]}]},{"slug":"model-serving-and-mlops","lessons":[{"slug":"fastapi-inference-shape","steps":[{"id":"model-serving-and-mlops/fastapi-inference-shape/s01-01-intro"},{"id":"model-serving-and-mlops/fastapi-inference-shape/s02-02-choose-the-risk"},{"id":"model-serving-and-mlops/fastapi-inference-shape/s03-03-predict-the-checks"},{"id":"model-serving-and-mlops/fastapi-inference-shape/s04-04-fill-the-return"},{"id":"model-serving-and-mlops/fastapi-inference-shape/s05-05-fix-the-overtrust"},{"id":"model-serving-and-mlops/fastapi-inference-shape/s06-06-write-count-ready"},{"id":"model-serving-and-mlops/fastapi-inference-shape/s07-07-checkpoint"}]},{"slug":"batch-vs-realtime-serving","steps":[{"id":"model-serving-and-mlops/batch-vs-realtime-serving/s01-01-intro"},{"id":"model-serving-and-mlops/batch-vs-realtime-serving/s02-02-choose-the-risk"},{"id":"model-serving-and-mlops/batch-vs-realtime-serving/s03-03-predict-the-checks"},{"id":"model-serving-and-mlops/batch-vs-realtime-serving/s04-04-fill-the-return"},{"id":"model-serving-and-mlops/batch-vs-realtime-serving/s05-05-fix-the-overtrust"},{"id":"model-serving-and-mlops/batch-vs-realtime-serving/s06-06-write-count-ready"},{"id":"model-serving-and-mlops/batch-vs-realtime-serving/s07-07-checkpoint"}]},{"slug":"docker-runtime-and-config","steps":[{"id":"model-serving-and-mlops/docker-runtime-and-config/s01-01-intro"},{"id":"model-serving-and-mlops/docker-runtime-and-config/s02-02-choose-the-risk"},{"id":"model-serving-and-mlops/docker-runtime-and-config/s03-03-predict-the-checks"},{"id":"model-serving-and-mlops/docker-runtime-and-config/s04-04-fill-the-return"},{"id":"model-serving-and-mlops/docker-runtime-and-config/s05-05-fix-the-overtrust"},{"id":"model-serving-and-mlops/docker-runtime-and-config/s06-06-write-count-ready"},{"id":"model-serving-and-mlops/docker-runtime-and-config/s07-07-checkpoint"}]},{"slug":"github-actions-validation-gates","steps":[{"id":"model-serving-and-mlops/github-actions-validation-gates/s01-01-intro"},{"id":"model-serving-and-mlops/github-actions-validation-gates/s02-02-choose-the-risk"},{"id":"model-serving-and-mlops/github-actions-validation-gates/s03-03-predict-the-checks"},{"id":"model-serving-and-mlops/github-actions-validation-gates/s04-04-fill-the-return"},{"id":"model-serving-and-mlops/github-actions-validation-gates/s05-05-fix-the-overtrust"},{"id":"model-serving-and-mlops/github-actions-validation-gates/s06-06-write-failing-checks"},{"id":"model-serving-and-mlops/github-actions-validation-gates/s07-07-checkpoint"}]},{"slug":"continuous-training-and-rollout","steps":[{"id":"model-serving-and-mlops/continuous-training-and-rollout/s01-01-intro"},{"id":"model-serving-and-mlops/continuous-training-and-rollout/s02-02-choose-the-risk"},{"id":"model-serving-and-mlops/continuous-training-and-rollout/s03-03-predict-the-checks"},{"id":"model-serving-and-mlops/continuous-training-and-rollout/s04-04-fill-the-return"},{"id":"model-serving-and-mlops/continuous-training-and-rollout/s05-05-fix-the-overtrust"},{"id":"model-serving-and-mlops/continuous-training-and-rollout/s06-06-write-count-ready"},{"id":"model-serving-and-mlops/continuous-training-and-rollout/s07-07-checkpoint"}]},{"slug":"mission-fastapi-model-server","steps":[{"id":"model-serving-and-mlops/mission-fastapi-model-server/s01-01-intro"},{"id":"model-serving-and-mlops/mission-fastapi-model-server/s02-02-choose-the-risk"},{"id":"model-serving-and-mlops/mission-fastapi-model-server/s03-03-predict-the-checks"},{"id":"model-serving-and-mlops/mission-fastapi-model-server/s04-04-fill-the-return"},{"id":"model-serving-and-mlops/mission-fastapi-model-server/s05-05-fix-the-overtrust"},{"id":"model-serving-and-mlops/mission-fastapi-model-server/s06-06-write-count-ready"},{"id":"model-serving-and-mlops/mission-fastapi-model-server/s07-07-checkpoint"}]}]},{"slug":"monitoring-cloud-portfolio","lessons":[{"slug":"structured-logs-and-alerts","steps":[{"id":"monitoring-cloud-portfolio/structured-logs-and-alerts/s01-01-intro"},{"id":"monitoring-cloud-portfolio/structured-logs-and-alerts/s02-02-choose-the-risk"},{"id":"monitoring-cloud-portfolio/structured-logs-and-alerts/s03-03-predict-the-checks"},{"id":"monitoring-cloud-portfolio/structured-logs-and-alerts/s04-04-fill-the-return"},{"id":"monitoring-cloud-portfolio/structured-logs-and-alerts/s05-05-fix-the-overtrust"},{"id":"monitoring-cloud-portfolio/structured-logs-and-alerts/s06-06-write-count-ready"},{"id":"monitoring-cloud-portfolio/structured-logs-and-alerts/s07-07-checkpoint"}]},{"slug":"data-and-concept-drift","steps":[{"id":"monitoring-cloud-portfolio/data-and-concept-drift/s01-01-intro"},{"id":"monitoring-cloud-portfolio/data-and-concept-drift/s02-02-choose-the-risk"},{"id":"monitoring-cloud-portfolio/data-and-concept-drift/s03-03-predict-the-checks"},{"id":"monitoring-cloud-portfolio/data-and-concept-drift/s04-04-fill-the-return"},{"id":"monitoring-cloud-portfolio/data-and-concept-drift/s05-05-fix-the-overtrust"},{"id":"monitoring-cloud-portfolio/data-and-concept-drift/s06-06-write-count-ready"},{"id":"monitoring-cloud-portfolio/data-and-concept-drift/s07-07-checkpoint"}]},{"slug":"retraining-triggers","steps":[{"id":"monitoring-cloud-portfolio/retraining-triggers/s01-01-intro"},{"id":"monitoring-cloud-portfolio/retraining-triggers/s02-02-choose-the-risk"},{"id":"monitoring-cloud-portfolio/retraining-triggers/s03-03-predict-the-checks"},{"id":"monitoring-cloud-portfolio/retraining-triggers/s04-04-fill-the-return"},{"id":"monitoring-cloud-portfolio/retraining-triggers/s05-05-fix-the-overtrust"},{"id":"monitoring-cloud-portfolio/retraining-triggers/s06-06-write-count-ready"},{"id":"monitoring-cloud-portfolio/retraining-triggers/s07-07-checkpoint"}]},{"slug":"cloud-gpu-kubernetes-cost","steps":[{"id":"monitoring-cloud-portfolio/cloud-gpu-kubernetes-cost/s01-01-intro"},{"id":"monitoring-cloud-portfolio/cloud-gpu-kubernetes-cost/s02-02-choose-the-risk"},{"id":"monitoring-cloud-portfolio/cloud-gpu-kubernetes-cost/s03-03-predict-the-checks"},{"id":"monitoring-cloud-portfolio/cloud-gpu-kubernetes-cost/s04-04-fill-the-return"},{"id":"monitoring-cloud-portfolio/cloud-gpu-kubernetes-cost/s05-05-fix-the-overtrust"},{"id":"monitoring-cloud-portfolio/cloud-gpu-kubernetes-cost/s06-06-write-count-ready"},{"id":"monitoring-cloud-portfolio/cloud-gpu-kubernetes-cost/s07-07-checkpoint"}]},{"slug":"portfolio-architecture-docs","steps":[{"id":"monitoring-cloud-portfolio/portfolio-architecture-docs/s01-01-intro"},{"id":"monitoring-cloud-portfolio/portfolio-architecture-docs/s02-02-choose-the-risk"},{"id":"monitoring-cloud-portfolio/portfolio-architecture-docs/s03-03-predict-the-checks"},{"id":"monitoring-cloud-portfolio/portfolio-architecture-docs/s04-04-fill-the-return"},{"id":"monitoring-cloud-portfolio/portfolio-architecture-docs/s05-05-fix-the-overtrust"},{"id":"monitoring-cloud-portfolio/portfolio-architecture-docs/s06-06-write-count-ready"},{"id":"monitoring-cloud-portfolio/portfolio-architecture-docs/s07-07-checkpoint"}]},{"slug":"mission-final-portfolio-ml-system","steps":[{"id":"monitoring-cloud-portfolio/mission-final-portfolio-ml-system/s01-01-intro"},{"id":"monitoring-cloud-portfolio/mission-final-portfolio-ml-system/s02-02-choose-the-risk"},{"id":"monitoring-cloud-portfolio/mission-final-portfolio-ml-system/s03-03-predict-the-checks"},{"id":"monitoring-cloud-portfolio/mission-final-portfolio-ml-system/s04-04-fill-the-return"},{"id":"monitoring-cloud-portfolio/mission-final-portfolio-ml-system/s05-05-fix-the-overtrust"},{"id":"monitoring-cloud-portfolio/mission-final-portfolio-ml-system/s06-06-write-decide"},{"id":"monitoring-cloud-portfolio/mission-final-portfolio-ml-system/s07-07-checkpoint"}]}]},{"slug":"graphic-design-studio","lessons":[{"slug":"prompting-like-an-art-director","steps":[{"id":"graphic-design-studio/prompting-like-an-art-director/s01-01-the-prompt-is-a-creative-brief"},{"id":"graphic-design-studio/prompting-like-an-art-director/s02-02-style-language"},{"id":"graphic-design-studio/prompting-like-an-art-director/s03-03-which-tool-for-the-headline"},{"id":"graphic-design-studio/prompting-like-an-art-director/s04-04-predict-the-scaffold"},{"id":"graphic-design-studio/prompting-like-an-art-director/s05-05-negative-space-and-the-iteration-loop"},{"id":"graphic-design-studio/prompting-like-an-art-director/s06-06-fix-the-mood-word-prompt"},{"id":"graphic-design-studio/prompting-like-an-art-director/s07-07-write-prompt-linter"},{"id":"graphic-design-studio/prompting-like-an-art-director/s08-08-checkpoint"}]},{"slug":"the-design-kit","steps":[{"id":"graphic-design-studio/the-design-kit/s01-01-the-brand-bible-as-data"},{"id":"graphic-design-studio/the-design-kit/s02-02-fill-the-palette-line"},{"id":"graphic-design-studio/the-design-kit/s03-03-banned-looks"},{"id":"graphic-design-studio/the-design-kit/s04-04-predict-the-negatives"},{"id":"graphic-design-studio/the-design-kit/s05-05-which-field-failed"},{"id":"graphic-design-studio/the-design-kit/s06-06-fix-the-crossed-kit"},{"id":"graphic-design-studio/the-design-kit/s07-07-write-contrast-check"},{"id":"graphic-design-studio/the-design-kit/s08-08-tokens-for-the-interface"},{"id":"graphic-design-studio/the-design-kit/s09-09-write-token-audit"},{"id":"graphic-design-studio/the-design-kit/s10-10-checkpoint"}]},{"slug":"fifty-assets-one-brand","steps":[{"id":"graphic-design-studio/fifty-assets-one-brand/s01-01-the-consistency-problem"},{"id":"graphic-design-studio/fifty-assets-one-brand/s02-02-seeds-the-same-dice-twice"},{"id":"graphic-design-studio/fifty-assets-one-brand/s03-03-why-does-the-mascot-drift"},{"id":"graphic-design-studio/fifty-assets-one-brand/s04-04-predict-the-batch-plan"},{"id":"graphic-design-studio/fifty-assets-one-brand/s05-05-the-qa-filter"},{"id":"graphic-design-studio/fifty-assets-one-brand/s06-06-defend-the-pick"},{"id":"graphic-design-studio/fifty-assets-one-brand/s07-07-fix-the-qa-threshold"},{"id":"graphic-design-studio/fifty-assets-one-brand/s08-08-write-palette-distance"},{"id":"graphic-design-studio/fifty-assets-one-brand/s09-09-checkpoint"}]}]},{"slug":"campaign-studio","lessons":[{"slug":"voice-pack-as-data","steps":[{"id":"campaign-studio/voice-pack-as-data/s01-01-the-campaign-and-the-gate"},{"id":"campaign-studio/voice-pack-as-data/s02-02-lint-the-draft"},{"id":"campaign-studio/voice-pack-as-data/s03-03-predict-the-violations"},{"id":"campaign-studio/voice-pack-as-data/s04-04-testable-or-mood"},{"id":"campaign-studio/voice-pack-as-data/s05-05-fill-the-linter"},{"id":"campaign-studio/voice-pack-as-data/s06-06-variants-as-records"},{"id":"campaign-studio/voice-pack-as-data/s07-07-write-lint-copy"},{"id":"campaign-studio/voice-pack-as-data/s08-08-checkpoint"}]},{"slug":"batch-plan-and-calendar","steps":[{"id":"campaign-studio/batch-plan-and-calendar/s01-01-slots-before-prompts"},{"id":"campaign-studio/batch-plan-and-calendar/s02-02-which-field-is-missing"},{"id":"campaign-studio/batch-plan-and-calendar/s03-03-write-batch-plan"},{"id":"campaign-studio/batch-plan-and-calendar/s04-04-the-calendar-is-data"},{"id":"campaign-studio/batch-plan-and-calendar/s05-05-predict-the-queue"},{"id":"campaign-studio/batch-plan-and-calendar/s06-06-fix-the-gate"},{"id":"campaign-studio/batch-plan-and-calendar/s07-07-checkpoint"}]},{"slug":"the-numbers-pass","steps":[{"id":"campaign-studio/the-numbers-pass/s01-01-a-report-is-a-draft-over-data"},{"id":"campaign-studio/the-numbers-pass/s02-02-predict-the-verdict"},{"id":"campaign-studio/the-numbers-pass/s03-03-write-verify-numbers"},{"id":"campaign-studio/the-numbers-pass/s04-04-denominators-and-the-ftc"},{"id":"campaign-studio/the-numbers-pass/s05-05-what-may-not-ship"},{"id":"campaign-studio/the-numbers-pass/s06-06-fill-the-policy-router"},{"id":"campaign-studio/the-numbers-pass/s07-07-checkpoint"}]},{"slug":"synthetic-creator-detection","steps":[{"id":"campaign-studio/synthetic-creator-detection/s01-01-mass-ugc-as-a-channel"},{"id":"campaign-studio/synthetic-creator-detection/s02-02-what-the-job-is"},{"id":"campaign-studio/synthetic-creator-detection/s03-03-run-the-ugc-channel"},{"id":"campaign-studio/synthetic-creator-detection/s04-04-predict-the-ship"},{"id":"campaign-studio/synthetic-creator-detection/s05-05-what-clears-the-gate"},{"id":"campaign-studio/synthetic-creator-detection/s06-06-fill-the-batch-line"},{"id":"campaign-studio/synthetic-creator-detection/s07-07-write-ship-checklist"},{"id":"campaign-studio/synthetic-creator-detection/s08-08-checkpoint"}]}]},{"slug":"support-studio","lessons":[{"slug":"the-policy-pack","steps":[{"id":"support-studio/the-policy-pack/s01-01-the-reply-that-binds-the-company"},{"id":"support-studio/the-policy-pack/s02-02-the-pack-as-data"},{"id":"support-studio/the-policy-pack/s03-03-spot-the-banned-promise"},{"id":"support-studio/the-policy-pack/s04-04-predict-the-lint"},{"id":"support-studio/the-policy-pack/s05-05-fix-the-stale-citation"},{"id":"support-studio/the-policy-pack/s06-06-the-review-loop-evidence"},{"id":"support-studio/the-policy-pack/s07-07-write-lint-draft"},{"id":"support-studio/the-policy-pack/s08-08-checkpoint"}]},{"slug":"golden-evals-earn-autonomy","steps":[{"id":"support-studio/golden-evals-earn-autonomy/s01-01-the-klarna-arc"},{"id":"support-studio/golden-evals-earn-autonomy/s02-02-a-macro-is-three-things"},{"id":"support-studio/golden-evals-earn-autonomy/s03-03-inside-the-lane"},{"id":"support-studio/golden-evals-earn-autonomy/s04-04-predict-the-eval-run"},{"id":"support-studio/golden-evals-earn-autonomy/s05-05-fill-the-promotion-rule"},{"id":"support-studio/golden-evals-earn-autonomy/s06-06-write-run-golden-evals"},{"id":"support-studio/golden-evals-earn-autonomy/s07-07-checkpoint"}]},{"slug":"the-escalation-boundary","steps":[{"id":"support-studio/the-escalation-boundary/s01-01-drafting-is-not-spending"},{"id":"support-studio/the-escalation-boundary/s02-02-triggers-as-conditions"},{"id":"support-studio/the-escalation-boundary/s03-03-route-this-ticket"},{"id":"support-studio/the-escalation-boundary/s04-04-predict-the-routing"},{"id":"support-studio/the-escalation-boundary/s05-05-fix-the-refund-hole"},{"id":"support-studio/the-escalation-boundary/s06-06-disclosure-and-the-kill-switch"},{"id":"support-studio/the-escalation-boundary/s07-07-write-route-ticket"},{"id":"support-studio/the-escalation-boundary/s08-08-checkpoint"}]}]},{"slug":"copy-studio","lessons":[{"slug":"the-voice-fingerprint","steps":[{"id":"copy-studio/the-voice-fingerprint/s01-01-the-client-you-inherit"},{"id":"copy-studio/the-voice-fingerprint/s02-02-the-fingerprint"},{"id":"copy-studio/the-voice-fingerprint/s03-03-predict-the-ceiling"},{"id":"copy-studio/the-voice-fingerprint/s04-04-the-samples-say-otherwise"},{"id":"copy-studio/the-voice-fingerprint/s05-05-fill-derive-the-rules"},{"id":"copy-studio/the-voice-fingerprint/s06-06-the-pack-with-provenance"},{"id":"copy-studio/the-voice-fingerprint/s07-07-write-fingerprint"},{"id":"copy-studio/the-voice-fingerprint/s08-08-checkpoint"}]},{"slug":"variants-that-hold-the-line","steps":[{"id":"copy-studio/variants-that-hold-the-line/s01-01-twelve-by-thursday"},{"id":"copy-studio/variants-that-hold-the-line/s02-02-the-drift-problem"},{"id":"copy-studio/variants-that-hold-the-line/s03-03-predict-the-drift-report"},{"id":"copy-studio/variants-that-hold-the-line/s04-04-which-subject-line-ships"},{"id":"copy-studio/variants-that-hold-the-line/s05-05-fix-the-channel-check"},{"id":"copy-studio/variants-that-hold-the-line/s06-06-the-kill-log"},{"id":"copy-studio/variants-that-hold-the-line/s07-07-write-voice-gate"},{"id":"copy-studio/variants-that-hold-the-line/s08-08-checkpoint"}]},{"slug":"the-claim-check","steps":[{"id":"copy-studio/the-claim-check/s01-01-forty-one-of-seventy-seven"},{"id":"copy-studio/the-claim-check/s02-02-what-counts-as-checkable"},{"id":"copy-studio/the-claim-check/s03-03-predict-the-claim-list"},{"id":"copy-studio/the-claim-check/s04-04-what-closes-a-row"},{"id":"copy-studio/the-claim-check/s05-05-fill-the-ship-decision"},{"id":"copy-studio/the-claim-check/s06-06-the-corrections-log"},{"id":"copy-studio/the-claim-check/s07-07-write-ship-gate"},{"id":"copy-studio/the-claim-check/s08-08-checkpoint"}]}]},{"slug":"analytics-studio","lessons":[{"slug":"the-cleaning-log","steps":[{"id":"analytics-studio/the-cleaning-log/s01-01-where-did-those-rows-go"},{"id":"analytics-studio/the-cleaning-log/s02-02-the-log-as-data"},{"id":"analytics-studio/the-cleaning-log/s03-03-refuse-the-silent-step"},{"id":"analytics-studio/the-cleaning-log/s04-04-predict-the-receipts"},{"id":"analytics-studio/the-cleaning-log/s05-05-fill-the-null-decision"},{"id":"analytics-studio/the-cleaning-log/s06-06-fix-the-vanishing-rows"},{"id":"analytics-studio/the-cleaning-log/s07-07-write-the-null-ledger"},{"id":"analytics-studio/the-cleaning-log/s08-08-checkpoint"}]},{"slug":"every-number-has-an-address","steps":[{"id":"analytics-studio/every-number-has-an-address/s01-01-the-plausible-wrong-number"},{"id":"analytics-studio/every-number-has-an-address/s02-02-sample-first-then-full"},{"id":"analytics-studio/every-number-has-an-address/s03-03-which-check-catches-it"},{"id":"analytics-studio/every-number-has-an-address/s04-04-predict-the-fan-out"},{"id":"analytics-studio/every-number-has-an-address/s05-05-fill-the-trace"},{"id":"analytics-studio/every-number-has-an-address/s06-06-write-audit-the-memo"},{"id":"analytics-studio/every-number-has-an-address/s07-07-checkpoint"}]},{"slug":"challenge-then-rerun","steps":[{"id":"analytics-studio/challenge-then-rerun/s01-01-the-confident-recommendation"},{"id":"analytics-studio/challenge-then-rerun/s02-02-the-triad-as-a-checklist"},{"id":"analytics-studio/challenge-then-rerun/s03-03-name-the-leg"},{"id":"analytics-studio/challenge-then-rerun/s04-04-predict-the-rerun"},{"id":"analytics-studio/challenge-then-rerun/s05-05-fix-the-drifting-memo"},{"id":"analytics-studio/challenge-then-rerun/s06-06-write-score-the-challenge"},{"id":"analytics-studio/challenge-then-rerun/s07-07-checkpoint"}]}]},{"slug":"delivery-studio","lessons":[{"slug":"the-spec-is-the-build","steps":[{"id":"delivery-studio/the-spec-is-the-build/s01-01-the-clarifying-question-is-gone"},{"id":"delivery-studio/the-spec-is-the-build/s02-02-the-ticket-as-data"},{"id":"delivery-studio/the-spec-is-the-build/s03-03-spot-the-untestable-check"},{"id":"delivery-studio/the-spec-is-the-build/s04-04-predict-the-spec-lint"},{"id":"delivery-studio/the-spec-is-the-build/s05-05-fill-the-scope-fence"},{"id":"delivery-studio/the-spec-is-the-build/s06-06-inside-or-outside-the-frontier"},{"id":"delivery-studio/the-spec-is-the-build/s07-07-write-lint-spec"},{"id":"delivery-studio/the-spec-is-the-build/s08-08-checkpoint"}]},{"slug":"acceptance-before-the-build","steps":[{"id":"delivery-studio/acceptance-before-the-build/s01-01-the-ninety-seven-thousand-dollar-skip"},{"id":"delivery-studio/acceptance-before-the-build/s02-02-evidence-against-the-checks"},{"id":"delivery-studio/acceptance-before-the-build/s03-03-which-check-catches-it"},{"id":"delivery-studio/acceptance-before-the-build/s04-04-fix-the-vibes-review"},{"id":"delivery-studio/acceptance-before-the-build/s05-05-predict-the-review-run"},{"id":"delivery-studio/acceptance-before-the-build/s06-06-rework-is-a-list-not-a-feeling"},{"id":"delivery-studio/acceptance-before-the-build/s07-07-write-review-deliverable"},{"id":"delivery-studio/acceptance-before-the-build/s08-08-checkpoint"}]},{"slug":"status-from-artifacts","steps":[{"id":"delivery-studio/status-from-artifacts/s01-01-watermelon-status"},{"id":"delivery-studio/status-from-artifacts/s02-02-derive-the-rag"},{"id":"delivery-studio/status-from-artifacts/s03-03-spot-the-artifact"},{"id":"delivery-studio/status-from-artifacts/s04-04-fill-the-worst-of"},{"id":"delivery-studio/status-from-artifacts/s05-05-predict-the-rollup"},{"id":"delivery-studio/status-from-artifacts/s06-06-the-not-ready-call"},{"id":"delivery-studio/status-from-artifacts/s07-07-write-readiness-gate"},{"id":"delivery-studio/status-from-artifacts/s08-08-checkpoint"}]},{"slug":"the-hours-saved-receipt","steps":[{"id":"delivery-studio/the-hours-saved-receipt/s01-01-the-token-chart-is-not-a-receipt"},{"id":"delivery-studio/the-hours-saved-receipt/s02-02-the-receipt-as-data"},{"id":"delivery-studio/the-hours-saved-receipt/s03-03-which-line-survives-staff-meeting"},{"id":"delivery-studio/the-hours-saved-receipt/s04-04-fix-the-vanity-chart"},{"id":"delivery-studio/the-hours-saved-receipt/s05-05-predict-the-receipt-run"},{"id":"delivery-studio/the-hours-saved-receipt/s06-06-only-accepted-ships-count"},{"id":"delivery-studio/the-hours-saved-receipt/s07-07-write-hours-receipt"},{"id":"delivery-studio/the-hours-saved-receipt/s08-08-checkpoint"}]}]},{"slug":"people-studio","lessons":[{"slug":"the-data-firewall","steps":[{"id":"people-studio/the-data-firewall/s01-01-the-rule-that-cannot-live-in-memory"},{"id":"people-studio/the-data-firewall/s02-02-the-firewall-as-data"},{"id":"people-studio/the-data-firewall/s03-03-which-payload-passes"},{"id":"people-studio/the-data-firewall/s04-04-predict-the-scan"},{"id":"people-studio/the-data-firewall/s05-05-fix-the-leaky-gate"},{"id":"people-studio/the-data-firewall/s06-06-employee-relations-takes-nothing"},{"id":"people-studio/the-data-firewall/s07-07-write-prompt-gate"},{"id":"people-studio/the-data-firewall/s08-08-checkpoint"}]},{"slug":"briefs-with-receipts","steps":[{"id":"people-studio/briefs-with-receipts/s01-01-the-most-automated-desk"},{"id":"people-studio/briefs-with-receipts/s02-02-a-claim-with-a-receipt"},{"id":"people-studio/briefs-with-receipts/s03-03-sourced-or-inference"},{"id":"people-studio/briefs-with-receipts/s04-04-predict-the-receipt-audit"},{"id":"people-studio/briefs-with-receipts/s05-05-fill-the-lookup"},{"id":"people-studio/briefs-with-receipts/s06-06-the-screening-line"},{"id":"people-studio/briefs-with-receipts/s07-07-write-audit-brief"},{"id":"people-studio/briefs-with-receipts/s08-08-checkpoint"}]},{"slug":"the-paper-trail","steps":[{"id":"people-studio/the-paper-trail/s01-01-policy-is-legal-surface"},{"id":"people-studio/the-paper-trail/s02-02-the-boundary-as-a-state-machine"},{"id":"people-studio/the-paper-trail/s03-03-who-signs-off"},{"id":"people-studio/the-paper-trail/s04-04-predict-the-version-log"},{"id":"people-studio/the-paper-trail/s05-05-fix-the-shortcut"},{"id":"people-studio/the-paper-trail/s06-06-the-evidence-trail"},{"id":"people-studio/the-paper-trail/s07-07-write-decision-record"},{"id":"people-studio/the-paper-trail/s08-08-checkpoint"}]}]},{"slug":"ops-studio","lessons":[{"slug":"the-sop-is-data","steps":[{"id":"ops-studio/the-sop-is-data/s01-01-the-two-weeks-notice-problem"},{"id":"ops-studio/the-sop-is-data/s02-02-the-sop-as-data"},{"id":"ops-studio/the-sop-is-data/s03-03-spot-the-invented-step"},{"id":"ops-studio/the-sop-is-data/s04-04-fill-the-sop-lint"},{"id":"ops-studio/the-sop-is-data/s05-05-predict-the-diff"},{"id":"ops-studio/the-sop-is-data/s06-06-the-diff-is-the-change-control"},{"id":"ops-studio/the-sop-is-data/s07-07-write-lint-sop"},{"id":"ops-studio/the-sop-is-data/s08-08-checkpoint"}]},{"slug":"auto-run-or-named-approval","steps":[{"id":"ops-studio/auto-run-or-named-approval/s01-01-the-checklist-that-lied"},{"id":"ops-studio/auto-run-or-named-approval/s02-02-the-schedule-is-data"},{"id":"ops-studio/auto-run-or-named-approval/s03-03-which-item-may-auto-run"},{"id":"ops-studio/auto-run-or-named-approval/s04-04-fix-the-silent-auto-complete"},{"id":"ops-studio/auto-run-or-named-approval/s05-05-predict-the-exception-queue"},{"id":"ops-studio/auto-run-or-named-approval/s06-06-exceptions-are-a-queue-not-a-shrug"},{"id":"ops-studio/auto-run-or-named-approval/s07-07-write-run-checklist"},{"id":"ops-studio/auto-run-or-named-approval/s08-08-checkpoint"}]},{"slug":"numbers-with-receipts","steps":[{"id":"ops-studio/numbers-with-receipts/s01-01-the-number-that-moves-money"},{"id":"ops-studio/numbers-with-receipts/s02-02-recompute-dont-trust"},{"id":"ops-studio/numbers-with-receipts/s03-03-which-claim-has-no-receipt"},{"id":"ops-studio/numbers-with-receipts/s04-04-predict-the-verification"},{"id":"ops-studio/numbers-with-receipts/s05-05-fill-the-receipt-check"},{"id":"ops-studio/numbers-with-receipts/s06-06-the-anomaly-is-a-question"},{"id":"ops-studio/numbers-with-receipts/s07-07-write-verify-report"},{"id":"ops-studio/numbers-with-receipts/s08-08-checkpoint"}]},{"slug":"the-pii-proxy","steps":[{"id":"ops-studio/the-pii-proxy/s01-01-the-ticket-that-left-the-building"},{"id":"ops-studio/the-pii-proxy/s02-02-mask-then-unmask"},{"id":"ops-studio/the-pii-proxy/s03-03-which-payload-may-leave"},{"id":"ops-studio/the-pii-proxy/s04-04-fill-the-leftover-check"},{"id":"ops-studio/the-pii-proxy/s05-05-predict-the-two-sides"},{"id":"ops-studio/the-pii-proxy/s06-06-unmask-is-a-named-human-act"},{"id":"ops-studio/the-pii-proxy/s07-07-write-the-proxy"},{"id":"ops-studio/the-pii-proxy/s08-08-checkpoint"}]}]},{"slug":"legal-studio","lessons":[{"slug":"the-cite-check-gate","steps":[{"id":"legal-studio/the-cite-check-gate/s01-01-the-brief-that-reads-perfectly"},{"id":"legal-studio/the-cite-check-gate/s02-02-three-verdicts-as-data"},{"id":"legal-studio/the-cite-check-gate/s03-03-which-cite-needs-no-check"},{"id":"legal-studio/the-cite-check-gate/s04-04-predict-the-verification-run"},{"id":"legal-studio/the-cite-check-gate/s05-05-fix-the-verifier-that-asks-again"},{"id":"legal-studio/the-cite-check-gate/s06-06-write-verify-authorities"},{"id":"legal-studio/the-cite-check-gate/s07-07-checkpoint"}]},{"slug":"clause-extraction-with-pinpoints","steps":[{"id":"legal-studio/clause-extraction-with-pinpoints/s01-01-a-claim-without-a-pinpoint-is-a-rumor"},{"id":"legal-studio/clause-extraction-with-pinpoints/s02-02-the-playbook-as-data"},{"id":"legal-studio/clause-extraction-with-pinpoints/s03-03-which-row-is-unusable"},{"id":"legal-studio/clause-extraction-with-pinpoints/s04-04-predict-the-triage"},{"id":"legal-studio/clause-extraction-with-pinpoints/s05-05-fill-the-walk-away-route"},{"id":"legal-studio/clause-extraction-with-pinpoints/s06-06-write-triage-extraction"},{"id":"legal-studio/clause-extraction-with-pinpoints/s07-07-checkpoint"}]},{"slug":"privilege-rules-and-the-review-log","steps":[{"id":"legal-studio/privilege-rules-and-the-review-log/s01-01-privilege-is-a-routing-question"},{"id":"legal-studio/privilege-rules-and-the-review-log/s02-02-the-routing-table"},{"id":"legal-studio/privilege-rules-and-the-review-log/s03-03-which-request-is-the-waiver-risk"},{"id":"legal-studio/privilege-rules-and-the-review-log/s04-04-predict-the-router"},{"id":"legal-studio/privilege-rules-and-the-review-log/s05-05-fix-the-privilege-hole"},{"id":"legal-studio/privilege-rules-and-the-review-log/s06-06-the-log-that-survives-a-motion"},{"id":"legal-studio/privilege-rules-and-the-review-log/s07-07-write-log-ready"},{"id":"legal-studio/privilege-rules-and-the-review-log/s08-08-checkpoint"}]}]},{"slug":"agent-studio","lessons":[{"slug":"the-tool-contract","steps":[{"id":"agent-studio/the-tool-contract/s01-01-the-feature-you-ship-today"},{"id":"agent-studio/the-tool-contract/s02-02-the-schema-is-the-blast-radius"},{"id":"agent-studio/the-tool-contract/s03-03-spot-the-loose-tool"},{"id":"agent-studio/the-tool-contract/s04-04-predict-the-validation"},{"id":"agent-studio/the-tool-contract/s05-05-fix-the-yolo-rerun"},{"id":"agent-studio/the-tool-contract/s06-06-write-validate-call"},{"id":"agent-studio/the-tool-contract/s07-07-checkpoint"}]},{"slug":"the-loop-with-a-meter","steps":[{"id":"agent-studio/the-loop-with-a-meter/s01-01-a-loop-that-cannot-stop-is-an-invoice"},{"id":"agent-studio/the-loop-with-a-meter/s02-02-caps-are-part-of-the-loop"},{"id":"agent-studio/the-loop-with-a-meter/s03-03-why-did-it-stop"},{"id":"agent-studio/the-loop-with-a-meter/s04-04-predict-the-stop-reason"},{"id":"agent-studio/the-loop-with-a-meter/s05-05-fill-the-budget-check"},{"id":"agent-studio/the-loop-with-a-meter/s06-06-the-trace-is-the-receipt"},{"id":"agent-studio/the-loop-with-a-meter/s07-07-write-run-loop"},{"id":"agent-studio/the-loop-with-a-meter/s08-08-checkpoint"}]},{"slug":"evals-before-it-works","steps":[{"id":"agent-studio/evals-before-it-works/s01-01-green-before-it-runs"},{"id":"agent-studio/evals-before-it-works/s02-02-a-golden-case-is-a-past-incident"},{"id":"agent-studio/evals-before-it-works/s03-03-which-case-catches-it"},{"id":"agent-studio/evals-before-it-works/s04-04-predict-the-eval-run"},{"id":"agent-studio/evals-before-it-works/s05-05-fix-the-router-to-green"},{"id":"agent-studio/evals-before-it-works/s06-06-the-ratchet-entry"},{"id":"agent-studio/evals-before-it-works/s07-07-write-lint-the-ratchet"},{"id":"agent-studio/evals-before-it-works/s08-08-checkpoint"}]}]}]},"detail":{"number":49,"slug":"campaign-studio","title":"campaign studio — one campaign, end to end, with the gate on","blurb":"brief to voice-locked copy variants to batch plan to calendar to the numbers pass, then synthetic creator detection for hyperscale fake-organic. the whole campaign as data your scripts can check — and an approval gate nothing skips. built for the person who owns the send button.","overview":"$2c","status":"live","lessons":[{"slug":"voice-pack-as-data","title":"The voice pack is data — on-voice copy at batch volume","estMinutes":21,"prerequisites":[],"status":"live","steps":[{"type":"read","id":"campaign-studio/voice-pack-as-data/s01-01-the-campaign-and-the-gate","xp":1,"hint":[],"personalize":false,"phase":"warmup","estSeconds":200,"concept":"campaign-studio-setup","body":"$2d","cta":"Got it","runnable":true},{"type":"read","id":"campaign-studio/voice-pack-as-data/s02-02-lint-the-draft","xp":1,"hint":[],"personalize":false,"phase":"warmup","estSeconds":170,"concept":"voice-linting","body":"$2e","cta":"Got it","code":"PACK = {\n \"banned\": [\"best-in-class\", \"revolutionary\", \"game-changing\", \"#1\"],\n \"max_words\": 20,\n}\n\ndraft = \"Our revolutionary subscription is the best-in-class way to buy coffee.\"\n\nproblems = []\ntext = draft.lower()\nfor phrase in PACK[\"banned\"]:\n if phrase in text:\n problems.append(f\"banned: {phrase}\")\nif len(draft.split()) > PACK[\"max_words\"]:\n problems.append(\"too long\")\n\nprint(f\"{len(problems)} violation(s)\")\nfor p in problems:\n print(f\"- {p}\")\n","runnable":true},{"type":"predict","id":"campaign-studio/voice-pack-as-data/s03-03-predict-the-violations","xp":3,"hint":[{"level":1,"body":"Check each of the four banned phrases against the lowercased draft. `best-in-class` is the only one that doesn't appear. The list comprehension keeps BANNED's order, so `revolutionary` comes first even though `#1` might feel more prominent in the sentence.","cost":0},{"level":2,"body":"Three hits, in BANNED order: first line `violations: 3`, then `- revolutionary`, `- game-changing`, `- #1`.","cost":0}],"personalize":false,"phase":"build","estSeconds":70,"concept":"banned-phrase-scan","code":"BANNED = [\"best-in-class\", \"revolutionary\", \"game-changing\", \"#1\"]\n\ndraft = \"Our revolutionary roaster is the #1 choice for game-changing mornings.\"\n\nhits = [b for b in BANNED if b in draft.lower()]\nprint(f\"violations: {len(hits)}\")\nfor b in hits:\n print(f\"- {b}\")\n","prompt":"Fieldnote's fall email is in draft. The subject line the model wrote\nis exactly as bad as you fear — \"revolutionary,\" \"game-changing,\"\na \"#1\" legal would never clear. The scan walks the banned list against\nthe lowercased draft, in list order. What prints?\n\n(Watch the order: the output follows the BANNED list, not the order\nthe phrases appear in the draft.)\n","grader":{"kind":"stdout-equality","expected":"violations: 3\n- revolutionary\n- game-changing\n- #1\n","normalize":"collapse-trailing-newline"}},{"type":"mc","id":"campaign-studio/voice-pack-as-data/s04-04-testable-or-mood","xp":2,"hint":[{"level":1,"body":"The test for a testable rule: could you write an `if` statement that fails a draft against it? Exactly one candidate survives that question — it involves counting.","cost":0}],"personalize":false,"phase":"build","estSeconds":60,"concept":"testable-vs-mood-rules","prompt":"You're migrating Fieldnote's brand PDF into the voice pack. Only rules\na script can check go in the `rules` list — the rest either become\nbanned phrases or stay as human-judgment notes. Which candidate\nbelongs in `rules`?\n","options":[{"id":"under_20","label":"2 — sentences under 20 words"},{"id":"warm_prof","label":"1 — warm but professional","explain":"Warmth isn't measurable by a script. This is a mood word — it can live in the prompt to steer the draft, but it can't gate anything, because no check can fail it."},{"id":"punchy","label":"3 — punchy, thumb-stopping copy","explain":"'Punchy' has no test. Ask three marketers whether a line is punchy and you'll get four answers. Mood words go in the prompt, not the rules list."},{"id":"friend","label":"4 — sounds like a knowledgeable friend","explain":"A persona note, and a useful one — for the `reader` field or the prompt. But there's no substring match or word count that verifies 'knowledgeable friend.' Human judgment territory."},{"id":"bold","label":"5 — authentically bold","explain":"Two mood words stapled together. 'Authentic' may be the least testable word in marketing — no substring match, count, or regex measures it. Prompt material at best; it can't gate anything."}],"answerIds":["under_20"],"shuffle":false,"code":"# five lines pulled from Fieldnote's old brand PDF.\ncandidates = [\n \"warm but professional\",\n \"sentences under 20 words\",\n \"punchy, thumb-stopping copy\",\n \"sounds like a knowledgeable friend\",\n \"authentically bold\",\n]\nfor i, c in enumerate(candidates, 1):\n print(f\"{i}. {c}\")\n","runnable":true},{"type":"fill","id":"campaign-studio/voice-pack-as-data/s05-05-fill-the-linter","xp":3,"hint":[{"level":1,"body":"Python's `in` on two strings is a substring check. You want: is this banned phrase anywhere inside the lowercased draft?","cost":0},{"level":2,"body":"`phrase in text` — reads left to right as 'phrase appears in text.' Note the order: `text in phrase` would ask whether the whole draft fits inside the banned phrase, which is backwards.","cost":0}],"personalize":false,"phase":"build","estSeconds":80,"concept":"substring-banned-check","prompt":"The linter is one blank away from working. `text` is the lowercased\ndraft; `phrase` is the current banned phrase from the pack. Fill in\nthe condition that catches a banned phrase anywhere in the draft.\n\nExpected output:\n```\n['banned: revolutionary', 'banned: synergy']\n[]\n```\n","code":"PACK = {\n \"banned\": [\"best-in-class\", \"revolutionary\", \"synergy\"],\n \"max_words\": 20,\n}\n\ndef lint(line):\n problems = []\n text = line.lower()\n for phrase in PACK[\"banned\"]:\n if ___:\n problems.append(f\"banned: {phrase}\")\n if len(line.split()) > PACK[\"max_words\"]:\n problems.append(\"too long\")\n return problems\n\nprint(lint(\"A revolutionary blend with true synergy\"))\nprint(lint(\"Fresh beans, every Tuesday\"))\n","blanks":[{"id":"banned_check","accept":["phrase in text"],"caseSensitive":false,"normalize":"trim"}]},{"type":"read","id":"campaign-studio/voice-pack-as-data/s06-06-variants-as-records","xp":1,"hint":[],"personalize":false,"phase":"build","estSeconds":180,"concept":"copy-variants-as-records","body":"$2f","cta":"Got it","code":"# one drafted variant. not a paragraph in a doc — a record.\nvariant = {\n \"id\": \"E3\",\n \"channel\": \"email\",\n \"slot\": \"subject-line\",\n \"text\": \"Your Tuesday beans are on the way\",\n \"cta\": \"none\",\n \"source\": \"ai-draft\",\n \"lint\": [], # filled by the linter\n \"approved_by\": \"\", # filled by a human, never by a script\n}\n\nfor field in (\"id\", \"channel\", \"slot\", \"text\"):\n print(f\"{field:<9} {variant[field]}\")\nprint(f\"lint {'clean' if not variant['lint'] else variant['lint']}\")\n","runnable":true},{"type":"write","id":"campaign-studio/voice-pack-as-data/s07-07-write-lint-copy","xp":5,"hint":[{"level":1,"body":"Same shape as the fill step: lowercase once, loop `pack['banned']` with a substring check, then the word-count check LAST. No draft here trips both — but the caller joins violations with `; `, and when a draft does trip both (the checkpoint batch has one), the banned phrases must come before `too long`. Build the list in that order now.","cost":0},{"level":2,"body":"```python\ndef lint_copy(text, pack):\n problems = []\n lowered = text.lower()\n for phrase in pack[\"banned\"]:\n if phrase in lowered:\n problems.append(f\"banned: {phrase}\")\n if len(text.split()) > pack[\"max_words\"]:\n problems.append(\"too long\")\n return problems\n```\nV3 is 15 words against a max of 12 — that's the `too long`. V2 trips `game-changing`.\n","cost":0}],"personalize":false,"phase":"build","estSeconds":240,"concept":"write-lint-copy","prompt":"Write `lint_copy(text, pack)` — the voice check that runs on every\nAI draft before it reaches review.\n\nThese drafts are subject lines, and subject lines carry a tighter\ncap than the pack's 20-word body-sentence rule — Dana set\n`max_words` to 12 for this slot. The linter doesn't care: it reads\nwhatever cap the pack states. That's the point of pack-as-data.\n\nRules, in order:\n\n1. For each phrase in `pack[\"banned\"]` (in list order): if it appears\n in the lowercased `text`, add the violation string\n `\"banned: \"`.\n2. If the word count (`len(text.split())`) is greater than\n `pack[\"max_words\"]`, add `\"too long\"`.\n3. Return the list of violations (empty list = on-voice).\n\nFour AI drafts for the Fieldnote relaunch run through it. Expected\noutput:\n```\nV1: PASS\nV2: FAIL (banned: game-changing)\nV3: FAIL (too long)\nV4: PASS\n```\n","starter":"PACK = {\n \"banned\": [\"game-changing\", \"best-in-class\", \"revolutionary\"],\n \"max_words\": 12, # subject-line cap — tighter than the 20-word body rule\n}\n\ndrafts = [\n (\"V1\", \"Fresh beans at your door every Tuesday\"),\n (\"V2\", \"The game-changing subscription your mornings deserve\"),\n (\"V3\", \"We roast small batches weekly and ship them straight to your kitchen door for you\"),\n (\"V4\", \"Skip a week anytime, no questions\"),\n]\n\n# define lint_copy(text, pack) below\n\nfor vid, text in drafts:\n problems = lint_copy(text, PACK)\n if problems:\n print(f\"{vid}: FAIL ({'; '.join(problems)})\")\n else:\n print(f\"{vid}: PASS\")\n","grader":{"kind":"stdout-equality","expected":"V1: PASS\nV2: FAIL (banned: game-changing)\nV3: FAIL (too long)\nV4: PASS\n","normalize":"collapse-trailing-newline"},"solution":"PACK = {\n \"banned\": [\"game-changing\", \"best-in-class\", \"revolutionary\"],\n \"max_words\": 12, # subject-line cap — tighter than the 20-word body rule\n}\n\ndrafts = [\n (\"V1\", \"Fresh beans at your door every Tuesday\"),\n (\"V2\", \"The game-changing subscription your mornings deserve\"),\n (\"V3\", \"We roast small batches weekly and ship them straight to your kitchen door for you\"),\n (\"V4\", \"Skip a week anytime, no questions\"),\n]\n\ndef lint_copy(text, pack):\n problems = []\n lowered = text.lower()\n for phrase in pack[\"banned\"]:\n if phrase in lowered:\n problems.append(f\"banned: {phrase}\")\n if len(text.split()) > pack[\"max_words\"]:\n problems.append(\"too long\")\n return problems\n\nfor vid, text in drafts:\n problems = lint_copy(text, PACK)\n if problems:\n print(f\"{vid}: FAIL ({'; '.join(problems)})\")\n else:\n print(f\"{vid}: PASS\")\n","hiddenTests":[]},{"type":"checkpoint","id":"campaign-studio/voice-pack-as-data/s08-08-checkpoint","xp":8,"hint":[],"personalize":false,"phase":"check","estSeconds":280,"concept":"on-voice-batch-pass","prompt":"Checkpoint: the full voice pass. The AI drafted a five-variant batch\nfor the Fieldnote relaunch. Lint every variant, print the per-variant\nverdicts, and build the on-voice queue that goes to Dana.\n\nWrite BOTH functions:\n\n`lint_copy(text, pack)` — as before:\nbanned phrases from `pack[\"banned\"]` (in list order, case-insensitive,\nviolation string `\"banned: \"`), then `\"too long\"` if word\ncount exceeds `pack[\"max_words\"]`. Returns the violation list.\n\n`on_voice_variants(variants, pack)` — returns the list of variant\ndicts whose `lint_copy` result is empty, preserving order.\n\nThe harness at the bottom prints one line per variant and the final\nqueue count. Expected output:\n```\nE1 email PASS\nE2 email FAIL banned: revolutionary\nS1 social PASS\nS2 social FAIL banned: best-in-class; banned: #1; too long\nA1 ads PASS\nkept 3/5 — batch goes to Dana for approval\n```\n","starter":"$30","grader":{"kind":"stdout-equality","expected":"E1 email PASS\nE2 email FAIL banned: revolutionary\nS1 social PASS\nS2 social FAIL banned: best-in-class; banned: #1; too long\nA1 ads PASS\nkept 3/5 — batch goes to Dana for approval\n","normalize":"collapse-trailing-newline"},"solution":"$31","passThreshold":0.66}],"xpTotal":24},{"slug":"batch-plan-and-calendar","title":"Batch plan and calendar — creative at volume, gated before it ships","estMinutes":19,"prerequisites":["voice-pack-as-data"],"status":"live","steps":[{"type":"read","id":"campaign-studio/batch-plan-and-calendar/s01-01-slots-before-prompts","xp":1,"hint":[],"personalize":false,"phase":"warmup","estSeconds":190,"concept":"creative-batch-planning","body":"$32","cta":"Got it","runnable":true},{"type":"mc","id":"campaign-studio/batch-plan-and-calendar/s02-02-which-field-is-missing","xp":2,"hint":[{"level":1,"body":"Story frames in the wild usually carry a headline, so an unbriefed model helpfully invents one — in letters from no alphabet. Which field in lesson 1's batch plan made that decision explicit, even when the answer was 'none'?","cost":0}],"personalize":false,"phase":"build","estSeconds":70,"concept":"generation-brief-fields","prompt":"The story batch comes back and half the variants have garbled\npseudo-words baked into the image — melted letterforms where a\nheadline would go. The model was left to guess about something the\nbrief should have pinned down. Which missing field caused the rework?\n","options":[{"id":"text_on_asset","label":"text_on_asset — the exact words to render, or the explicit value \"none\""},{"id":"subject","label":"subject — the model didn't know what to draw","explain":"The subject is right there in the brief — box, counter, morning light — and the variants show it. The failure is specifically the invented text, and no field in this brief says whether text belongs on the asset at all."},{"id":"size","label":"size — without dimensions the model picked a random crop","explain":"1080x1920 is in the brief, and the variants came back vertical. Garbled letterforms aren't a crop problem — they're what image models produce when they decide, unbriefed, that a story frame usually has a headline."},{"id":"brand_constraints","label":"brand_constraints — the palette rules were too loose","explain":"The constraints line is present and reasonably tight. Palette drift would show as off-brand colors, not melted fake words. The text decision was never made, so the model made it."}],"answerIds":["text_on_asset"],"shuffle":false,"code":"# the brief that went to the image model for the story slot.\nbrief = {\n \"slot\": \"story\",\n \"size\": \"1080x1920\",\n \"subject\": \"the fall subscription box on a kitchen counter, morning light\",\n \"composition\": \"vertical, product in lower half, negative space top third\",\n \"brand_constraints\": \"warm palette, no faces, no competitor mugs\",\n}\nfor k, v in brief.items():\n print(f\"{k}: {v}\")\n","runnable":true},{"type":"write","id":"campaign-studio/batch-plan-and-calendar/s03-03-write-batch-plan","xp":4,"hint":[{"level":1,"body":"Loop the slots, accumulate two running totals, print the given f-string per slot, and `return total_assets, total_cost` at the end. The harness prints the total line for you — don't print it inside the function or it'll appear twice.","cost":0},{"level":2,"body":"```python\ndef batch_plan(slots, cost_per_image):\n total_assets = 0\n total_cost = 0.0\n for s in slots:\n line_cost = s[\"variants\"] * cost_per_image\n print(f\"{s['slot']:<13} x{s['variants']:<3} ${line_cost:.2f}\")\n total_assets += s[\"variants\"]\n total_cost += line_cost\n return total_assets, total_cost\n```\n","cost":0}],"personalize":false,"phase":"build","estSeconds":220,"concept":"batch-plan-cost","prompt":"Write `batch_plan(slots, cost_per_image)` — the function that turns\nthe creative plan into two totals. Fair warning: the dollar figure\ncomes out comically small. Generation is cheap; nobody defends $1.28\nin a budget meeting. The number that scales is the asset count —\n32 variants is 32 things a human has to review before anything\nreaches the calendar gate, and that review time is the real cost\nyou're planning here.\n\nFor each slot dict (in order), print one line:\n```\n x $\n```\ni.e. `f\"{s['slot']:<13} x{s['variants']:<3} ${s['variants'] * cost_per_image:.2f}\"`\n\nThen return a tuple `(total_assets, total_cost)` — the sum of all\nvariant counts and the sum of all line costs.\n\nExpected output:\n```\nemail-header x6 $0.24\nstory x8 $0.32\nfeed-square x8 $0.32\nad-banner x10 $0.40\ntotal: 32 assets, $1.28\n```\n","starter":"SLOTS = [\n {\"slot\": \"email-header\", \"variants\": 6},\n {\"slot\": \"story\", \"variants\": 8},\n {\"slot\": \"feed-square\", \"variants\": 8},\n {\"slot\": \"ad-banner\", \"variants\": 10},\n]\nCOST_PER_IMAGE = 0.04 # your image tool's current per-image rate\n\n# define batch_plan(slots, cost_per_image) below\n\ntotal_assets, total_cost = batch_plan(SLOTS, COST_PER_IMAGE)\nprint(f\"total: {total_assets} assets, ${total_cost:.2f}\")\n","grader":{"kind":"stdout-equality","expected":"email-header x6 $0.24\nstory x8 $0.32\nfeed-square x8 $0.32\nad-banner x10 $0.40\ntotal: 32 assets, $1.28\n","normalize":"collapse-trailing-newline"},"solution":"SLOTS = [\n {\"slot\": \"email-header\", \"variants\": 6},\n {\"slot\": \"story\", \"variants\": 8},\n {\"slot\": \"feed-square\", \"variants\": 8},\n {\"slot\": \"ad-banner\", \"variants\": 10},\n]\nCOST_PER_IMAGE = 0.04 # your image tool's current per-image rate\n\ndef batch_plan(slots, cost_per_image):\n total_assets = 0\n total_cost = 0.0\n for s in slots:\n line_cost = s[\"variants\"] * cost_per_image\n print(f\"{s['slot']:<13} x{s['variants']:<3} ${line_cost:.2f}\")\n total_assets += s[\"variants\"]\n total_cost += line_cost\n return total_assets, total_cost\n\ntotal_assets, total_cost = batch_plan(SLOTS, COST_PER_IMAGE)\nprint(f\"total: {total_assets} assets, ${total_cost:.2f}\")\n","hiddenTests":[]},{"type":"read","id":"campaign-studio/batch-plan-and-calendar/s04-04-the-calendar-is-data","xp":1,"hint":[],"personalize":false,"phase":"build","estSeconds":190,"concept":"calendar-approval-column","body":"$33","cta":"Got it","code":"# two-week relaunch calendar, first rows. timezone: America/Chicago.\nrows = [\n {\"date\": \"09-02\", \"channel\": \"email\", \"piece\": \"launch-email\",\n \"owner\": \"you\", \"approved_by\": \"dana\", \"status\": \"approved\"},\n {\"date\": \"09-02\", \"channel\": \"social\", \"piece\": \"teaser-story\",\n \"owner\": \"you\", \"approved_by\": \"\", \"status\": \"approved\"},\n {\"date\": \"09-03\", \"channel\": \"social\", \"piece\": \"meme-post\",\n \"owner\": \"you\", \"approved_by\": \"dana\", \"status\": \"rejected\"},\n]\n\nfor r in rows:\n gate = \"OK\" if r[\"status\"] == \"approved\" and r[\"approved_by\"] else \"HOLD\"\n print(f\"{r['date']} {r['channel']:<6} {r['piece']:<13} {gate}\")\n","runnable":true},{"type":"predict","id":"campaign-studio/batch-plan-and-calendar/s05-05-predict-the-queue","xp":3,"hint":[{"level":1,"body":"Walk the four rows against BOTH conditions. launch-email: approved + dana, passes. teaser-story: approved but `approved_by` is `\"\"` — empty string is falsy, fails. meme-post: has a name but status is rejected, fails. ad-set-a: approved + sam, passes.","cost":0},{"level":2,"body":"Two rows survive: `scheduled: 2`, then `09-02 launch-email` and `09-04 ad-set-a`. The teaser-story is the trap — status flipped to approved, but no human put a name in the row, and the empty string fails the gate.","cost":0}],"personalize":false,"phase":"build","estSeconds":80,"concept":"approval-gate-filter","code":"rows = [\n {\"date\": \"09-02\", \"piece\": \"launch-email\", \"approved_by\": \"dana\", \"status\": \"approved\"},\n {\"date\": \"09-02\", \"piece\": \"teaser-story\", \"approved_by\": \"\", \"status\": \"approved\"},\n {\"date\": \"09-03\", \"piece\": \"meme-post\", \"approved_by\": \"dana\", \"status\": \"rejected\"},\n {\"date\": \"09-04\", \"piece\": \"ad-set-a\", \"approved_by\": \"sam\", \"status\": \"approved\"},\n]\n\nqueue = [r for r in rows if r[\"status\"] == \"approved\" and r[\"approved_by\"]]\n\nprint(f\"scheduled: {len(queue)}\")\nfor r in queue:\n print(f\"{r['date']} {r['piece']}\")\n","prompt":"The gate runs on four calendar rows. Remember: an empty string is\nfalsy in Python, so `r[\"approved_by\"]` alone fails the `and` for a\nrow nobody put their name on. What prints?\n","grader":{"kind":"stdout-equality","expected":"scheduled: 2\n09-02 launch-email\n09-04 ad-set-a\n","normalize":"collapse-trailing-newline"}},{"type":"fix","id":"campaign-studio/batch-plan-and-calendar/s06-06-fix-the-gate","xp":3,"hint":[{"level":1,"body":"The `if` checks one condition; the gate needs two. Add the approver check with `and` — an empty string is falsy, so `r[\"approved_by\"]` by itself is the test for 'a human put a name here.'","cost":0},{"level":2,"body":"Change line 12 to: `if r[\"status\"] == \"approved\" and r[\"approved_by\"]:` — the teaser-story row then fails the second condition and the queue drops from 3 rows to 2.","cost":0}],"personalize":false,"phase":"build","estSeconds":110,"concept":"fix-approval-gate","brokenCode":"rows = [\n {\"date\": \"09-02\", \"channel\": \"email\", \"piece\": \"launch-email\", \"approved_by\": \"dana\", \"status\": \"approved\"},\n {\"date\": \"09-02\", \"channel\": \"social\", \"piece\": \"teaser-story\", \"approved_by\": \"\", \"status\": \"approved\"},\n {\"date\": \"09-03\", \"channel\": \"social\", \"piece\": \"meme-post\", \"approved_by\": \"dana\", \"status\": \"rejected\"},\n {\"date\": \"09-05\", \"channel\": \"email\", \"piece\": \"winback\", \"approved_by\": \"sam\", \"status\": \"approved\"},\n]\n\ndef publish_queue(rows):\n queue = []\n for r in rows:\n # bug: status alone is not approval — no-name rows slip through\n if r[\"status\"] == \"approved\":\n queue.append(r)\n return queue\n\nq = publish_queue(rows)\nprint(f\"queue: {len(q)} rows\")\nfor r in q:\n print(f\"{r['date']} {r['piece']} -> approved by {r['approved_by']}\")\n","prompt":"This gate is leaking. The teaser-story row has `status: approved` but\nan empty `approved_by` — someone flipped the status without putting a\nname on it — and the current gate schedules it anyway. In September\nthat's an unreviewed AI draft going out under the brand's name.\n\nFix `publish_queue` so a row needs BOTH `status == \"approved\"` AND a\nnon-empty `approved_by` to reach the queue.\n\nExpected output:\n```\nqueue: 2 rows\n09-02 launch-email -> approved by dana\n09-05 winback -> approved by sam\n```\n","grader":{"kind":"stdout-equality","expected":"queue: 2 rows\n09-02 launch-email -> approved by dana\n09-05 winback -> approved by sam\n","normalize":"collapse-trailing-newline"},"bugLines":[11,12],"revealAfter":6},{"type":"checkpoint","id":"campaign-studio/batch-plan-and-calendar/s07-07-checkpoint","xp":8,"hint":[],"personalize":false,"phase":"check","estSeconds":280,"concept":"full-calendar-gate","prompt":"Checkpoint: the full calendar gate, the one that runs before anything\ntouches the scheduling tool.\n\nWrite `gate(rows)` returning a dict with three lists, each preserving\nrow order:\n\n- `\"schedule\"` — rows with `status == \"approved\"` AND a non-empty\n `approved_by`. These may enter the scheduler.\n- `\"blocked\"` — rows with `status == \"approved\"` but NO approver.\n These go back for a named sign-off, not into the scheduler.\n- `\"rejected\"` — rows with `status == \"rejected\"`. These stay in the\n file as the record of what the team said no to.\n\nThe harness prints each list and a summary. The rows are the full\nrelaunch calendar so far — including the teaser-story that's been\nsitting nameless since the gate first caught it. Expected output:\n```\nSCHEDULE 09-02 email launch-email (dana)\nSCHEDULE 09-04 ads ad-set-a (sam)\nSCHEDULE 09-05 email winback (sam)\nBLOCKED 09-02 social teaser-story (no approver)\nKEPT 09-03 social meme-post (rejected, stays in the file)\n3 scheduled, 1 blocked, 1 rejected-and-kept\n```\n","starter":"$34","grader":{"kind":"stdout-equality","expected":"SCHEDULE 09-02 email launch-email (dana)\nSCHEDULE 09-04 ads ad-set-a (sam)\nSCHEDULE 09-05 email winback (sam)\nBLOCKED 09-02 social teaser-story (no approver)\nKEPT 09-03 social meme-post (rejected, stays in the file)\n3 scheduled, 1 blocked, 1 rejected-and-kept\n","normalize":"collapse-trailing-newline"},"solution":"$35","passThreshold":0.66}],"xpTotal":22},{"slug":"the-numbers-pass","title":"The numbers pass — every claimed metric traced to the export","estMinutes":19,"prerequisites":["voice-pack-as-data","batch-plan-and-calendar"],"status":"live","steps":[{"type":"read","id":"campaign-studio/the-numbers-pass/s01-01-a-report-is-a-draft-over-data","xp":1,"hint":[],"personalize":false,"phase":"warmup","estSeconds":190,"concept":"report-over-export","body":"$36","cta":"Got it","runnable":true},{"type":"predict","id":"campaign-studio/the-numbers-pass/s02-02-predict-the-verdict","xp":3,"hint":[{"level":1,"body":"618 / 18200 * 100 = 3.3956..., which formats to `3.4%` at one decimal. Compare that string to the claimed `3.6%`.","cost":0},{"level":2,"body":"Three lines: `claimed CTR: 3.6%`, `export CTR: 3.4%` (note the two spaces after the colon — the strings are aligned), and since 3.4 != 3.6, `verdict: invented`. The model rounded up because 3.6 made a nicer sentence. The export disagrees.","cost":0}],"personalize":false,"phase":"build","estSeconds":70,"concept":"trace-one-claim","code":"export = {\"sent\": 18200, \"opens\": 4914, \"clicks\": 618}\n\nclaimed = \"3.6%\"\nactual = export[\"clicks\"] / export[\"sent\"] * 100\n\nprint(f\"claimed CTR: {claimed}\")\nprint(f\"export CTR: {actual:.1f}%\")\nprint(\"verdict:\", \"traced\" if f\"{actual:.1f}%\" == claimed else \"invented\")\n","prompt":"The AI-drafted summary claims a 3.6% CTR for the launch email. The\nscript recomputes CTR from the export (clicks over sent — this\nplatform's convention; many tools compute CTR over delivered, which\nis exactly why the check states its denominator) at one decimal\nplace and compares. What prints?\n\n(618 / 18200 = 0.03395..., then x100.)\n","grader":{"kind":"stdout-equality","expected":"claimed CTR: 3.6%\nexport CTR: 3.4%\nverdict: invented\n","normalize":"collapse-trailing-newline"}},{"type":"write","id":"campaign-studio/the-numbers-pass/s03-03-write-verify-numbers","xp":5,"hint":[{"level":1,"body":"Loop the claims, look up `export[c['metric']]`, compare to `c['value']`, print the matching f-string from the prompt, count the matches, return the count. The clicks claim (655 vs the export's 618) is the invented one — the model inflated it.","cost":0},{"level":2,"body":"```python\ndef verify_numbers(claims, export):\n traced = 0\n for c in claims:\n actual = export[c[\"metric\"]]\n if c[\"value\"] == actual:\n print(f\"{c['label']:<13} {c['value']:>6} TRACED\")\n traced += 1\n else:\n print(f\"{c['label']:<13} {c['value']:>6} INVENTED (export: {actual})\")\n return traced\n```\n","cost":0}],"personalize":false,"phase":"build","estSeconds":240,"concept":"write-verify-numbers","prompt":"Write `verify_numbers(claims, export)` — the pass that runs on every\nAI-drafted report before it leaves the team.\n\nEach claim is a dict: `{\"label\", \"metric\", \"value\"}`. For each claim,\nin order, print one line:\n\n- if `claim[\"value\"] == export[claim[\"metric\"]]`:\n `f\"{c['label']:<13} {c['value']:>6} TRACED\"`\n- otherwise:\n `f\"{c['label']:<13} {c['value']:>6} INVENTED (export: {export[c['metric']]})\"`\n\nReturn the count of traced claims. The harness prints the summary\nline. Expected output:\n```\nemails sent 18200 TRACED\nopens 4914 TRACED\nclicks 655 INVENTED (export: 618)\nunsubscribes 43 TRACED\n3/4 traced — report is NOT approval-ready\n```\n","starter":"export = {\"sent\": 18200, \"delivered\": 17654, \"opens\": 4914, \"clicks\": 618, \"unsubs\": 43}\n\nclaims = [\n {\"label\": \"emails sent\", \"metric\": \"sent\", \"value\": 18200},\n {\"label\": \"opens\", \"metric\": \"opens\", \"value\": 4914},\n {\"label\": \"clicks\", \"metric\": \"clicks\", \"value\": 655},\n {\"label\": \"unsubscribes\", \"metric\": \"unsubs\", \"value\": 43},\n]\n\n# define verify_numbers(claims, export) below\n\ntraced = verify_numbers(claims, export)\nready = \"approval-ready\" if traced == len(claims) else \"NOT approval-ready\"\nprint(f\"{traced}/{len(claims)} traced — report is {ready}\")\n","grader":{"kind":"stdout-equality","expected":"emails sent 18200 TRACED\nopens 4914 TRACED\nclicks 655 INVENTED (export: 618)\nunsubscribes 43 TRACED\n3/4 traced — report is NOT approval-ready\n","normalize":"collapse-trailing-newline"},"solution":"export = {\"sent\": 18200, \"delivered\": 17654, \"opens\": 4914, \"clicks\": 618, \"unsubs\": 43}\n\nclaims = [\n {\"label\": \"emails sent\", \"metric\": \"sent\", \"value\": 18200},\n {\"label\": \"opens\", \"metric\": \"opens\", \"value\": 4914},\n {\"label\": \"clicks\", \"metric\": \"clicks\", \"value\": 655},\n {\"label\": \"unsubscribes\", \"metric\": \"unsubs\", \"value\": 43},\n]\n\ndef verify_numbers(claims, export):\n traced = 0\n for c in claims:\n actual = export[c[\"metric\"]]\n if c[\"value\"] == actual:\n print(f\"{c['label']:<13} {c['value']:>6} TRACED\")\n traced += 1\n else:\n print(f\"{c['label']:<13} {c['value']:>6} INVENTED (export: {actual})\")\n return traced\n\ntraced = verify_numbers(claims, export)\nready = \"approval-ready\" if traced == len(claims) else \"NOT approval-ready\"\nprint(f\"{traced}/{len(claims)} traced — report is {ready}\")\n","hiddenTests":[]},{"type":"read","id":"campaign-studio/the-numbers-pass/s04-04-denominators-and-the-ftc","xp":1,"hint":[],"personalize":false,"phase":"build","estSeconds":240,"concept":"denominators-and-banned-outright","body":"$37","cta":"Got it","code":"# two real 2026 statistics about AI in marketing. both true. not comparable.\nstats = [\n {\"figure\": \"75%\", \"of_what\": \"marketers who have adopted AI at all\",\n \"source\": \"Salesforce State of Marketing 2026 (vendor survey)\"},\n {\"figure\": \"24.2%\", \"of_what\": \"marketing activities AI is used in\",\n \"source\": \"The CMO Survey, Spring 2026 wave\"},\n]\nfor s in stats:\n print(f\"{s['figure']:>6} of {s['of_what']}\")\n print(f\" ({s['source']})\")\n","runnable":true},{"type":"mc","id":"campaign-studio/the-numbers-pass/s05-05-what-may-not-ship","xp":2,"hint":[{"level":1,"body":"Three of these are claims a human can check and sign. One is a testimonial from a person who does not exist — and 16 CFR Part 465 has a specific phrase, and a specific per-violation penalty, for exactly that.","cost":0}],"personalize":false,"phase":"build","estSeconds":70,"concept":"banned-outright-vs-reviewable","prompt":"Four AI drafts are queued for review. Three can move through the\nstudio's gates — lint, then a named approver. One may not ship at any\napproval level, with sign-off from anyone, ever. Which?\n","options":[{"id":"fake_review","label":"C — the five-star review from 'Sarah K.'"},{"id":"subject","label":"A — the email subject line","explain":"Squarely in AI-may-draft territory: lint it against the voice pack, put it in the calendar, get an approver on the row. That's what the whole pipeline is for."},{"id":"ad_copy","label":"B — 'Roasted weekly in small batches'","explain":"A factual claim, so it needs a fact-check — is the roasting actually weekly? — and an approver. But it's a checkable claim about your own product, which makes it reviewable, not banned."},{"id":"pricing","label":"D — 'The most affordable subscription in the US'","explain":"Close — an unsubstantiated superlative is deceptive if false, and this one probably dies in review. But it dies BY review: it needs substantiation and a named approver, and with real price data behind it, a version of it could ship. A category apart from the fabricated reviewer."}],"answerIds":["fake_review"],"shuffle":false,"code":"# four pieces the AI drafted for relaunch week.\ndrafted = [\n \"A: email subject — 'Your Tuesday beans, now with a fall tier'\",\n \"B: ad copy — 'Roasted weekly in small batches'\",\n \"C: five-star review from 'Sarah K., Austin' — 'Fieldnote changed my mornings!'\",\n \"D: pricing claim — 'The most affordable subscription in the US'\",\n]\nfor line in drafted:\n print(line)\n","runnable":true},{"type":"fill","id":"campaign-studio/the-numbers-pass/s06-06-fill-the-policy-router","xp":3,"hint":[{"level":1,"body":"You're asking: does this piece type appear in the current tier's list? `in` on a list is a membership check — same operator as the banned-phrase linter in the voice-pack lesson, different container.","cost":0},{"level":2,"body":"`piece in kinds` — `kinds` is the list for the current tier. 'ad copy' hits the first tier, 'testimonial' falls through to banned_outright, and 'case study' is in no list, so the function falls out of the loop to the safe default.","cost":0}],"personalize":false,"phase":"build","estSeconds":80,"concept":"policy-router-membership","prompt":"The brand-safety policy is data, so routing a piece to its list is a\nmembership check. `route` walks the policy tiers in order and returns\nthe first tier whose list contains the piece; anything unlisted\ndefaults to `named_approver` — when in doubt, a human signs.\n\nFill in the membership test.\n\nExpected output:\n```\nai_may_draft\nbanned_outright\nnamed_approver\n```\n","code":"POLICY = {\n \"ai_may_draft\": [\"social post\", \"email subject\", \"ad copy\"],\n \"named_approver\": [\"press quote\", \"pricing claim\", \"partner mention\"],\n # AI-drafted only: an AI-drafted review is fabricated by definition —\n # the FTC rule. Genuine customer voices, disclosed, are a different artifact.\n \"banned_outright\": [\"customer review\", \"testimonial\"],\n}\n\ndef route(piece):\n for tier, kinds in POLICY.items():\n if ___:\n return tier\n return \"named_approver\"\n\nprint(route(\"ad copy\"))\nprint(route(\"testimonial\"))\nprint(route(\"case study\"))\n","blanks":[{"id":"membership","accept":["piece in kinds"],"caseSensitive":false,"normalize":"trim"}]},{"type":"checkpoint","id":"campaign-studio/the-numbers-pass/s07-07-checkpoint","xp":8,"hint":[],"personalize":false,"phase":"check","estSeconds":290,"concept":"full-campaign-audit","prompt":"$38","starter":"export = {\"sent\": 18200, \"opens\": 4914, \"clicks\": 618, \"signups\": 212}\n\nreport_claims = [\n {\"metric\": \"sent\", \"value\": 18200},\n {\"metric\": \"opens\", \"value\": 4914},\n {\"metric\": \"clicks\", \"value\": 618},\n {\"metric\": \"signups\", \"value\": 230},\n]\n\nqueue = [\n {\"piece\": \"results-recap email\", \"approved_by\": \"dana\"},\n {\"piece\": \"we-hit-record post\", \"approved_by\": \"\"},\n]\n\n# define campaign_audit(claims, export, queue) below\n\ncampaign_audit(report_claims, export, queue)\n","grader":{"kind":"stdout-equality","expected":"sent 18200 TRACED\nopens 4914 TRACED\nclicks 618 TRACED\nsignups 230 INVENTED (export: 212)\nresults-recap email: OK (dana)\nwe-hit-record post: BLOCKED (no approver)\nverdict: HELD (1 invented number(s), 1 unapproved row(s))\n","normalize":"collapse-trailing-newline"},"solution":"$39","passThreshold":0.66}],"xpTotal":23},{"slug":"synthetic-creator-detection","title":"mass ugc-looking as a channel","estMinutes":20,"prerequisites":["the-numbers-pass"],"status":"live","steps":[{"type":"read","id":"campaign-studio/synthetic-creator-detection/s01-01-mass-ugc-as-a-channel","xp":1,"hint":[],"personalize":false,"phase":"warmup","estSeconds":210,"concept":"mass-ugc-as-channel","body":"$3a","cta":"Got it","runnable":true},{"type":"mc","id":"campaign-studio/synthetic-creator-detection/s02-02-what-the-job-is","xp":2,"hint":[{"level":1,"body":"Leverage the channel with disclosure and a ship checklist. Detection of competitors is supporting; an undisclosed farm is not the answer.","cost":0}],"personalize":false,"phase":"warmup","estSeconds":70,"concept":"leverage-channel-not-detection-hobby","prompt":"Mass UGC-looking / synthetic creators are in the studio as a channel\ncase. What should you take from this lesson?\n","options":[{"id":"run_the_channel","label":"How to run mass UGC-looking as a brand channel — templates, fleet/batch, owned CTA, disclosure + approval, and a campaign receipt"},{"id":"detection_only","label":"Only how to HOLD competitor fake-organic until receipts — detection is the whole job","explain":"Receipts and competitor holds are a supporting beat (intel / quality bar). The spine is running the channel yourself with gates."},{"id":"how_to_farm","label":"The steps to stand up undisclosed agentic accounts and ship fake-organic that looks like random demand","explain":"Covert / undisclosed plants are out of scope. Brand-owned or disclosed synthetic UGC only — no farm-to-deceive playbook."},{"id":"sermon","label":"Write the moral case that synthetic creators are wrong, then add an ethics slide and skip the channel","explain":"A sermon does not replace a ship checklist. If the team runs this channel, they need the operator workflow and the gates."}],"answerIds":["run_the_channel"],"shuffle":false,"runnable":true},{"type":"read","id":"campaign-studio/synthetic-creator-detection/s03-03-run-the-ugc-channel","xp":1,"hint":[],"personalize":false,"phase":"build","estSeconds":230,"concept":"ugc-channel-operator-playbook","body":"$3b","cta":"Got it","code":"# brand campaign fixture — Fieldnote fall UGC drop, not a real person.\ncampaign = {\n \"id\": \"fieldnote_fall_ugc\",\n \"template_arc\": \"day_in_life_coffee\",\n \"fleet_size\": 8,\n \"bio_cta\": \"fieldnote.com/fall\",\n \"disclosure\": \"brand-owned synthetic · paid partnership\",\n \"approver\": \"Dana\",\n \"receipt_logged\": True,\n}\nprint(campaign[\"id\"], \"fleet\", campaign[\"fleet_size\"], \"cta\", campaign[\"bio_cta\"])\n","runnable":true},{"type":"predict","id":"campaign-studio/synthetic-creator-detection/s04-04-predict-the-ship","xp":3,"hint":[{"level":1,"body":"Zero flags is READY_TO_SHIP. Missing disclosure or two-plus flags is BLOCKED. The first campaign clears; the second trips three gates.","cost":0},{"level":2,"body":"First line is `fieldnote_fall_ugc: READY_TO_SHIP (gates clear)`. Second line is `draft_missing_gate: BLOCKED (missing_disclosure, missing_approver, no_campaign_receipt)`.","cost":0}],"personalize":false,"phase":"build","estSeconds":80,"concept":"predict-ready-vs-blocked","code":"$3c","prompt":"Two Fieldnote campaign fixtures run through the same ship checklist.\n`fieldnote_fall_ugc` has disclosure, approver, receipt, CTA, and batch\ndepth. `draft_missing_gate` is the same plan with those three gates\nempty. What prints?\n","grader":{"kind":"stdout-equality","expected":"fieldnote_fall_ugc: READY_TO_SHIP (gates clear)\ndraft_missing_gate: BLOCKED (missing_disclosure, missing_approver, no_campaign_receipt)\n","normalize":"collapse-trailing-newline"}},{"type":"mc","id":"campaign-studio/synthetic-creator-detection/s05-05-what-clears-the-gate","xp":2,"hint":[{"level":1,"body":"Missing disclosure is a hard BLOCK. Fleet size and receipts do not clear an empty disclosure field.","cost":0}],"personalize":false,"phase":"build","estSeconds":70,"concept":"disclosure-required-to-ship","prompt":"Your team wants to ship an eight-account UGC-looking batch for the\nFieldnote fall drop: shared template, product in every bio, same CTA.\nApprover is Dana. Campaign receipt is logged. Disclosure field is still\nblank because \"it looks more organic that way.\" What do you do first?\n","options":[{"id":"block_for_disclosure","label":"BLOCKED — require a disclosure label (brand-owned synthetic / paid partnership) before anything ships"},{"id":"ship_organic","label":"Ship dark. Looking organic is the whole point of the channel.","explain":"Looking creator-shaped is fine. Hiding the material connection is not. Undisclosed plants are out of scope for this lesson."},{"id":"views_first","label":"Post two accounts as a test. If views clear 100k, backfill disclosure later.","explain":"Disclosure is a hard gate before ship, not a patch after reach. The checklist exists so reach never outruns the label."},{"id":"detect_competitors","label":"Ignore your batch. Spend the week HOLDing competitor posts until receipts show real people.","explain":"Competitor detection is a supporting beat. Your job here is to clear *your* ship gates — starting with disclosure."}],"answerIds":["block_for_disclosure"],"shuffle":false,"runnable":true},{"type":"fill","id":"campaign-studio/synthetic-creator-detection/s06-06-fill-the-batch-line","xp":3,"hint":[{"level":1,"body":"The second read set the batch floor at three accounts. The blank is that integer.","cost":0},{"level":2,"body":"`3` — `fleet_size < 3` is True for 1, False for 3 and 8.","cost":0}],"personalize":false,"phase":"build","estSeconds":80,"concept":"batch-floor-is-three","prompt":"Underbatched means the fleet is too thin to treat as a channel. Fill\nthe floor so a one-account hope flags `underbatched`, a three-account\nbatch clears that flag, and the rest of the ship checklist still runs.\n","code":"def underbatched(fleet_size):\n return fleet_size < ___\n\nprint(underbatched(1))\nprint(underbatched(3))\nprint(underbatched(8))\n","blanks":[{"id":"batch_floor","accept":["3"],"caseSensitive":false,"normalize":"trim"}]},{"type":"write","id":"campaign-studio/synthetic-creator-detection/s07-07-write-ship-checklist","xp":5,"hint":[{"level":1,"body":"Walk the five ifs in the prompt order, append flag names, print each as `flag: …`, then pick BLOCKED / NEEDS_WORK / READY_TO_SHIP from disclosure + count.","cost":0},{"level":2,"body":"```python\ndef ship_checklist(campaign):\n hits = []\n if not campaign[\"disclosure\"]:\n hits.append(\"missing_disclosure\")\n if not campaign[\"approver\"]:\n hits.append(\"missing_approver\")\n if not campaign[\"receipt_logged\"]:\n hits.append(\"no_campaign_receipt\")\n if not campaign[\"bio_cta\"]:\n hits.append(\"no_owned_cta\")\n if campaign[\"fleet_size\"] < 3:\n hits.append(\"underbatched\")\n for name in hits:\n print(f\"flag: {name}\")\n if (not campaign[\"disclosure\"]) or len(hits) >= 2:\n print(\"verdict: BLOCKED\")\n elif hits:\n print(\"verdict: NEEDS_WORK\")\n else:\n print(\"verdict: READY_TO_SHIP\")\n return hits\n```\n","cost":0}],"personalize":false,"phase":"build","estSeconds":240,"concept":"write-ship-checklist","prompt":"Write `ship_checklist(campaign)` — the pass that runs before a mass\nUGC-looking batch ships.\n\n`campaign` is a dict with `id`, `template_arc`, `fleet_size`,\n`bio_cta`, `disclosure`, `approver`, and `receipt_logged`.\n\nCollect flags in this order, then print them:\n- `missing_disclosure` when `disclosure` is empty\n- `missing_approver` when `approver` is empty\n- `no_campaign_receipt` when `receipt_logged` is false\n- `no_owned_cta` when `bio_cta` is empty\n- `underbatched` when `fleet_size < 3`\n\nFor each flag, print `f\"flag: {name}\"`. Then print one verdict line:\n- `verdict: BLOCKED` when disclosure is missing OR there are two or\n more flags\n- `verdict: NEEDS_WORK` when there is exactly one flag (and disclosure\n is present)\n- `verdict: READY_TO_SHIP` when there are none\n\nReturn the flag list. The harness prints the campaign id. Expected\noutput:\n```\ndraft_missing_gate\nflag: missing_disclosure\nflag: missing_approver\nflag: no_campaign_receipt\nverdict: BLOCKED\n```\n","starter":"campaign = {\n \"id\": \"draft_missing_gate\",\n \"template_arc\": \"day_in_life_coffee\",\n \"fleet_size\": 8,\n \"bio_cta\": \"fieldnote.com/fall\",\n \"disclosure\": \"\",\n \"approver\": \"\",\n \"receipt_logged\": False,\n}\n\n# define ship_checklist(campaign) below\n\nprint(campaign[\"id\"])\nship_checklist(campaign)\n","grader":{"kind":"stdout-equality","expected":"draft_missing_gate\nflag: missing_disclosure\nflag: missing_approver\nflag: no_campaign_receipt\nverdict: BLOCKED\n","normalize":"collapse-trailing-newline"},"solution":"campaign = {\n \"id\": \"draft_missing_gate\",\n \"template_arc\": \"day_in_life_coffee\",\n \"fleet_size\": 8,\n \"bio_cta\": \"fieldnote.com/fall\",\n \"disclosure\": \"\",\n \"approver\": \"\",\n \"receipt_logged\": False,\n}\n\ndef ship_checklist(campaign):\n hits = []\n if not campaign[\"disclosure\"]:\n hits.append(\"missing_disclosure\")\n if not campaign[\"approver\"]:\n hits.append(\"missing_approver\")\n if not campaign[\"receipt_logged\"]:\n hits.append(\"no_campaign_receipt\")\n if not campaign[\"bio_cta\"]:\n hits.append(\"no_owned_cta\")\n if campaign[\"fleet_size\"] < 3:\n hits.append(\"underbatched\")\n for name in hits:\n print(f\"flag: {name}\")\n if (not campaign[\"disclosure\"]) or len(hits) >= 2:\n print(\"verdict: BLOCKED\")\n elif hits:\n print(\"verdict: NEEDS_WORK\")\n else:\n print(\"verdict: READY_TO_SHIP\")\n return hits\n\nprint(campaign[\"id\"])\nship_checklist(campaign)\n","hiddenTests":[]},{"type":"checkpoint","id":"campaign-studio/synthetic-creator-detection/s08-08-checkpoint","xp":8,"hint":[],"personalize":false,"phase":"check","estSeconds":280,"concept":"two-campaign-ship-audit","prompt":"Checkpoint: two Fieldnote UGC-looking batches want onto next week's\ncalendar. Run the ship checklist on both, then decide whether the\ncalendar may treat the drop as cleared.\n\nWrite `ship_audit(campaigns)`:\n\n1. For each campaign, in order, run the same flags as\n `ship_checklist` (`missing_disclosure`, `missing_approver`,\n `no_campaign_receipt`, `no_owned_cta`, `underbatched`).\n2. Print `f\"{c['id']}: BLOCKED\"` when disclosure is missing OR there\n are two or more flags, `f\"{c['id']}: NEEDS_WORK\"` when there is\n exactly one flag (and disclosure is present), and\n `f\"{c['id']}: READY_TO_SHIP\"` when there are none.\n3. After the loop, print `f\"blocked: {n}\"` where `n` is the BLOCKED\n count, then `calendar: HELD` if any campaign blocked, otherwise\n `calendar: CLEAR`.\n\nExpected output:\n```\nfieldnote_fall_ugc: READY_TO_SHIP\ndraft_missing_gate: BLOCKED\nblocked: 1\ncalendar: HELD\n```\n","starter":"campaigns = [\n {\n \"id\": \"fieldnote_fall_ugc\",\n \"template_arc\": \"day_in_life_coffee\",\n \"fleet_size\": 8,\n \"bio_cta\": \"fieldnote.com/fall\",\n \"disclosure\": \"brand-owned synthetic · paid partnership\",\n \"approver\": \"Dana\",\n \"receipt_logged\": True,\n },\n {\n \"id\": \"draft_missing_gate\",\n \"template_arc\": \"day_in_life_coffee\",\n \"fleet_size\": 8,\n \"bio_cta\": \"fieldnote.com/fall\",\n \"disclosure\": \"\",\n \"approver\": \"\",\n \"receipt_logged\": False,\n },\n]\n\n# define ship_audit(campaigns) below\n\nship_audit(campaigns)\n","grader":{"kind":"stdout-equality","expected":"fieldnote_fall_ugc: READY_TO_SHIP\ndraft_missing_gate: BLOCKED\nblocked: 1\ncalendar: HELD\n","normalize":"collapse-trailing-newline"},"solution":"$3d","passThreshold":0.66}],"xpTotal":25}],"liveLessonCount":4,"liveStepCount":30,"xpTotal":94}},"chapter":"$28:props:tree:detail","lesson":"$28:props:tree:detail:lessons:3","step":"$28:props:tree:detail:lessons:3:steps:1","stepIndex":1,"nav":{"tocNext":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":2},"tocPrev":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":0},"nextByPath":{"developer":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":2},"marketer":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":2},"designer":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":2},"customer-service":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":2},"copywriter":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":2},"data-analyst":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":2},"project-manager":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":2},"hr-specialist":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":2},"operations":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":2},"lawyer":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":2}},"prevByPath":{"developer":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":0},"marketer":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":0},"designer":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":0},"customer-service":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":0},"copywriter":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":0},"data-analyst":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":0},"project-manager":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":0},"hr-specialist":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":0},"operations":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":0},"lawyer":{"chapterSlug":"campaign-studio","lessonSlug":"synthetic-creator-detection","stepIndex":0}}}}]

mass ugc-looking as a channel — step 2 of 8