>Z_ Operating Manual — How to Run AI Builds

          > OPERATING MANUAL
          
        

v2.0 · two AIs, one boss, zero-gap night runs

WHO THIS IS FOR

You run builds with AI (Claude, GPT, Copilot — doesn't matter). You've hit the wall where chat turns into chaos after 30 minutes. This is the operating system that fixes that.

One human. Two AIs. Zero wasted tokens.

YOU · BOSS
decisions only
ARCHITECT · AI CHAT
Chrome · QA · strategy
CLAUDE CODE
builds · always open

1 · big decisions in one burst

answer everything the architect needs

→

2 · architect writes the brief

phases · zero-gap night runs

1 paste →

3 · code builds

smoke test · commit · push

                HANDOFF.md
              

● LIVE

code writes report · risk · 2 ideas → architect QAs it

one live file · two AIs talk through it

5 · boss: 1 paste + gitpush

the only relay left in the loop

(or none, on night runs)

4 · architect reads + QAs

Chrome test · writes next instructions

+ one brilliant idea of its own

←

🌙

NIGHT-RUN RULE

The last brief of the day has ZERO human-gated steps. Night run = beautician, not surgeon. Credentials, confirm-clicks and "does this sound like me?" calls are all cleared earlier — so the run finishes without you.

New logic = daytime supervised. Night runs only format, polish, and verify.

boss sleeps · code + architect run to completion · you read the result in the morning ☾

PLANNING PROTOCOL

ROUND 1

Strategic

15 questions

what & why

→

ROUND 2

Mechanical

15 questions

how

→

ROUND 3

Layout & Build Plan

15 questions

where

→

FINAL

ALIGNMENT

BUILD-SPEC.md

Every major build starts with 3 rounds of 15 questions. Boss decides, Architect structures. No building until alignment is locked.

BUILD PHASES & RISK BUCKETING

PHASE 1 · Skeleton

1 location, end-to-end

PHASE 2 · Roll-out

All locations + Cash Flow + Financing

PHASE 3 · Polish

Formatting · Print · Extract · README · Audit

QA gate ✓

QA gate ✓

QA gate ✓

🔴 OUT OF BUILD

High crash risk, do separately

e.g. openpyxl charts, complex conditional formatting

🟡 SUPERVISED ONLY

New formula logic, untested patterns

e.g. What-If slider, breakeven calculator

🟢 NIGHT-RUN SAFE

Formatting, text, static content, recalc

No new logic, no new formulas, no risk

Before every build, Architect produces a risk matrix. Red never enters the build. Yellow is daytime only. Green runs while you sleep.

HANDOFF PROTOCOL

HANDOFF.md

HANDOFF.md
├── 1. What was built (per step)
├── 2. Deviations from spec (with justification)
├── 3. Verification table (target vs actual, Δ)
├── 4. recalc.py output (status, errors, probes)
└── 5. TWO brilliant ideas
     └── blind spots, improvements, architectural
         insights the Architect hasn't considered

Code writes the report. Architect reads and QAs. If verification fails — Code fixes before next phase. Ideas get evaluated and either adopted into the next brief or parked for later.

COMMUNICATION PIPELINE

BOSS

(you)

◄──►chat

ARCHITECT

(this chat)

◄──►briefs

CLAUDE CODE

(terminal)

Task board

Architect logs task updates & exchange items

Git · project repo

Code commits + push; Boss relays the paste

Accountant

← Auto-generated P&L export

Advisor

← Valuation summary export

Investors / Bank

← One-pager + Memo (on demand)

Boss talks to Architect. Architect talks to Code. Code talks to no one — it builds. External partners get extracted outputs, never model access.

THE PARKING LOT

        > PARKING LOT
      

Running list of ideas, requests, and side tasks that come up mid-conversation. Boss drops thoughts → Architect captures → next brief or parked for future sprint.
✦ Never interrupts the current build
✦ Nothing gets lost
✦ Reviewed at every QA gate
✦ Lives in the task tracker as exchange items
Example:
→ Automate expense categorization from GL export
→ Build executive dashboard for COO
→ Add sensitivity calculator for key negotiations
→ Breakeven analysis per business unit
> 

THE RULES

click any card to expand

RULE {{ rule.num }}

{{ rule.title }}

▾

ADOPT THIS

Fork it. Adapt it. The principles are universal:

→ Separate thinking from execution
→ Plan in rounds, build in phases
→ Night runs = cosmetic only
→ Every handoff has a contract