Skip to content

Value Streams

FCC's four value streams cut across the three ARTs. Each value stream describes a coherent slice of ecosystem output that delivers measurable value to a named audience. Portfolio epics (epics.md) map to exactly one value stream; ARTs (../arts/) may contribute to multiple.

1. Framework

The Framework value stream delivers improvements to the core src/fcc/ Python package, the R.I.S.C.E.A.R. specification, the workflow graph engine, the action library, the simulation engine, the compliance pipeline, the CLEAR+ evaluation stack, and the plugin ecosystem (including the 11 plugin types). The audience is every downstream consumer — sister projects, JV partners, constellation verticals, and external users who install fcc-agent-team-ext from PyPI. Value is delivered as a better R.I.S.C.E.A.R. + FCC workflow every PI: higher CLEAR+ benchmark scores, faster framework start-up, cleaner plugin contracts, and additional personas that extend the canonical catalogue without breaking downstream consumers. The Framework ART is the primary delivery train. Portfolio epics carried by this stream include real canonical seed data (PE-002), GraphRAG (PE-001), real-time multi-user collaboration (PE-004), performance optimization (PE-006), and the dual-bus event-split architecture shipped in v1.4.2 (PE-008). Framework value is the keystone: every other value stream depends on a healthy framework as its upstream.

KPIs

  • Throughput: PRs merged into main per PI (target: ≥25 per PI, trend-stable).
  • Lead time: first-commit to merged-PR median (target: ≤72 hours for non-enabler PRs).
  • Quality gate pass rate: PHOENIX 58-gate registry aggregate pass rate (target: ≥95% per release).
  • CLEAR+ aggregate score: 7-dimension weighted score (direction: non-negative trend across 4 rolling PIs).
  • Test coverage: branch coverage against the coverage ratchet (target: ≥99%, enforced by CI gate).
  • Customer NPS: measured via the fcc feedback flow from sister projects (target: ≥40 trailing-quarter).

2. Ecosystem

The Ecosystem value stream keeps the 10 constellation verticals (Ophiuchus, Serpens, Libra, Crater, Scutum, Norma, Pyxis, Vela, Columba, Caelum), the JV L2 partners (athenium, mnemosyne, ice_ext, research_center_ext), and the vendored ecosystem registries (port allocation + project inventory under src/fcc/data/ecosystem/) aligned and healthy. The audience is the ecosystem's operators: CONSTEL coordinators, JV stewards, constellation maintainers, and plugin authors. Value is delivered as a coherent multi-repo ecosystem where vocabulary, ports, and contracts never drift: zero SHA-256 drift between FCC's packaged vocabulary mappings and upstream providers; zero port-allocation conflicts with the RC NEXUS v2.1.0 registry; successful cross-project federated search; and the ecosystem-integration-tests CI gate staying green. Portfolio epics carried here include advanced bidirectional federation (PE-005) and the POLARIS/LYRA bridge integration (PE-009). The Ecosystem ART drives delivery, but the Framework ART supplies the contracts this ART must honor.

KPIs

  • Throughput: cross-repo PRs coordinated per PI (target: ≥15 per PI across the 10+JV surface).
  • Lead time: constellation upstream-to-sync median (target: ≤10 business days for a framework release).
  • Quality gate pass rate: VocabularyProviderPlugin SHA-256 parity rate (target: 100%).
  • Port-conflict count: against RC NEXUS v2.1.0 (target: 0, enforced by drift test).
  • Federated search success rate: cross-namespace query success (target: ≥99%).
  • Ecosystem-integration-tests CI gate pass rate: rolling 4-PI (target: ≥95%).

3. Documentation

The Documentation value stream keeps every persona-aligned audience (decision-makers, architects, developers, auditors, educators, knowledge engineers, operators, scientists, data-architects, professionals, teams) able to read themselves into the framework. This covers the 24-chapter FCC Guidebook, the 3-book series (30 chapters), the 23 Jupyter notebooks, the 27 Streamlit apps, the 19+ guided demos, the 173 auto-generated model cards, the MkDocs site, and the multi-format publishing pipeline (Quarto + Pandoc + Typst). The audience is anyone reading FCC documentation — from a first-time adopter browsing the guidebook to a compliance officer looking for a specific EU AI Act mapping. Value is delivered as continuously regenerated, audience-aware, machine-readable documentation that tracks the codebase without falling behind. Portfolio epics carried here include internationalization (PE-003). The Docs ART drives delivery, while TLDR enforces the three-layer convention ecosystem-wide.

KPIs

  • Throughput: doc-impact PRs landed per PI (target: ≥20 per PI).
  • Lead time: code-change-to-doc-regen median (target: ≤48 hours).
  • Quality gate pass rate: docs-as-code gates QG-DOC-001..005 aggregate (target: 100%).
  • MkDocs strict-mode build success: per-release build pass rate (target: 100%).
  • Publication artifact count: books + executive + presentations + academic + reference-cards (target: ≥27, growing with coverage).
  • Model-card freshness: median age gap between persona YAML change and card regen (target: ≤24 hours).
  • Audience-tutorial coverage: per audience tree (target: every tree has ≥1 tutorial).
  • Customer NPS: measured via docs feedback issues (target: ≥40 trailing-quarter).

4. Delegation

The Delegation value stream grows the ecosystem's ability to accept downstream contributions — plugins, vocabulary providers, vertical packs, and patent claims — without FCC core becoming a bottleneck. The audience is plugin authors, vertical-pack authors, patent counsel, and partner projects that want to contribute back. Value is delivered as a stable, well-documented extensibility surface: a predictable plugin ABC, a versioned vocabulary-mapping contract, a patent-delegation protocol that moves IP authority cleanly across sister projects (PHOENIX becomes the ecosystem-wide IP home in PE-007), and a contributor onboarding path that doesn't require FCC core commit rights to add value. Portfolio epics carried here include patent delegation (PE-007). All three ARTs contribute, with Framework ART owning plugin-contract stability, Ecosystem ART owning vocabulary-provider health, and Docs ART owning contributor-onboarding material.

KPIs

  • Throughput: externally authored plugin releases per PI (target: ≥3 per PI as the community grows).
  • Lead time: external-PR-opened to external-PR-merged median (target: ≤14 days for plugin contributions).
  • Quality gate pass rate: plugin-contract gate QG-PLUGIN-001 (target: 100%).
  • External plugin count: currently 12 VocabularyProviderPlugins (target: ≥20 by v1.5.0).
  • Vertical pack count: currently 6 (healthcare/finance/legal/insurance/energy/government); target: ≥8 by v1.5.0 including two community-authored packs.
  • Patent-claim inventory: provisional + utility claims across sister projects (target: 20+32 preserved in FCC; growing in PHOENIX).
  • Customer NPS: measured via contributor survey (target: ≥40 trailing-quarter, with emphasis on plugin authors).