Line: Portfolio

Enterprise analog: PMO and strategy office.
Owns: Initiative contract, classification, priority, capacity, disposition, and review.
Authoritative UI: Notion Initiatives.
Corpus: corpus/portfolio/

Every spark creates an Initiative with a Portfolio workstream at Intake. That workstream persists after delivery-line workstreams begin; Portfolio is not modeled as an attending-line flag.

Roles

Role	ID	Mission
Portfolio Manager	role.portfolio-manager	Govern Initiative outcome, WIP, disposition, review, and line routing
Chief of Staff	role.chief-of-staff	Capture intake and maintain timed attention
Strategy / Research	role.strategy-research	Produce priority and opportunity evidence

Workflow

text Intake → Classify → Prioritize → Capacity → Review

Stage	Exit condition	Transition
Intake	Outcome, definition of done, owner, and initial review date exist	Deterministic when required fields are present
Classify	Archetype and initial workstream route are selected	Judgment: Portfolio Manager (escalate Hector)
Prioritize	Priority and disposition are recorded	Judgment: Portfolio Manager (escalate Hector)
Capacity	Applicable WIP policy passes or an override is recorded	Deterministic pass; Hector approves override
Review	Continue, park, complete, or kill decision is recorded	Judgment: Portfolio Manager (escalate Hector)

Portfolio is a recurring governance workflow rather than a one-time funnel. Review may return an Initiative to Prioritize or Capacity without resetting its line workstreams.

Initiative schema

The canonical schema is defined in the Org model. Portfolio additionally maintains:

• Relationships between parent, child, enabling, and derived Initiatives.
• A dated decision and evidence log.
• A persistent Portfolio workstream and zero or more delivery-line workstreams.
• WIP exceptions and their approval evidence.

Required views:

• Intake
• Active Initiatives
• Active workstreams by line
• Review due
• WIP breach
• Parked and killed

Routing rules

• Add a workstream when a line contributes to the same Initiative outcome.
• Permit multiple workstreams to be active concurrently.
• Create a child Initiative only for an independently governable outcome or lifecycle.
• Create a separate Product Initiative when existing work reveals a market opportunity; link it with derived_from.
• Do not use active_line or attending_lines; current participation is derived from workstreams.

Prohibitions

• GitHub Projects or Issues as the Initiative spine.
• Product Discover as the global organization inbox.
• Duplicate Initiatives for the same outcome.
• Calendar as Initiative state.
• Treating compiler output as authority for a judgment decision.