feat(roles): give CEO a multi-year portfolio operating model #129
Labels
No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agent-compose#129
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The current CEO briefing is disciplined about portfolio allocation but under-specified about the inputs and obligations that distinguish CEO work from PM planning. It can produce repository-level recommendations without a durable portfolio thesis, a live scorecard, or an explicit long-horizon investment model.
PM work optimizes the next program and its learning loop. CEO work decides what Kai is building across years, where the portfolio concentrates, what compounds, and what it declines to maintain.
Direction
Reframe the CEO role around three horizons:
Required operating model
Require CEO to:
Acceptance criteria
Supersedes coilyco-flight-deck/agentic-os#782, which was filed in the downstream AOS repository before the authoritative Agent Compose ownership boundary was recognized.
Landed on canonical main in
ef75fa4. The CEO role skill now defines the 1-to-3-year portfolio thesis, 2-to-4-quarter strategic bets, and current-quarter capital allocation horizons. It requires an authenticated portfolio scorecard and in-flight inventory, explicitly records their absence as a prerequisite, rejects checkout recency as a strategy proxy, maintains a limited four-class portfolio map, and requires displacement, accountable role, evidence, investment boundary, and exit or revisit triggers. The CEO/PM/Engineer/Ops boundaries and a concentration-versus-non-investment decision pattern are covered by a role test. ward exec test and ward exec smoke passed.