OP1 — 12-hour development sprint

1-hour blocks, 7:00 PM → 6:00 AM PDT. Each block: the manager writes their OP1 section; their coworker prepares them via mail (e2m envelopes). Operator drives each block with one skill: /op1-coworker (coworker session) + /op1-manager (manager session).

schedule api

/api/schedule

7:00 PMh1

product-manager ← operator

OP1 kickoff — set the envelope: targets, the 5 providers (GCP/Azure/AWS/Anthropic/OpenAI)

8:00 PMh2

design-manager ← design-coworker

design OP1 — the 8-token system, the platform UI

9:00 PMh3

engineering-manager ← engineering-coworker

engineering OP1 — e2m packages, the workers, CI

10:00 PMh4

data-manager ← data-coworker

data OP1 — e2m-OKF warehouse, freshness

11:00 PMh5

project-manager ← project-management-coworker

delivery rollup + the operator router

12:00 AMh6

operations-manager ← operations-coworker

ops OP1 — deploys, runbooks, uptime

1:00 AMh7

finance-manager ← finance-coworker

finance OP1 — cost, 1p→3p economics

2:00 AMh8

legal-manager ← legal-coworker

legal OP1 — contracts, the OAuth-only posture

3:00 AMh9

compliance-manager ← legal-coworker

compliance OP1 — OTel observability, audit

4:00 AMh10

human-resources-manager ← human-resources-coworker

people OP1 — hiring, onboarding

5:00 AMh11

agent-resources-manager ← agent-resources-coworker

agent-lifecycle OP1 — skills, evals, provisioning

6:00 AMh12

sales-manager ← sales-coworker

sales OP1 — pipeline, GTM