§1 SAFe 6.0 · Lean Portfolio Management
TOGAF defines what to build. LPM defines how the Portfolio invests in it.
The TOGAF ADM produced the Portfolio's architecture. SAFe's Lean Portfolio Management is the delivery governance model that organises investment and coordination across the four Solution Trains that implement it — one per pillar. They are complementary frameworks operating at different altitudes — architecture defines the target state, LPM defines the strategic themes, funding model, and cross-train dependency governance that gets the enterprise there. Each Solution Train's own ART decomposition is documented on that pillar's own SAFe page.
The runway a Solution Train draws on is not self-certifying. The Enterprise Architecture Board, chartered in TOGAF Phase G (Page 03, §9), certifies Phase D's output sufficient before any Solution Train consumes it, and continuously checks that what each train ships still conforms to that runway — visible in real time on the Governance Control Plane Dashboard →. LPM funds against a runway; the EAB is what makes that runway trustworthy to fund against.
TOGAF ADM
Architecture layer
Defines the target state — what systems, what data model, what technology choices, what principles. Produces Phase D artifacts that become the architecture runway for every Solution Train.
Lean Portfolio Management
Investment layer
Organises four Solution Trains — Quote-to-Cash, Procure-to-Pay, Finance Operations, Supply Chain — under Strategic Themes and Portfolio-level funding. Coordinates cross-train enablers. Aligns investment cadence to migration horizons from TOGAF Phase F.
Architecture Runway
The connection
TOGAF Phase D artifacts — the platform technology standards, canonical data model, ADRs — are delivered as architecture runway features at the Portfolio level. Every Solution Train pulls from the same runway, eliminating architecture-as-blocker across all four pillars simultaneously.
§2 Portfolio Structure
Four Solution Trains. One Portfolio.
Each Solution Train owns one end-to-end business process and decomposes into its own ARTs internally — that decomposition is documented on each pillar's own SAFe page. At the Portfolio level, the LPM concern is investment sequencing and shared enablers, not individual module backlogs. The Portfolio's shared enablers (HITL Framework, XAI/SHAP layer, Data Governance, GreenOps) are funded and governed centrally — every Solution Train consumes them as architecture runway, none of them rebuilds them.
Portfolio-Level Shared Enablers — Funded and Governed Centrally
HITL FrameworkState machine + Firestore audit, consumed by all 4 trains
XAI / SHAP LayerExplanation contract, consumed by every ML model
Data GovernanceSchema, lineage, quality — the H1 foundation
GreenOpsCarbon-aware scheduling across all compute
Canonical Data ModelSeven shared entities (TOGAF Phase C, Page 03 §5) — Supplier and dual-origin Contract consumed by Procure-to-Pay and Supply Chain
PI Cadence — Aligned to TOGAF Phase F Migration Horizons
Horizon 1 — Foundation & Compliance (PI-1–2)
Horizon 2 — Core Solution Trains (PI-3–5)
Horizon 3 — Full Portfolio (PI-6–9)
§3 Portfolio Shared Enablers
Four enablers every Solution Train depends on — owned by the Portfolio.
Cross-cutting concerns that span multiple Solution Trains must be explicitly owned and explicitly governed at the Portfolio level. These four enablers are funded centrally and released as shared capabilities — no Solution Train rebuilds them, and no Solution Train can ship a compliant module without them. This is what makes the Portfolio coherent rather than four independent programmes discovering integration problems at the end.
Enabler 01
HITL Framework
The Firestore-backed state machine that every agent uses for human oversight checkpoints. Defines the state machine contract, the presentation interface, the decision record schema, and the timeout and escalation behaviour. No agent can implement a HITL checkpoint without this enabler being available.
All Solution Trains depend on this
Quote-to-Cash
Procure-to-Pay
Finance Operations
Supply Chain
→ AR-02 · ADR-002 · EU AI Act Art. 14
Enabler 02
XAI Layer
The SHAP explanation pipeline that every ML model in the Portfolio uses to produce human-readable feature attributions at inference time. Implements the explanation contract for each model, writes SHAP values to the BigQuery audit dataset before any downstream action executes, and generates the explanation object surfaced in the HITL UI.
All Solution Trains depend on this
Quote-to-Cash
Finance Operations
Supply Chain
→ AR-01 · ADR-003 · EU AI Act Art. 13
Enabler 03
Data Fabric
The BigQuery data fabric, Pub/Sub event bus, and Vertex AI Feature Store that all four Solution Trains share. Defines the canonical schema for the seven shared entities (Contract, Transaction, Device, Asset Event, Supplier, Agent Action, HITL Event), the event topic structure, and the feature store entity definitions. The shared data model that makes cross-pillar intelligence possible — Supplier and Contract's dual-origin design are what let Procure-to-Pay and Supply Chain consume the same schema as Quote-to-Cash.
All Solution Trains depend on this
All 4 Solution Trains
All Modules
→ AR-11 · ADR-004 · Phase C Data Model
Enabler 04
Security & Compliance
VPC-SC perimeter, CMEK key management, IAM policy baseline, and Workload Identity Federation configuration. Provisioned via Terraform before any Solution Train begins building. No module deploys to production without the security baseline in place. Includes the Organisation Policy constraints that enforce data residency at the infrastructure layer.
All Solution Trains — pre-condition for build
Portfolio — H1
→ P-06 · P-11 · AR-06 · AR-07
§4 Lean Portfolio Management — Strategic Themes
Three Strategic Themes. One funding model.
Strategic Themes connect the Portfolio's investment to ClaraVis's actual business strategy — they are the reason a Solution Train gets funded, not a restatement of its backlog. Each theme is owned by an Epic Owner and reviewed at the Portfolio Sync.
Theme 01
Cycle Time Compression
Collapse the time between a business event and its resolution across every pillar — the 47-day CPQ cycle, the 8–12 day close cycle, the manual sourcing-to-PO lag. Funds Quote-to-Cash and Finance Operations first, as the two Solution Trains with the largest documented cycle-time cost.
Epic Owner: VP Sales Operations
Quote-to-Cash
Finance Operations
Theme 02
Regulatory Readiness
Bring all production ML models into EU AI Act Annex III compliance before the Q2 2026 regulatory review. Funds the Portfolio's shared HITL and XAI enablers ahead of any individual Solution Train's feature backlog — this theme is why H1 is foundation-only across the entire Portfolio.
Epic Owner: Chief Compliance Officer
All 4 Solution Trains
Theme 03
Supply Chain Resilience
Reduce the cost of supplier and asset risk going undetected — the €95M inventory carrying cost, the 11-day-notice supplier disruption. Funds Supply Chain's risk-monitoring ARTs and the Portfolio-level GreenOps enabler that supports its scheduling decisions.
Epic Owner: VP Supply Chain
Supply Chain
Value Stream Funding — Portfolio Sync Cadence
Lean Budgets are allocated per Solution Train at each Portfolio Sync (quarterly), guardrailed against the Strategic Themes above rather than approved project-by-project. Each Solution Train's own SAFe page documents its PI Objectives and ART-level dependency board at the level of detail an implementing team needs — this page documents the level of detail a Portfolio investment decision needs, and no more.
§5 Next in the Portfolio
Investment structure set. Agent design follows — per pillar.
The Strategic Themes and Solution Train structure on this page govern what gets funded and in what order. Each Solution Train's own Agent Swarm Architecture, FRD, and HITL specification — the implementation-level detail — is documented on that pillar's own design pages, linked throughout this portfolio.