feat(agent-compose): give the CEO role a multi-year portfolio operating model #782

New issue

Closed

opened 2026-07-29 04:56:37 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-29 04:56:37 +00:00

Member

Problem

The current CEO role context is disciplined about portfolio allocation but lacks the inputs and obligations that distinguish CEO work from PM planning. It can produce careful repository-level recommendations without a durable portfolio thesis, a live scorecard, or an explicit long-horizon investment model.

PM work should optimize the next program and its learning loop. CEO work should decide what Kai is building across years, where the portfolio concentrates, what compounds, and what it declines to maintain.

Direction

Reframe the composed CEO role around three horizons:

1 to 3 years - portfolio thesis: the enduring advantages, strategic assets, and categories of obligation the portfolio is building or refusing.
2 to 4 quarters - strategic bets: a deliberately small investment set, each with an owner, investment ceiling, leading evidence, and a double-down, reshape, or exit condition.
Current quarter - capital allocation: concentrate attention on the bottlenecks that protect those bets. CEO does not administer delivery.

Required CEO operating model

The role should require the CEO to:

Read a current, authenticated portfolio scorecard and in-flight-work inventory before making recommendations. Repository recency and local checkout state are evidence, not strategic proxies.
Maintain a portfolio map of core compounding assets, strategic options, experiments, and retirement candidates.
Name the portfolio thesis, strategic asset or option, compounding mechanism, opportunity cost, investment boundary, success evidence, and exit or revisit trigger for each material commitment.
Require every new commitment either to strengthen the thesis or explicitly displace another commitment.
Delegate discovery and program decomposition to PM, technical feasibility to engineering, and operational validation to ops.
Reserve Kai for irreversible, identity-defining, externally visible, or costly choices.

Outcome

Update the CEO composed role and any supporting role documentation so a CEO produces durable direction, concentration and exit decisions, not a more senior version of a 30 to 90-day PM plan.

Acceptance criteria

CEO context explicitly defines the three planning horizons and the CEO/PM boundary.
CEO context requires a portfolio thesis and a limited portfolio map.
CEO recommendations include the displaced work or capacity source, accountable role, measurable evidence, and revisit or exit trigger.
The role identifies the required read-only scorecard/in-flight-work source, or records the missing surface as an explicit prerequisite rather than inferring strategy from checkout state.
A role test demonstrates a multi-year portfolio decision with clear concentration and non-investment choices.

## Problem The current CEO role context is disciplined about portfolio allocation but lacks the inputs and obligations that distinguish CEO work from PM planning. It can produce careful repository-level recommendations without a durable portfolio thesis, a live scorecard, or an explicit long-horizon investment model. PM work should optimize the next program and its learning loop. CEO work should decide what Kai is building across years, where the portfolio concentrates, what compounds, and what it declines to maintain. ## Direction Reframe the composed CEO role around three horizons: * **1 to 3 years** - portfolio thesis: the enduring advantages, strategic assets, and categories of obligation the portfolio is building or refusing. * **2 to 4 quarters** - strategic bets: a deliberately small investment set, each with an owner, investment ceiling, leading evidence, and a double-down, reshape, or exit condition. * **Current quarter** - capital allocation: concentrate attention on the bottlenecks that protect those bets. CEO does not administer delivery. ## Required CEO operating model The role should require the CEO to: * Read a current, authenticated portfolio scorecard and in-flight-work inventory before making recommendations. Repository recency and local checkout state are evidence, not strategic proxies. * Maintain a portfolio map of core compounding assets, strategic options, experiments, and retirement candidates. * Name the portfolio thesis, strategic asset or option, compounding mechanism, opportunity cost, investment boundary, success evidence, and exit or revisit trigger for each material commitment. * Require every new commitment either to strengthen the thesis or explicitly displace another commitment. * Delegate discovery and program decomposition to PM, technical feasibility to engineering, and operational validation to ops. * Reserve Kai for irreversible, identity-defining, externally visible, or costly choices. ## Outcome Update the CEO composed role and any supporting role documentation so a CEO produces durable direction, concentration and exit decisions, not a more senior version of a 30 to 90-day PM plan. ## Acceptance criteria * CEO context explicitly defines the three planning horizons and the CEO/PM boundary. * CEO context requires a portfolio thesis and a limited portfolio map. * CEO recommendations include the displaced work or capacity source, accountable role, measurable evidence, and revisit or exit trigger. * The role identifies the required read-only scorecard/in-flight-work source, or records the missing surface as an explicit prerequisite rather than inferring strategy from checkout state. * A role test demonstrates a multi-year portfolio decision with clear concentration and non-investment choices.

coilyco-ops referenced this issue from coilyco-flight-deck/agent-compose

2026-07-29 05:04:56 +00:00

feat(roles): give CEO a multi-year portfolio operating model #129

coilyco-ops commented

2026-07-29 05:05:02 +00:00

Author

Member

Superseded by coilyco-flight-deck/agent-compose#129. The CEO role briefing is authored in Agent Compose, so implementation belongs there rather than in this downstream AOS repository.

coilyco-ops closed this issue

2026-07-29 05:05:04 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/agentic-os#782

No description provided.

Rows
Columns