Build Track · M0 · v1 — awaiting Sarmad's read-aloud

0.3 · Workspace Setup & Hygiene

~7 min · five rules · object-job-status naming · the 3am safety system

Spec, sourcing & version notes

v1 (2026-09-23) — generated post-S1/S2 standards (opener, no em dashes spoken, scaffolds + seeds, reel cues, house recap, solo-sequence tease 0.3 → 0.4). Cold open uses the topic-misconception lever (hygiene = cosmetic), per PRODUCTION-STANDARD; no invented anecdotes — the 3am line comes from the curriculum itself.

Track: Build Track · Milestone 0 · Runtime: ~7 min · Artifact: The Workspace Starter (naming convention + folder spec + archive protocol, printable) · Exercise: build your workspace to spec; self-check against the rubric

Sourced from: CURRICULUM 0.3 · SARMAD-INTAKE G4 (inherited messes — partial; step-by-step retellings stay reserved for S4/S5) + G6 (adoption/ownership) · brain/06 · the S2 audit stat (42% one table / half never used — referenced as "you saw in the credit video," not re-told) · production/VOICE-PROFILE.md.

Differentiation from S5: S5 = maintaining workbooks you INHERITED (handover demands, ownership maps, safe-change). 0.3 = setting up YOUR OWN workspace correctly on day one so nobody ever has to inherit a mess from you.

OPEN — FACE, 0:00–0:35

(paid-course opener: orient → stakes → in) Okay, this video is about how you set up your workspace, and I want to kill one idea before we start: this is not about being tidy. Naming and folder structure feel cosmetic until the day somebody opens your workspace at three in the morning, finds four tables called Untitled and New Table Copy 2, and re-runs the wrong one on ten thousand rows. Hygiene is a safety system. You saw in the credit video what one unwatched table can burn. This is the fifteen minutes of setup that makes that mistake close to impossible.

CHAPTER CARD: 0.3 · Workspace Setup & Hygiene
DIAGRAM — the five rules, 0:40–2:30
🎬 REEL CUE — hook: "Your Clay workspace is one 'Untitled table' away from a 3am disaster." The five rules cut as a carousel-style short; rattle them with confidence.

Five rules. That's the whole system.

  1 · NEST everything      no table lives outside a workbook, ever
  2 · NUMBER workbooks     "01 · Inbound" sorts itself; "Inbound" doesn't
  3 · NAME descriptively   [object] + [what it does] + [status]
                           "Companies · TAM enrich · LIVE"
  4 · SEPARATE builds      one project per workbook; test tables get
                           their own sandbox workbook
  5 · ARCHIVE ruthlessly   dead table? archive it TODAY, not someday

Rule one, nest everything. A table outside a workbook is a table nobody owns. Rule two, number your workbooks, because numbered folders sort themselves and unnumbered ones become a junk drawer. Rule three, name descriptively, and use a convention: the object, what it does, and its status. "Companies, TAM enrich, LIVE" tells you everything before you open it. "Untitled table" tells you nothing after you do. Rule four, separate your builds. One project per workbook, and your experiments live in a sandbox workbook, never next to production. Rule five, archive ruthlessly. A dead table sitting in a live workbook is a loaded weapon; somebody will eventually run it.

DIAGRAM — the naming convention, 2:30–3:30

The convention is three parts, and it borrows a rule you may already use in your CRM: lead with the object.

  [OBJECT] · [WHAT IT DOES] · [STATUS]

Companies · TAM enrich · LIVE People · CFO multithread · TEST Companies · funding signal → sequencer · LIVE People · old event list 2025 · ARCHIVED ```

Object first, so everything about companies sits together. Then the job, in plain words. Then the status in capitals: LIVE, TEST, or ARCHIVED. Anyone who opens your workspace, including you in three months, reads the whole system at a glance.

SCREEN — live setup, 3:30–5:30

(outline only — narrate live, mistakes stay in) - Start from a messy sandbox workspace (pre-seed it with Untitled tables and a stray copy) - Create the workbook skeleton: 00 Sandbox · 01 Data Foundation · 02 Inbound · 03 Outbound - Rename two bad tables to the convention on camera, thinking out loud - Drag the stray table into its workbook; archive one dead table - End state: the before/after of the same workspace

RECAP — FACE, 5:30–6:10

Here's a quick recap of what we learned in this video.

One: hygiene is a safety system, not housekeeping. The 3am wrong-table re-run only happens in messy workspaces.

Two: five rules. Nest everything, number workbooks, name descriptively, separate builds, archive ruthlessly.

Three: the naming convention is object, job, status. "Companies, TAM enrich, LIVE." Read the workspace at a glance.

The Workspace Starter under this video has the full spec: the folder skeleton, the convention, and the archive protocol. Set it up once and every build in this course lands in the right place.

EXERCISE CARD — 6:10–6:40

Your exercise: build your workspace to spec. Create the numbered workbook skeleton, rename every existing table to the convention, and archive anything dead. Then check yourself against the rubric on the Workspace Starter. It takes fifteen minutes, and it's the last time you'll ever think about it.

Next up: the Quick-Wins Bank. Fifteen builds you can ship this week, before you've mastered anything.

Production notes
← Back to the Script Room
space play/pause · ↑↓ speed · ←→ size · esc exit
exact script cards · ☰ Pointers switches to bullet prompts (pink = say exactly) · space/→ next · ← back · esc exit