Skip to content

Chapter 31: SAFe Adoption in FCC

New in v1.4.1. FCC v1.4.0 closed the "ecosystem pivot" pillar by publishing the 10 constellation verticals as independent public repositories. That bumped the coordination surface from "one repo plus sister libraries" to "one authority repo plus 10 public verticals plus JV L2 partners" — and at that scale, a shared vocabulary for scope, cadence, and cross-project dependency tracking stopped being optional. This chapter is the walkthrough of how SAFe 6.0 was adopted in FCC v1.4.1 and what it means for every contributor.

Why SAFe in FCC

There are three things SAFe 6.0 brings that FCC actually needed:

  1. A shared vocabulary — Portfolio Epic, Program Epic, Capability, Feature, Enabler Story — that every contributor can point at on a common diagram instead of inventing ad-hoc labels per sprint.
  2. A portfolio tier that reconciles long-running themes (patent delegation, real seed data, GraphRAG, i18n, multi-user collab) with the per-PI delivery cadence the ARTs actually run.
  3. PI (Program Increment) cadence that synchronises with the Research Center's quarterly rhythm, so cross-repo dependencies don't drift.

What SAFe deliberately does not dictate is implementation style, quality-gate content, or architectural direction. Those remain FCC-canonical. We absorb vocabulary and cadence from SAFe; everything else stays owned by FCC's existing governance layer (see Chapter 9 and Chapter 16).

The authoritative documentation lives under docs/safe/; this chapter summarises the structure and explains how it connects to the persona roster, the event bus, and the audience tracks.

The three FCC ARTs

FCC organises delivery around three Agile Release Trains. Each runs on a 10-week PI with 2-week iterations inside, and each owns a distinct slice of the portfolio. The topology is compact on purpose — more ARTs would add coordination overhead without enabling more parallel work.

flowchart LR
    P[Portfolio] --> F[Framework ART<br/>core src/fcc/<br/>plugins + tests]
    P --> E[Ecosystem ART<br/>10 constellations<br/>+ JV partners]
    P --> D[Docs ART<br/>Guidebook + Books<br/>+ MkDocs site]

    F -.->|owners| FO[PE, RC, BC, DE, FA]
    E -.->|owners| EO[EC, JVC, VDS, SFBI]
    D -.->|owners| DO[DE, TLDR, EC, STE]

    F --> FA[Framework value stream]
    E --> EA[Ecosystem value stream]
    D --> DA[Documentation value stream]
    P --> DL[Delegation value stream]

The Framework ART ships R.I.S.C.E.A.R. and workflow improvements every PI. The Ecosystem ART keeps the constellations and JV partners aligned. The Docs ART keeps the audience tracks readable and the MkDocs site current. Every persona named in the owner column is an existing FCC persona — there are no new meta-roles invented just to fit SAFe's org chart.

The four value streams

Value streams cut across ARTs rather than nesting inside them. FCC runs four:

  1. Framework — ship a better R.I.S.C.E.A.R. and FCC workflow every PI.
  2. Ecosystem — keep the 10 constellations and JV partners aligned and healthy.
  3. Documentation — keep every audience track (decision-makers, architects, developers, auditors, educators, ...) able to read themselves into the framework.
  4. Delegation — grow the ecosystem's ability to accept downstream contributions — plugins, vocabulary providers, vertical packs, and patents.

Each value stream aggregates flow metrics from multiple ARTs. The SMC (SAFe Metrics Crafter) persona, new in v1.4.1, owns the aggregation. It consumes completion events from every ART, rolls them up per value stream, and produces the dashboard that the portfolio uses to plan the next PI.

PI cadence

FCC's PI calendar runs on a 10-week rhythm. The calendar is documented in full at docs/safe/pi-calendar.md; this section gives the intuition.

gantt
    title FCC PI — 10 weeks, 5 iterations
    dateFormat  YYYY-MM-DD
    axisFormat  Week %W

    section Planning
    PI Planning          :done,   plan,   2026-04-22, 3d
    Feature refinement   :active, refine, after plan, 5d

    section Iterations
    Iteration 1          :i1, after refine, 14d
    Iteration 2          :i2, after i1, 14d
    Iteration 3          :i3, after i2, 14d
    Iteration 4          :i4, after i3, 14d
    IP Iteration         :ip, after i4, 14d

    section Close
    System Demo          :demo, after ip, 2d
    Inspect and Adapt    :ia,   after demo, 2d
    Retrospective        :retro, after ia, 1d

Every PI ends with an Inspect and Adapt (I&A) checkpoint where the three ARTs converge, review flow metrics, and commit to the next PI's backlog. This is also when portfolio epics are re-prioritised and new ones added — the portfolio backlog is the authoritative list.

Portfolio epics

Portfolio epics are the long-running themes that span multiple PIs. v1.4.1 seeded five:

  • Ecosystem Pivot Completion — publish the 10 constellations (landed in v1.4.0) and make them healthy consumers of FCC.
  • Patent Delegation to PHOENIX — move ecosystem IP to ai-coe-docs as the single source of truth. Covered in depth in Chapter 33.
  • Industry Paper Pipeline — drafts go to the Research Center for extension and submission. Covered in Chapter 34.
  • Dual-Bus Event Model — physical separation of PAOM and UX event lanes. Covered in Chapter 32.
  • Zachman Coevolution — absorb the 6×6 cross-cut from ice_ext and make it canonical. Covered in Chapter 35.

Each of the five gets a dedicated file under docs/safe/portfolio/ with a state, owner, ART allocation, and PI-by-PI burn-down.

The SMC and SFBI personas

Two personas were introduced in v1.4.1 specifically to make SAFe sustainable:

  • SMC — SAFe Metrics Crafter (category jv_governance). Owns flow metrics, PI objectives, and quality-gate aggregates. Every ART reports metrics in a format SMC can aggregate; SMC produces the portfolio-level dashboard at each I&A.
  • SFBI — SAFe-FCC Bridge Interpreter (category jv_governance). Translates between SAFe vocabulary and FCC vocabulary. Portfolio Epic ↔ Layer 1 (ROADMAP), Program Epic ↔ Layer 2 (SAR), Capability ↔ feature-set in the MkDocs nav, Feature ↔ a PR. SFBI is the persona you bring to a RC-vs-FCC coordination meeting so the two sides don't talk past each other.

Both personas carry full R.I.S.C.E.A.R. specifications and are registered in the main persona registry. See the core personas YAML for the authoritative definitions.

The SAFe ↔ FCC vocabulary table

The explicit crosswalk between SAFe and FCC vocabulary is maintained as a single-source-of-truth file at docs/safe/safe-fcc-vocabulary.md. The short version:

SAFe term FCC equivalent Notes
Portfolio Epic ROADMAP section (Layer 1) Multi-PI theme
Program Epic SAR section (Layer 2) PI-scale architecture
Capability MkDocs nav section Shipped user-visible block
Feature Merged PR Single-iteration deliverable
Enabler Story Technical debt ticket Supports future features
Iteration Sprint 2 weeks
PI Program Increment 10 weeks, 5 iterations
I&A Inspect and Adapt PI retrospective

SFBI reviews this table every PI and updates it as vocabulary drifts on either side.

What SAFe does not change

It is worth restating what stays the same. FCC's governance layer is unchanged: the 58 quality gates, the constitution registry, the R.I.S.C.E.A.R. 10-element spec, the 99% coverage gate, and the persona-evolution ladder are all exactly where they were in v1.3.11. SAFe provides wrapping for planning, not replacement for quality. A PR that would not merge before SAFe still does not merge after.

Key takeaways

  • FCC v1.4.1 adopts SAFe 6.0 for vocabulary and cadence, not for implementation style or governance.
  • Three ARTs (Framework, Ecosystem, Docs) run 10-week PIs with five 2-week iterations each.
  • Four value streams (Framework, Ecosystem, Documentation, Delegation) cut across ARTs; SMC aggregates the flow metrics.
  • SFBI translates SAFe vocabulary to FCC vocabulary so cross-repo coordination with RC and PHOENIX stays fluent.
  • The authoritative docs live under docs/safe/; this chapter is the guidebook-level summary.