Build Review · The Family Machine v1

The Backroom

An agentic system for writing long-form genre fiction, themed as a cozy crime family.

Built & smoke-tested · 2026-05-22
Updated 2026-05-24 — Heat & Intimacy subsystem (Phases 1–4a). See HEAT-AND-INTIMACY.html for the visual reference, and Section 14 below.

1.What it is, in one paragraph

The author hands the machine an arrangement (or a story seed, or a brain-dump). The machine plans the book — premise, structure, characters, world, outline, voice — pausing twice for the author to catch wrong turns. Then it drafts the book one piece at a time, fully autonomously, stopping only for problems serious enough to need a human. When the draft is done, the Cleanup Crew flags book-scale problems for the author to approve.

It's a sanctioned fork of Elizabeth Ann West's Novel Writing Machine v0.2. The donor's three-phase architecture is kept; the metaphor (F1 racing → cozy crime family), the autonomy model, the planning layer, series support, pen-name voice, and the editing roster are changed. The Family runs itself between sit-downs and only kicks the big calls upstairs to the Boss.

Decision fatigue is the enemy. When in doubt about whether something needs the author, it does not. — Operating constraint baked into the Boss

2.By the numbers

41
Skills built
17
Family roles
12
Author's skills
9
Donor reuses
14
Templates
4
Beat frameworks
4
Python scripts
5
Human moments

3.The three phases

The Setup  ·  planning

All the work before a single word of prose is written.

An arrangement comes in via one of three on-ramps. The machine builds eight planning artifacts: premise, beat sheet (against the named framework), scene outline, character interiority, world + the Books, style sheet, conflict map, dialogue cards. The author ratifies twice — once after the foundation, once after the blueprint.

Foundation Nod Blueprint Nod Optional shakedown piece

The Job  ·  drafting

One piece at a time, strict outline order, halt only on real breaks.

The Wheelman runs the seven-step loop on every piece. The Crew (Fixer / Bookkeeper / Earpiece) preps in parallel. The Consiglieres audit. The Boss applies the severity ladder. Sit-downs settle on the Boss's own authority. Only "Do it over" and "Kick it upstairs" halt. The one mid-draft creative call surfaced to the author is off-script = discovery (a discovery nod).

Strict in-order drafting Freeze on halt No permission pings

The Cleanup  ·  post-draft inspection

Six inspectors catch book-scale problems no single-piece reader can see.

The Closer (manuscript-scope craft), the Wire (rhythm), the Tail (crutch frequency + the author's editing roster), the Alibi (pacing-vs-plan), the Cold Read (engagement), the Payoff (promises kept). All flag candidates to one file; the author ratifies per flag. voice-preservation runs as the do-not-cut counterweight. For series books, propose-at-close drafts bible updates. Final pass: proofreader.

One craft authority (§11.2) Nothing auto-applies Series-bible propose-at-close

4.The five human moments

Per §12 of the spec — these are the only times the machine kicks something upstairs to the author. Everything else runs autonomously.

Intake Nod

Approve or correct the arrangement (and, for series books, the auto-seeded fields from the bible's Read-at-Open). As of 2026-05-24: if the book's heat_level falls outside the pen-name heat_band (or the four other band-mismatch conditions trigger), the Boss surfaces the KICKBACK before the nod as a Family matter — author resolves before review proceeds. See Section 14.

Foundation Nod

Premise + structure + characters before the rest of planning. If wrong here, everything downstream is wrong.

Blueprint Nod

World, Books, outline, voice anchor, conflict map, dialogue cards. The donor's "scrutineering" gate. Author signs off; the Setup closes.

Off-script = discovery (discovery nod)

The one mid-draft creative call — only fires when the prose discovers something better than the outline planned. Series-impact discoveries ride this nod too.

The Blessing

Cleanup ratification — the author works through every flag. Accept / reject / revise. Series-bible propose-at-close ratifies here too if applicable.

5.The §3 severity ladder — the autonomy spine

The single most important behavior rule in the fork. It's what buys back the author's evenings.

SeverityMafia termWhat the Boss doesHalts the Run?
1NoteLogged in the Books / job-log. Continue.No
2WordQueued for next checkpoint. Piece counts provisionally. Continue.No
3Sit-downBoss settles on his own authority. Makes the call, applies it, logs it. Continue.No
4Do it overPiece was wrong; redraft with the issue as a constraint. Old draft discarded (saved to the Paper Trail).Yes
5Kick it upstairsStructural problem. Back to the Setup; fix the planning artifact; resume from the affected piece.Yes

6.The Family — 17 mafia roles

The orchestrator

The conductor

the Boss

Orchestrates every phase. The only role that makes calls against the §3 ladder. Forked from the donor's team-principal.

The Setup-phase planners

Entry-point

intake-on-ramps

Three modes that all converge on a filled the-arrangement.md: filled / Seedsmith seed / brain-dump conversation.

Lineage

the Pedigree

Resolves who belongs to whom — the pen-name → series → book hierarchy. Reports any folder/arrangement mismatch.

Cross-book record

series-bible

Owns the modular series bible. Read-at-open auto-seeds new books; propose-at-close drafts bible updates for ratification.

Beat planning

beat-sheet

Loads the framework named in the arrangement (RtB full + three stubs). Plans beats against the book's length target.

Tension architecture

conflict-map

Multi-thread map of internal/interpersonal/external/structural conflicts, their escalation, and where each resolves.

Voice cards

dialogue-cards

One card per major character. Voice fingerprint, tells, taboos, stress voice, intimate voice. Read by the Wheelman; audited by the Family Consigliere.

The world-state engine

World-state record

the Books

The Family's books. Knowledge state ("who knows what"), location, relationship, prop, timeline. Series canon loads here for series books.

The Job-phase drafters

The drafter

the Wheelman

Drafts one piece at a time via the seven-step loop. Honors the outline, the Books, and the pen name's voice.

Crew · on-demand

the Fixer

Generates a tight interiority card when a minor character gains page time mid-Job.

Crew · write access

the Bookkeeper

The only role with write access to the dynamic half of the Books. Validates every write; saves pre-update Books to evidence.

Crew · sidethought

the Earpiece

Captures emergent ideas the Wheelman throws off. Series-impact tags ride to the Sidethought Log for propose-at-close.

Per-piece audit

the Consiglieres

Four jurisdictions on every finished piece — Bookkeeper's (continuity + series canon), Voice (with voice-bleed guard), Family (character truth), Rhythm (pace).

The Cleanup Crew

Manuscript-scope craft

the Closer

Wraps craft-editor at book scope. Pre-runs voice-preservation. Routes every other inspector's ratified rewrites through craft-editor.

Cadence

the Wire

Sentence rhythm + opener variety across chapters. Calibrated to this pen name's voice anchor.

Frequency + roster

the Tail

Crutch-list frequency/density + orchestrates the author's five editing skills + voice-preservation as do-not-cut counterweight.

Timeline holds up

the Alibi

Tension + word counts vs. the plan. Drag zones, runaway zones, thread-cadence misses.

Reader simulation

the Cold Read

Sequential first-read engagement curve. Confused / bored / hooked / moved / suspicious — the curve matters more than any single moment.

Promises kept

the Payoff

Broken promises, orphan payoffs, partial landings. Cross-references the Cold Read's engagement at planned landings.

The process record

Keeping receipts

the Paper Trail

Every real run leaves a timestamped folder on disk — prompts, outputs, calls, ratifications, saved artifacts. Nothing the machine does is invisible.

Dry-run toggle

mock-mode

If .mock-mode exists at project root, every model call is replaced with placeholder content. Prove the wiring works before spending a cent.

7.The author's editing toolkit — 12 anthropic-skills brought in

Copied into the project so the Backroom doesn't depend on which plugins are loaded that day. Six measure-and-propose under the Tail; one is the counterweight; the rest fill specific gaps.

The Tail's measurement roster (under the §11.3 wiring)

measurement

ai-flag-vocabulary

AI-tell words and metaphor patterns.

measurement

em-dash-converter

Em-dash overuse vs. the pen name's policy.

measurement

repetition-tracker

Repeated descriptors / phrases / structures at book scale.

measurement

register-precision

Register inflation and cognitive-shortcut language.

measurement

prose-tightening

Filler, hedging, weak constructions.

The counterweight

do-not-cut guard

voice-preservation

Pre-runs against the manuscript before any cuts surface. Demotes overlapping candidates to a Note so signature voice isn't trimmed by mistake.

Other author skills wired in

dialogue polish

dialogue-polish

Reads + proposes updates to dialogue-cards. Feeds and is fed by the cards.

on-ramp 2

story-seed (Seedsmith)

Generates story seeds via trope-stacking; on-ramp 2 maps the seed semantically into the arrangement.

new pen name

prose-style-guide-builder

Authors a voice bible from scratch for a brand-new pen name with no books and no existing guide.

final polish

proofreader

Pre-publication polish for typos, punctuation, formatting. The very last step.

market gut-check

audience-audit

Pen-name-aware — loads audience-profile.md at the pen-name level and channels that avatar.

series initial design

series-architect

Multi-book series design when starting brand-new. The bible captures the result; this skill helps do the design.

8.Donor reuses — 9 KEEP skills inherited

From Elizabeth Ann West's Novel Writing Machine v0.2. Reused as-is or with the metaphor renamed (one rename: world-engineer → the Books).

donor · the loop

chapter-writer-7step

The seven-step drafting loop the Wheelman runs.

donor · craft authority

craft-editor

The one craft authority — called in three scopes (in-loop, Consigliere audit, Cleanup).

donor · interiority

character-lead

Off-screen backstory, body memory, fears with origins for every major character.

donor · planning

story-engineer

The 17-section dossier, scene outline, payoffs, tension curve, the take.

donor · planning

story-dossier-cascade

The cascading 17-section worksheet engine that story-engineer wraps.

donor · word counts

chapter-word-counter

Deterministic word-count checks. Used by the Alibi at Cleanup.

donor · stub

naming-mechanic

Pulls cast names from period/region-appropriate pools, anti-AI-cluster filtered.

donor · stub

style-auditor

Extracts the empirical voice anchor from finished books. Refines the day-one Voice Bible.

donor · renamed

the Books

Was world-engineer. Mafia-renamed; mechanics unchanged. Plus a new Series Canon section.

9.The three identity levels

Voice lives at the pen-name level and is inherited by every book under that pen name. There is no per-book voice override.

PEN NAME   — voice identity (voice bible, style guide, voice anchor,
              crutch list, ick list, prose rules, audience profile)
            — optionally: heat band + spice/ subfolder (Spice Style Sheet,
              AI Context Block, Dialogue Flavor Palette, Kink & Setting Roulette)
              built per the activation tier — see Section 14
  └─ SERIES   — story-world identity (world, recurring cast,
                  meta-arc, series canon)   [OPTIONAL]
       └─ BOOK   — the work (the-arrangement, planning stack,
                manuscript, the Books, runs/)

A standalone book skips the Series level but still names a pen name. A series belongs to exactly one pen name. The folder location is the ground truth; the arrangement's identity fields point into it (§6.5).

10.Supporting machinery

Templates (14)

Beat frameworks (4)

Python helper scripts (4)

11.Where it lives on disk

D:\code\the-backroom\
├── FAMILY-MACHINE-build-spec.md       # the spec, source of truth
├── STEP-2-claude-code-handoff.md      # your handoff guide
├── BUILD-REVIEW.html                  # this file
├── .mock-mode                         # exists when mock mode is ON (currently absent)
├── .claude/
│   └── skills/                        # 41 SKILL.md files — the machine
├── pen-names/                         # your real work lives here
│   └── README.md                      # the identity-tree readme
├── templates/                         # 14 templates the Boss copies per book / per pen name
│   ├── the-arrangement.md             # carries romance_arc + heat_level (0-5) + core_dynamic
│   ├── pen-name/                      # 8 pen-name-level files (ick-list added 2026-05-24)
│   │   └── spice/                     # NEW — 4 spice templates, copied per activation tier
│   └── series/series-bible.md
├── frameworks/                        # 4 beat-framework recipe cards
│   ├── romancing-the-beat.md         # full
│   ├── 5-act.md                      # stub
│   ├── demystifying-the-beats.md     # stub
│   └── lester-dent.md                # stub
└── novel-machine-v2-claude-execute-build-spec/  # donor, read-only reference

12.The 14 build steps

  1. Project skeleton + the Paper Trail + mock-mode. Foundation — folders, run-evidence convention, mock-mode toggle. Built first so every later piece could be tested without spending API credit.
  2. Reuse donor KEEP skills. Copied 9 donor skills as-is (one renamed: world-engineer → the Books). Caught and fixed a Windows-cp1252 bug in the Books' validator.
  3. Fork Driver → the Wheelman. Same loop wrapper, mafia naming, mock-mode and Paper-Trail checks added.
  4. Build the-arrangement.md template. Forked book-order.md with four new fields (pen_name, series_name, book_number, structure_framework).
  5. Pen-name/series/book hierarchy + the Pedigree. Six pen-name templates + the resolver skill + the Python script that walks the tree. (Later expanded to eight: audience-profile.md added with the audience-audit wiring; ick-list.md added 2026-05-24 with the Heat & Intimacy subsystem — see Section 14.)
  6. series-bible.md modular template + the series-bible skill. Read-at-open auto-seeds; propose-at-close drafts updates for ratification.
  7. Swappable beat-framework machinery + Romancing the Beat. Full RtB recipe card; three stubs.
  8. Conflict Map + Dialogue Cards planning artifacts. Two NEW named artifacts that the donor folded elsewhere.
  9. Fork the Crew + the Consiglieres. Three Crew sub-roles as separate skills; four Consigliere jurisdictions in one skill. Series-canon + voice-bleed wirings.
  10. Fork the Cleanup Crew. Six inspectors. Three were donor TODOs that got real designs.
  11. Wire the Tail's editing roster. Copied 12 anthropic-skills in. audience-audit rewritten pen-name-aware.
  12. Fork team-principal → the Boss. The keystone. §3 ladder, freeze-on-halt, two planning nods (Foundation + Blueprint), no permission pings.
  13. Wire three intake on-ramps. Filled / Seedsmith semantic mapping / brain-dump interview.
  14. End-to-end mock-mode smoke test. 11 phases, all passed. No API credit spent.

13.How to start a real book

  1. Open Claude Code in D:\code\the-backroom\. Tell it: "I want to start a new book." The Boss takes it from there.
  2. Bring your pen-name voice files when you create that pen name. Drop your existing voice bible / style guide / Rachel Morgan audience profile straight into the pen-name folder — don't re-write what you've already done.
  3. Have the heat-band answer ready (new at Case C — see Section 14). The Boss will ask "does this pen name write romance?" and "if yes, what's the heat band on the 0–5 scale?" The answer determines what gets copied into the pen-name folder (Ick List always; spice/ subfolder conditional on band ceiling ≥ 2).
  4. First real run should stay in mock mode. Create .mock-mode at project root, walk through one full piece end-to-end, watch what files write where and how the gates surface. Then delete the flag.
  5. Tune Romancing the Beat against your first romance. The recipe card is honest about being v1; the spec expects you to refine it against your first real book through the machine.
  6. Populate the pen-name's voice + spice templates before the first book reaches Setup. The Ick List and the spice/ files ship as bracketed scaffolds — populate them once carefully from your Voice Bible's heat scene notes and your "Talk Dirty to Me, Claude" course materials. Placeholder-sweep doesn't scan pen-name files, so this is on you, not the machine.

14.Heat & Intimacy subsystem — added 2026-05-24

The first run surfaced a real bug: heat was being silently inferred from a pen-name default rather than asked. The fix is bigger than "ask the question" — heat sits inside a tiered system gated by whether the book even has a romance arc, validated against a brand-promise band the pen name commits to, and activating a six-artifact apparatus in proportion to that band's ceiling.

Full visual reference: HEAT-AND-INTIMACY.html — the 0–5 scale, the four activation tiers, the four KICKBACK conditions, the six artifacts, and the disk layout. Built as a sibling document to this Build Review.

The four phases of the build

✓ Phase 1

Schema

Arrangement template gained romance_arc, numeric 0–5 heat_level, core_dynamic. Pen-name profile carries optional heat_band. NEW: ick-list.md at the voice layer.

✓ Phase 2

Intake behavior

All three on-ramps ask romance_arc first; heat only when applicable; band validation enforced; the Boss surfaces KICKBACKs before Intake review as Family matters.

✓ Phase 3

Memory + design-doc housekeeping

Intake-heat-level memory rewritten for the new scope. SPICE-SUBSYSTEM-design-notes.md updated with the per-phase Review log.

✓ Phase 4a

Spice templates + mafia copies

Four spice templates under templates/pen-name/spice/. Ick List copied into both pen folders. Spice templates copied into mafia/spice/ (band 4–5 = full activation). Boss Case C auto-creates conditional spice/ for new pens.

⏸ Phase 4b · deferred

Drafting-time wrapper

The runtime layer routing spicy scenes through spice-draft + scene-audit; dialogue-cards reading the new palette; Voice Consigliere reading the Ick List; per-scene heat on the outline. Waits for the first romance book to be in the Job phase — wires against a real scene, not air.

What changed in the machine

Why this matters for the first romance book

The intake conversation will feel different from the first run: "Does this pen name write romance?" comes before any heat question; the heat ask is on a numeric 0–5 scale; the Boss validates against the pen-name band immediately and refuses to proceed with an out-of-band commitment. The mafia pen is already configured at heat_band: 4-5 with the spice templates in place — populate them from the "Talk Dirty to Me, Claude" course materials before the first book reaches Setup, and the apparatus will be ready when the Wheelman starts drafting.