AI-ERA LEADERSHIP OPERATING SYSTEM (LOS)

Use this 30–60–90 day rollout to keep speed and safety aligned when engineers use AI copilots.

PART 1 — WEEKLY SCORECARD (review every Monday, 20 minutes)
1) Delivery
- Deployment frequency (per service / per team): ______
- Lead time for changes (typical): ______
2) Quality
- Change failure rate (deploys causing incident/rollback): ______
- MTTR (typical time to restore): ______
3) Review capacity
- PRs opened per engineer/week: ______
- PRs reviewed per engineer/week: ______
- Typical PR size (files changed / LOC): ______
4) Cost
- Cloud unit cost (e.g., cost per request, cost per active user): ______
- AI/inference unit cost (e.g., cost per action, cost per tokens): ______
5) Security
- Open critical vulnerabilities: ______
- Secrets detected in last 7 days: ______

PART 2 — DEFINITION OF DONE (ship checklist)
A change is only “done” when:
- It has a named owner (service owner + on-call)
- It has automated tests OR an explicit risk acceptance written down
- It is deployable behind a flag OR has a rollback plan
- Observability exists (dashboard + key alerts)
- A success signal is identified (activation, retention, latency, cost, support load)

PART 3 — DECISION ALTITUDE RULES (prevent expensive mistakes)
Implementation (PR-level):
- Refactors, tests, small features; reviewed via PR template + CI gates.
Architecture (RFC-level):
- Datastore changes, auth/billing flows, data retention, cross-service contracts.
Policy: Any irreversible change must have:
- Threat model link
- Reversibility statement (hours/days/weeks)
- Cost and scaling assumptions written down

PART 4 — 30–60–90 DAY ROLLOUT
Days 1–30: Visibility
- Establish scorecard baselines.
- Add a PR template requiring Outcome, Risk, Evidence.
- Identify recurring incident types and write runbooks.
Days 31–60: Constraints that create speed
- Enforce CI gates: severe vuln blocks, secrets detection, required reviews on critical modules.
- Create a lightweight RFC process (keep it short) and a decision log.
Days 61–90: Scale autonomy
- Build paved roads: starter repos, standard logging/metrics, deployment templates.
- Update performance expectations: reward outcomes, reliability, and reusable foundations (not volume).

PART 5 — 1:1 QUESTION SET (manager as debugger)
Ask each week:
- What assumption in your plan is most likely to be wrong?
- What decision is blocked, and who must make it?
- What is the biggest risk in your work (security, reliability, cost, product)?
- What proof will we accept that this worked?

If you do nothing else: make decisions explicit, enforce guardrails in tooling, and judge work by outcomes. AI can draft. Your job is to decide and verify.