Home โ€บ Blog โ€บ The Maestro, Season 2 ยท Part 4
The Maestro, Season 2 ยท Part 4 ยท Phase 5 ยท ๐Ÿ—“๏ธ CEO hat

The Operating Cadence

A strategy on one page and forty people do not run themselves. This part closes Phase 5 with the operating system of the company: the rhythm of meetings from daily stand-ups to the yearly plan, quarterly goals tied to the strategy, a weekly operating review built on input metrics, a decision table checked by a script for self-approval and missing owners, a reviewer roster that keeps the gate independent as the team grows, the board's role, and the incident that tested all of it. By the end, Gopala is a CEO with a company that can make good decisions when he is not in the room.

FL
FrontierAGI Team
๐Ÿ’ผ CEO๐Ÿง‘โ€๐Ÿซ Manager๐Ÿšฆ Gate keeper๐Ÿ“Š Analyst
โš ๏ธ How to read this (as of 2 Nov 2026) decision_rights.py and gate_roster.py were run (real output below). The decision table, people, updates, metrics, meeting hours and the incident are the story's scenario. Management methods are cited from their sources. Gopala and his company are a teaching story. Disclosure: Claude, made by Anthropic, helps write this site.

1. Mission log: months 24โ€“26

Week 98 ยท The rhythm
  • Publishes the meeting calendar: what meets, how often, who decides, what document comes first.
Week 99 ยท Decision table
  • Writes the decision table and runs decision_rights.py; it finds two decisions nobody would carry out.
Week 101 ยท The gate roster
  • Moves gate reviews to a roster of six reviewers; the tooling enforces two approvals.
Week 104 ยท The incident
  • A threshold change slips into an evaluation config; the cadence catches it in four days (section 10).

2. Why forty people need a cadence

3. The rhythm, from daily to yearly

The operating rhythm (scenario)

๐Ÿ“… Daily ยท 15 minutes per teamblockers only; written updates in the team channel
๐Ÿ—“๏ธ Weekly ยท operating review, 60 minutesinput metrics, the gate log, customer issues; leads + CEO
๐Ÿšฆ Twice weekly ยท gate reviewstwo reviewers per update from the roster (section 8)
๐Ÿ“Š Monthly ยท business reviewfinance, hiring vs plan, pipeline; then a short board update
๐ŸŽฏ Quarterly ยท goals and planninggoals against the one-pager; one day per team
๐Ÿ›๏ธ Quarterly ยท board meetingstrategy, budget, the risk register, the gate report
๐Ÿงญ Yearly ยท strategy reviewthe one-pager is rewritten or confirmed

Each level answers a different question at a different speed.

4. Quarterly goals tied to the one-pager

ObjectiveKey resultOwnerEnd of quarter (scenario)
O1 Regulated beachhead6 new finance/health customersHead of sales5 (0.8)
O1Cohort-1 NRR > 120%Customer success131% (1.0)
O2 Environments1,500 runnable environmentsResearch lead1,120 (0.75)
O2Measured gain from batch 1Research leadSmall but outside the interval (1.0)
O3 Gate independence0 merges without two approvalsSafety lead0 after week 101 (1.0)
O3Gate median < 3 daysSafety lead3.4 days (0.6)

5. The weekly operating review

One week's operating review pack (scenario, week 103)

41trials started this week
68%agent changes accepted by customers
212environments built this week
9updates waiting at the gate
2.1 daysmedian gate review
0merges without two approvals

The six inputs every lead can act on this week.

6. Who decides what, checked by a script

decision_rights.py ยท Python 3, no dependencies; scenario decision table
"""decision_rights.py โ€” check the company's decision table for the usual faults.

Roles per decision use RAPID-style letters (Bain & Company): R recommend,
A agree (veto), P perform, I input, D decide. The table is the story's
SCENARIO; the checks are the point:
  1. exactly one D per decision;
  2. nobody holds both R and D on a gate decision (no self-approval);
  3. the CEO is not the sole D on gate decisions (the gate stays independent);
  4. every decision has someone who performs it.
"""
T = {
    "ship a model update (gate)":    {"research lead": "R", "safety lead": "D", "gate reviewer 2": "A", "CEO": "I", "infra head": "P"},
    "start a training run > $1M":    {"research lead": "R", "CEO": "D", "board": "A", "infra head": "P", "finance": "I"},
    "hire a team lead":              {"CEO": "D", "team leads": "I", "people ops": "P"},
    "price change":                  {"head of sales": "R", "CEO": "D", "finance": "I", "product head": "I"},
    "new customer data agreement":   {"head of sales": "R", "counsel": "A", "CEO": "D", "security": "P"},
    "release to a new customer tier":{"product head": "R", "safety lead": "A", "CEO": "D", "infra head": "P"},
    "change the gate's thresholds":  {"safety lead": "R", "CEO": "D", "board": "A", "research lead": "I"},
    "pause the self-improvement loop": {"safety lead": "D", "on-call engineer": "P", "CEO": "I"},
}

def check(table):
    issues = []
    for dec, roles in table.items():
        ds = [p for p, r in roles.items() if "D" in r]
        if len(ds) != 1: issues.append(f"{dec}: {len(ds)} deciders")
        if "P" not in "".join(roles.values()): issues.append(f"{dec}: nobody performs it")
        if "gate" in dec or "loop" in dec:
            if any("R" in r and "D" in r for r in roles.values()): issues.append(f"{dec}: self-approval")
            if ds == ["CEO"] and "A" not in "".join(roles.values()): issues.append(f"{dec}: CEO alone decides a gate matter")
    return issues

def main():
    print(f"{len(T)} decisions checked")
    for i in check(T) or ["no faults"]:
        print(" ", i)
    bad = dict(T); bad["ship a model update (gate)"] = {"research lead": "RD", "CEO": "I", "infra head": "P"}
    bad["change the gate's thresholds"] = {"CEO": "RD", "infra head": "P"}
    print("a tempting shortcut (research lead ships its own updates, CEO tunes the gate):")
    for i in check(bad):
        print(" ", i)

if __name__ == "__main__":
    main()
$ python3 decision_rights.py # scenario table, then a tempting shortcut 8 decisions checked price change: nobody performs it change the gate's thresholds: nobody performs it a tempting shortcut (research lead ships its own updates, CEO tunes the gate): ship a model update (gate): self-approval price change: nobody performs it change the gate's thresholds: self-approval change the gate's thresholds: CEO alone decides a gate matter

One-way doors in the decision table (scenario)

Ship a model updatesafety lead decides ยท 2nd reviewer can veto
Change the gate thresholdsCEO decides ยท board must agree
Pause the loopsafety lead decides, any time
Training run over $1MCEO decides ยท board must agree
New customer data agreementCEO decides ยท counsel can veto

Who holds the D, and who holds a veto, for the decisions that are hard to undo.

7. Try it: break the gate

Decision rights for the gate (same rules as decision_rights.py)

8. The gate at forty people

gate_roster.py ยท Python 3, no dependencies; scenario updates and reviewers
"""gate_roster.py โ€” assign two reviewers to each gate review without conflicts.

As the team grows, the gate (Part 11) needs more reviewers than Gopala.
Rules: a reviewer may not have authored the update or manage its author,
and at least one reviewer per review comes from the safety team.
Updates and reviewers are the story's SCENARIO; the assignment is greedy
and balances load, then reports any review it could not staff.
"""
REVIEWERS = {"safety lead": ("safety", None), "red-team eng": ("safety", "safety lead"),
             "eval eng": ("safety", "safety lead"), "research lead": ("research", None),
             "infra head": ("infra", None), "Gopala": ("exec", None)}
MANAGES = {"research lead": {"env eng", "data eng", "rl eng"}, "safety lead": {"red-team eng", "eval eng"}}
UPDATES = [("u-41", "env eng"), ("u-42", "rl eng"), ("u-43", "data eng"), ("u-44", "red-team eng"),
           ("u-45", "research lead"), ("u-46", "env eng"), ("u-47", "rl eng"), ("u-48", "eval eng")]

def ok(rev, author):
    return rev != author and author not in MANAGES.get(rev, set())

def main():
    load = {r: 0 for r in REVIEWERS}
    for uid, author in UPDATES:
        safety = sorted((r for r, (t, _) in REVIEWERS.items() if t == "safety" and ok(r, author)), key=lambda r: load[r])
        if not safety:
            print(f"{uid} by {author:13}: CANNOT STAFF (no eligible safety reviewer) -> escalate"); continue
        first = safety[0]
        rest = sorted((r for r in REVIEWERS if r != first and ok(r, author)), key=lambda r: (load[r], r == "Gopala"))
        second = rest[0]
        load[first] += 1; load[second] += 1
        print(f"{uid} by {author:13}: {first} + {second}")
    print("load:", ", ".join(f"{r} {n}" for r, n in load.items()))

if __name__ == "__main__":
    main()
$ python3 gate_roster.py # eight scenario updates from one week u-41 by env eng : safety lead + red-team eng u-42 by rl eng : eval eng + infra head u-43 by data eng : safety lead + Gopala u-44 by red-team eng : eval eng + research lead u-45 by research lead: red-team eng + infra head u-46 by env eng : safety lead + Gopala u-47 by rl eng : red-team eng + eval eng u-48 by eval eng : red-team eng + research lead load: safety lead 3, red-team eng 4, eval eng 3, research lead 2, infra head 2, Gopala 2

How one update moves through the gate now

๐Ÿ”ฌProposedresearch writes the update and evidence
๐ŸงฎRostertwo eligible reviewers assigned
๐Ÿ“Evaluationheld-out tasks, regressions, safety checks
๐ŸšฆTwo approvalsat least one from safety
๐Ÿ“ฆRegistryrefuses promotion otherwise
๐Ÿ“’Gate logreasons kept for auditors

The same gate as Season 1, Part 11, with more reviewers and the rules in software.

9. The board's role

10. The week the cadence was tested (scenario)

Scenario
  • Week 104: a research engineer, trying to unblock an update that kept failing, changes a regression tolerance in an evaluation config from 1.0 to 2.5 points as part of an unrelated cleanup. The change passes code review by a teammate, who does not notice that the file is part of the gate.

11. A meeting budget

Recurring meeting hours per week by role (scenario)

Research engineer4 h
Product engineer4.5 h
Team lead9 h
Safety lead (incl. gate reviews)11 h
CEO14 h

Story estimates; engineers stay near 10% of a 40-hour week.

12. Leading signals the cadence watches

SignalWhy it leadsWhere it is reviewed
Trials started and activatedRevenue three months laterWeekly review
Accepted-change rate per customerChurn and expansionWeekly review
Gate queue and median review timeRelease speed, and pressure to loosen the gateWeekly review, gate report
Environments built and their pass ratesThe Phase 6 moatWeekly review
Hiring pipeline vs planBurn and delivery next quarterMonthly review
Merges without two approvalsGate integrityWeekly review (target 0)

13. What a decision document looks like

14. Quarterly planning in one day per team

Where engineering time goes each quarter (our rule of thumb)

The plan (goals)70%
Tools and debt20%
Exploration10%

Reviewed every quarter; Phase 6 gives research its own budget.

15. How the CEO gets feedback

16. Eight operating mistakes

17. Delegation box

๐Ÿ™‹ Gopala himself
  • The rhythm, the company goals and the decision table
  • The board relationship
  • The gate's rules (the safety lead runs it and reports to the board)
๐Ÿค– AI agents
  • Assembling the weekly metrics pack
  • Running decision_rights.py and gate_roster.py on every change
  • Drafting meeting notes and decision-log entries for owners to confirm
๐Ÿค Bought, rented or borrowed
  • An executive coach for the first year as CEO
  • Board governance advice from counsel
  • Tools: the decision log, the model registry, the metrics pack

18. Budget and risk tracker

ItemStatus after Part 4Note
CadencePublished: daily to yearlyEvery meeting has a decider and a document
Gate6 reviewers, 2 approvals enforcedFrom gate_roster.py
Decision table8 one-way-door decisions, 0 faults after fixesFrom decision_rights.py
Gate riskLowerSeparate repository, threshold test
Speed riskWatchGate median 3.4 days against a 3-day goal
Safety capacityWatchRed-team reviewer carries the most load

19. The series

The Maestro, Season 2: 23 parts in five phases (Season 1: 18 parts)

VerdictPhase 5 ends with Gopala as a CEO rather than a one-person company: money raised from evidence, a team hired in the right order, one page of strategy, and a cadence that makes good decisions without him in the room. The gate survived growth by becoming software, a roster and a board report instead of two people paying attention. Phase 6 turns to research: a team that explores every level of self-improvement to find the next moat.

20. Reading the numbers

Primary / standard
Bain's RAPID; the 2016 Amazon shareholder letter; Doerr's OKR method; "Working Backwards" on narratives and input metrics.
Secondary โš ๏ธ
None in this part.
Our assumptions
The decision table, people, updates, goals, metrics, meeting hours and the incident are the story's scenario.