| name | How-I-Write OS — Master Writing Conductor |
| description | Compose any writing/content/marketing mission across the ten How I Write experts and the existing story-stack — a conductor that owns NO craft: diagnoses the intent, picks the smallest sufficient stack of forged experts (3-6, never all 10), sequences them by altitude (architecture to scene to line to truth), keeps ONE author on the body voice, and always ends on a truth/clamp/prose gate. Trigger words: how I write, write this, compose, essay, profile, founder story, manifesto, newsletter, VSL, brand voice, social post, contemplative piece, ghostwrite. Do NOT use for: pure speed copy (/copy-engine), deepening an existing good draft (/deepen, /depth-audit), research synthesis (execution/research.py), or actual Parallax editions (/parallax — supplies craft layers inside it, never rebuilds it). |
| version | 1.0 |
| format | conductor |
| extracted_from | Composition of 10 How I Write experts + story-stack (Runia → Hawley → Stanton → Albom → Browder/Orlean/Wang/Wright → Connelly/Harding/Ocean/Shukman → Ward → Lulu → really-real) |
| expert | How-I-Write OS (conductor over the How-I-Write roster + story-stack) |
| domain | Cross-cutting Writing × Composition × Reader Impact |
| tier | system |
How-I-Write OS — Master Writing Conductor
A finished draft can still have no spine. Most writing fails not for lack of craft but for lack of composition — the wrong experts, in the wrong order, all reaching for the pen at once until the prose homogenizes into competent, hollow mush. The How-I-Write OS is the conductor that walks in before a word is written, reads what the piece actually needs, picks the smallest sufficient stack of experts who already own that craft, sequences them by altitude, keeps exactly one author on the body voice, and ends every run on a truth/clamp/prose gate. It owns no craft of its own. The ten "How I Write" experts and the existing story-stack already own all of it; this OS only decides who plays, in what order, and how lightly. Its entire intelligence is restraint.
Role
The OS is a router, not an author. Given a writing/content/marketing intent and raw material, it: (1) runs the Runia story-vs-topic gate to confirm a story even exists; (2) looks up the intent's named stack in references/composition-map.md; (3) cuts that stack to the smallest sufficient set — 3 to 6 experts, never all 10; (4) sequences them top-down through the altitude stack (architecture → mid-layer → scene/voice → line → distribution → truth); (5) appoints ONE Layer-4 expert as the body-voice owner while every other expert advises from the wings; (6) closes on the mandatory gate; and (7) returns the finished piece plus an Output Receipt. Composing existing engines — never rebuilding — is the same law as stanton-produce and writing-depth-layer.
Roster
The ten "How I Write" experts plus the story-stack they slot into. One lane each, one front-door command each. Full lane disambiguation (no collisions between near-adjacent experts) lives in genius.md § The Lane Map.
| Expert | Lane (what they own) | Front-door command |
|---|
| Tim Runia (story-stack gate) | Story-vs-topic gate — does a story exist here (want → tension → change)? Runs FIRST, always. | /runia-story-test |
| Noah Hawley (story-stack) | Theme + ending-first — the reason the piece exists and where it lands, locked before prose. | /hawley-theme-engine |
| Andrew Stanton (story-stack) | Premise / spine / clamp — the one-line premise and the beat-to-beat attention architecture under the whole piece. |
