01 Production map

Your production map: seven steps from idea to customer, and at each step one named person who answers one question before the work moves on. That question is the gate.

AI acts at every step. Nothing passes a gate because a tool said it was fine.

I would have a single person draft the map from a change you shipped last month. Then check it with three people who do the work, one at a time.

The gates are what you keep. The cards are what you hand the team.

Keys

Hat	Decides
Way of working owner	Any change to a production step, and who wears which hat. Usually you
Tool owner	Whether a tool comes in or stays (approval A1, part 03)
Rules owner	Data sources and what an agent may touch (approvals A2 and A3, part 03), and exceptions
Experience quality owner	Whether generated UI or copy is fit to ship. A designer if there is one, otherwise the PM, never an engineer
Customer contact owner	Whether an AI reply reaches a customer unread, and how it is labeled

Reviewer of record is a rule, not a hat: whoever merges, publishes or sends a change owns it as if they made it by hand.

From part 04	What it is	Until it exists
patterns.md	One file in the repo that says what good looks like. The tools read it	The reviewer compares the new screen with the nearest existing one
High severity list	One paragraph naming where a defect is costly: money, account, data, first time use, anything that cannot be undone in one step, legal and promise text, flows customers complained about. A change that touches it goes to the high lane	Every change touching money, account, data or first time use goes to the high lane
Release checklist	The author runs it and attaches evidence to the pull request: one screenshot per state, the checker result, the lane. Whoever merges confirms it is there	The author attaches one screenshot per state and says which lane

Start minimum, my judgment. On the Start path, in month one only G3, G4 and G7 run as written. The other gates read "the founder decides" until a defect, a complaint or a queue says otherwise.

How to fill it in

[ ] Pick one change shipped last month. Follow its ticket from idea to customer. About an hour, alone
[ ] Name each step in your own words, then fold them into the seven: discovery, design, build, review, release, operate, support. Write "none yet" for any you do not have
[ ] For each step: who does it, what comes in, what goes out. Artifacts, not intentions. "A merged pull request" is an artifact. "Alignment" is not
[ ] Mark where AI already acts, from the part 00 inventory: which tool, whose hands
[ ] For each step, write the one question a human answers before work moves on, who answers it, and what they look at. "None yet" is the finding
[ ] Show the map to three people who do the work, one at a time, ten minutes each. Write down where they would draw it differently
[ ] In the week after, each person who decides at a gate writes the card for that step, about twenty minutes. On Start, month one needs three cards: build, review, support
[ ] At about 150 people, map one team first: the one with the longest review queue

Team: {{name}}. Drafted by: {{name}}, on {{date}}. Change followed: {{ticket or pull request}}. Shown to: {{three names}}, who would draw it differently at: {{where, or nowhere}}. Path: {{Start or Fix}}.

Keys

How to fill it in

A. Steps