Skip to content

Ecosystem Alignment Status

This page tracks the sibling projects that co-evolve with the FCC framework. Every row is a live link between FCC and an external repository, an external team, or an external compliance surface. Keeping this page up to date matters because the VocabularyProviderPlugin pattern means FCC's vocabulary mappings are the contract surface — when a sibling bumps its schema, FCC needs to know, and when FCC ships a new plugin-type, the siblings need to know.

Last refreshed: 2026-06-18, FCC v1.9.0 ecosystem re-sync (full 7-repo forensic sweep). Review cadence: once per FCC patch that adds or removes a plugin type, and on every ecosystem re-sync arc.

Ecosystem Topology Diagram (C4 Level 1)

System-context view of the FCC ecosystem. FCC is the framework at the center; eleven project siblings + ten constellation verticals + three JV libraries orbit it. Two authority roles exist upstream — Research Center (NEXUS) owns coordination + the authoritative port + inventory registries (and is the sole R-CPV vocabulary-insights authority); PHOENIX owns the 61-gate quality registry + patent IP consolidation + open-science validation (the three-pillar authority role: quality-gate, patent-IP, and open-science validation over the 13 OPEN-SCI templates and per-codename patent subtrees). Solid boxes ship today; dashed-border boxes (LYRA live backend) are tracked but not yet published.

flowchart TB
    %% ---------- External actors ----------
    User([Framework adopter<br/>installs fcc · runs scenarios])
    Ops([SRE / Ops<br/>reads telemetry · admin UI])
    Browser([UX consumer<br/>Sky Parlour browser])

    %% ---------- Authorities (upstream) ----------
    subgraph Authorities["Authorities (upstream)"]
        direction LR
        NEXUS["NEXUS (Research Center) v6.2.0<br/>ecosystem_projects.yaml · port_allocation.yaml<br/>R-CPV authority · coordination · ADRs"]
        PHOENIX["PHOENIX (AI-COE-Docs) v6.2.0<br/>61-gate quality registry<br/>patent IP consolidation<br/>open-science validation"]
    end

    %% ---------- Framework ----------
    subgraph Framework["Framework (this repo)"]
        FCC["FCC v1.9.0<br/>149 personas · R.I.S.C.E.A.R.<br/>plugin system · governance"]
    end

    %% ---------- Tier 1/2 Projects ----------
    subgraph Projects["Project siblings (11)"]
        direction TB
        AURORA["AURORA / Sky Parlour v3.3.0<br/>UX portal :2000 · trace viewer"]
        AOME["AOME / CRUCIBLE v4.16.0<br/>React admin · forensic auditor"]
        CONSTEL["CONSTEL / PRISM v13.0.0<br/>classification GraphQL · codename registry"]
        PAOM["PAOM / SENTINEL v4.3.0<br/>runs FCC personas as live agents · MCP :3201"]
        DISTILLER["DISTILLER / FORNAX<br/>vocabulary harvester"]
        CTO["CTO<br/>telecom ontology"]
        POLARIS["POLARIS / ice_ext<br/>long-term archive"]
        LYRA["LYRA<br/>graph-of-thought"]
        P1["p1<br/>event-capture (Tier 4)"]
        DISTROHUB["l2_distro_hub_ext<br/>release artifacts"]
    end

    %% ---------- JV Libraries ----------
    subgraph JVLibs["JV Libraries (3)"]
        direction LR
        ATHENIUM["ATHENIUM<br/>analytics JV (8500)"]
        MNEMOSYNE["MNEMOSYNE<br/>memory JV (8510)"]
        DISTILLERJV["DISTILLER lib surface<br/>vocabulary-provider plugin"]
    end

    %% ---------- Constellation verticals ----------
    subgraph Constel["Constellation verticals (10) · ports 39xx (ADR-020)"]
        direction LR
        OPH[Ophiuchus<br/>medical ontology]
        SER[Serpens<br/>medical metadata]
        LIB[Libra<br/>finance ontology]
        CRA[Crater<br/>finance metadata]
        SCU[Scutum<br/>insurance ontology]
        NOR[Norma<br/>insurance metadata]
        PYX[Pyxis<br/>energy ontology]
        VEL[Vela<br/>energy metadata]
        COL[Columba<br/>gov ontology]
        CAE[Caelum<br/>gov metadata]
    end

    %% ---------- Wires ----------
    User -->|pip install fcc| FCC
    Browser -->|REST · WS| AURORA
    Ops -->|admin API 8900| FCC

    NEXUS -->|vendored SHA256| FCC
    PHOENIX -->|vendored gate registry| FCC

    FCC -->|plugin ABCs| Projects
    FCC -->|vocabulary_providers| Constel
    FCC -->|library consumers| JVLibs

    AURORA <-->|WS events 8765| FCC
    PAOM <-->|MCP + A2A| FCC
    AOME <-->|WS admin| FCC
    CONSTEL -->|codename issuance| FCC

    POLARIS -->|archive-id push| FCC
    LYRA -.->|graph-of-thought query| FCC

    classDef future fill:#e8f1fd,stroke:#5b7ff4,stroke-dasharray:4
    class LYRA future

Legend: - Solid box: shipped / live today. - Dashed-border box: future-tense (LYRA live backend pending; mock bridge ships today). - Solid arrow: live contract. - Dotted arrow: sentinel-guarded (fallback to mock when service absent).

Invariants: - FCC holds the authoritative persona catalog + R.I.S.C.E.A.R. spec; every sibling consumes, none overrides. - NEXUS is the single source of truth for port-allocation + ecosystem inventory (mirrored into src/fcc/data/ecosystem/ with SHA-256 drift gate). - PHOENIX (v6.2.0) is the three-pillar authority — single source of truth for (1) quality gates, (2) patent IP consolidation, and (3) open-science validation. FCC vendors the 61-gate registry (28 core + 15 plugin + 15 compliance + 3 NEXUS v1.8.0 governance gates) and consumes the 13 OPEN-SCI templates for FAIR-workflow + reproducibility-manifest validation; OSC (Open-Science Curator) persona enforces PHOENIX's open-science discipline during forensic audits. - Every bridge (POLARIS, LYRA, Distiller) is availability-sentinel-guarded — FCC always runs hermetic even when the live backend is absent. - JV libraries publish fcc.vocabulary_providers entry points; they never reverse-import FCC at runtime.

Source: src/fcc/data/ecosystem/ecosystem_projects.yaml, src/fcc/data/ecosystem/port_allocation.yaml, src/fcc/federation/namespace.py.

Tier Pyramid Diagram

Three-tier structural view of the ecosystem. Framework at the apex (single); eleven projects at the middle tier; thirteen constellations and JV libraries at the foundation. The two authorities (RC + PHOENIX) sit to the side — not in the hierarchy, but stamping every tier with their respective contracts (port/inventory + R-CPV for RC; quality gate + patent + open-science validation for PHOENIX). PHOENIX's open-science pillar extends its contract across the whole ecosystem via the 13 OPEN-SCI templates and the open_science_refs declarations on every persona.

flowchart TD
    subgraph Apex["Tier 0 — Framework (1)"]
        FCC[FCC<br/>this repo · v1.9.0]
    end

    subgraph Middle["Tier 1/2/3 — Projects (11)"]
        direction LR
        AURORA2[AURORA]
        AOME2[AOME]
        CONSTEL2[CONSTEL]
        PAOM2[PAOM]
        DIST2[DISTILLER]
        CTO2[CTO]
        NEXUS2[NEXUS]
        PHOENIX2[PHOENIX]
        POLARIS2[POLARIS]
        LYRA2[LYRA]
        P1_2[p1]
    end

    subgraph Base["Foundation — Constellations + JV Libraries (13)"]
        direction LR
        subgraph CLane["10 constellation verticals"]
            direction LR
            OPH2[Ophiuchus]
            SER2[Serpens]
            LIB2[Libra]
            CRA2[Crater]
            SCU2[Scutum]
            NOR2[Norma]
            PYX2[Pyxis]
            VEL2[Vela]
            COL2[Columba]
            CAE2[Caelum]
        end
        subgraph JVLane["3 JV libraries"]
            direction LR
            ATH2[ATHENIUM]
            MNEM2[MNEMOSYNE]
            DISTJV2[DISTILLER-lib]
        end
    end

    subgraph Authorities2["Authority side-strip"]
        direction TB
        NEX_AUTH[NEXUS<br/>coordination authority]
        PHX_AUTH[PHOENIX<br/>quality-gate + open-science<br/>validation authority]
    end

    FCC --> Middle
    Middle --> Base

    NEX_AUTH -.->|port + inventory contract| Apex
    NEX_AUTH -.->|port + inventory contract| Middle
    NEX_AUTH -.->|port + inventory contract| Base

    PHX_AUTH -.->|quality gate + patent + open-science contract| Apex
    PHX_AUTH -.->|quality gate + patent + open-science contract| Middle
    PHX_AUTH -.->|open-science validation contract| Base

    classDef authority fill:#fef8e6,stroke:#d4a017
    class NEX_AUTH,PHX_AUTH authority

Invariants: - Tier 0 (FCC) is a singleton — there is exactly one framework. - Tier 1/2/3 projects are the eleven sibling ecosystems; each has its own SemVer line and can release independently. - The foundation (constellations + JV libraries) must never reverse-import FCC at runtime; they declare fcc.vocabulary_providers entry points instead. - Authorities (RC + PHOENIX) are cross-cutting — they don't own tier rows; they stamp contracts across all three tiers. - Tier promotions (e.g., NEXUS from Tier 3 → Producer) require an ADR and a minor-version bump.

Source: docs/ecosystem/codename-decoder.md, src/fcc/federation/namespace.py.

Authoritative registries (vendored)

FCC vendors the authoritative ecosystem registries from the Research Center (NEXUS) repo under src/fcc/data/ecosystem/. The v1.9.0 ecosystem re-sync re-vendored them against NEXUS v6.2.0:

  • port_allocation.yaml — file v3.0.0 (NEXUS v6.2.0, ADR-020): adds tier3_cutover (the 39xx block is now authoritative; 8/10 constellations migrated), shifts RC ports into the [2400, 2599] band (2430 gateway / 2440), and adds the env_slots grid. (FCC v1.9.0 re-vendor; was file v2.0.0/ADR-007.)
  • ecosystem_projects.yaml — file v2.3.0 (NEXUS v6.2.0): bumps the inventory 22 → 23 projects, adds AURORA as a tracked row, and introduces the tier2_conforming tier. (FCC v1.9.0 re-vendor; was file v2.1.0.)

Vendored-registry bump history

Re-vendor port_allocation.yaml ecosystem_projects.yaml ux_rest_openapi Source tag
FCC v1.3.5.4 v2.0.0 (ADR-007, 8600 block) v2.0.0 (19 projects) — RC v2.0.0
FCC v1.8.2 v3.0.0 (ADR-020) v2.1.0 — RC v3.4.0
FCC v1.9.0 v3.0.0 (ADR-020, 39xx authoritative) v2.3.0 (23 projects, +AURORA) RC v6.0.0 NEXUS v6.2.0

A CI contract test (tests/test_ecosystem_registry_drift.py) pins both files by SHA256 and, when the RC repo is checked out locally, compares byte-for-byte against its canonical sources. The vendored copies drive FCC's own displays of the 23-project reporting registry — see the snapshot below.

Snapshot (as of NEXUS v6.2.0 / PHOENIX v6.2.0 / PAOM v4.3.0, 2026-06-18)

Versions and live-port reality below come from the 2026-06-18 7-repo forensic sweep. Live-probe results that day: RC :2430, AOME :3100, PAOM :3210, CONSTEL :8100, CTO :2810, AURORA :2000 all answering; PHOENIX has no always-on daemon; FCC's own service ports are not yet stood up (that lands in Phase 2 of the re-sync).

Project Codename Path (local) FCC tier FCC alignment Live port (2026-06-18)
PAOM SENTINEL .../Ideate/paom Tier 2 (Active) v4.3.0 "Helmsman" — now runs FCC personas as live agents via its PAOM-pull adapter (fcc_ingest.py, transport B); HEAD on PI-11 (FCC agent-spec handoff) :3210 (health) / :3201 (A2A+MCP)
AOME CRUCIBLE .../Ideate/aome_ext Tier 1 (Strict) v4.16.0 — UAT gold standard; React admin UI + forensic auditor; 3,845 tests at 96.96% :3100
CONSTEL PRISM .../Ideate/constel_ext Tier 1 (Strict) v13.0.0 — classification GraphQL authority (ADR-034 D4 / ADR-032 subordinate to NEXUS); 51 MCP tools :8100
CTO CTO .../Ideate/attic_om_poc/cto Tier 3 (Minimal) v14.0.0 — UAT + vision; 13 web-MCP tools; bridge surface unchanged :2810
Sky-Parlour AURORA .../Ideate/sky-parlour_poc/sky-parlour Tier 1 (Strict) v3.3.0 "portal-wiring" — UX portal + trace viewer :2000 (api /api/v1/health) / :2010 SPA
Research Center NEXUS .../Ideate/research_center_ext Tier 3 (Minimal, promotion to Producer staged) v6.2.0 — RC-MP-21 Contribution Intelligence; authoritative port + inventory + R-CPV registry :2430 (gateway; R-CPV insights only under make uat-serve)
AI-COE-Docs PHOENIX .../Ideate/ai-coe-docs Tier 2 (Active) v6.2.0 — 61-gate quality-gate + patent-IP + open-science validation authority (three-pillar role); 13 OPEN-SCI templates; EIF construct freeze no always-on daemon
distiller_ex FORNAX .../crucible/distiller_ex Tier 2 (Active) vocabulary distillation, 96% coverage, 1,781 backend tests 8002 + 5175
p1 — .../crucible/p1 Tier 4 (Autonomous) no FCC coupling yet; Phase E future integration via @crucible/shared-ui n/a
l2_distro_hub_ext — .../crucible/l2_distro_hub_ext Tier 4 (None) distribution hub, no runtime FCC coupling n/a
Athenium ATHENIUM .../crucible/L2/l2_athenium Tier 2 (JV partner, L2 library) v0.3.0 — pinned fcc>=1.2.1 (bump staged with Athenium team) 8500 (library_only)
Mnemosyne MNEMOSYNE .../crucible/L2/l2_mnemosyne Tier 2 (JV partner, L2 library) unreleased (dynamic) — pinned fcc>=1.2.1 (bump staged) 8510 (library_only)

Inventory reconciliation: NEXUS's ecosystem_projects.yaml (file v2.3.0, vendored at FCC v1.9.0) tracks 23 projects across its tiers (ecosystem partners + JV partners + 10 vocabulary/constellation projects), now including AURORA as a first-class tracked row. The 10 constellation codenames (Ophiuchus, Serpens, Libra, Crater, Scutum, Norma, Pyxis, Vela, Columba, Caelum) live as plugins/fcc-*-plugin/ in this repo and are also published as independent public repos (v1.4.0). Their FastAPI ports have moved to the 39xx block (39{vertical*10 + role}) per the RC ADR-020 tier-3 cutover (8/10 migrated). The legacy 86xx range is tolerated until 2026-Q3 for in-flight consumers, after which it is retired.

AURORA tracking resolved: earlier alignment notes flagged that RC's ecosystem_projects.yaml did not list AURORA. As of file v2.3.0 (NEXUS v6.2.0) AURORA is a tracked row; the upstream gap is closed.

Published constellation repos (new in v1.4.0)

As of FCC v1.4.0 (2026-04-22), all 10 constellation vertical projects are published as independent public GitHub repositories at v0.2.0, signaling FCC v1.4.0 alignment:

Codename Vertical Repository Standard(s)
Ophiuchus medical ontology ophiuchus_ext HL7 FHIR Genomics IG + DICOM PS3 + IEC 62304
Serpens medical metadata serpens_ext ICH E2B(R3) ICSR + EudraVigilance
Libra financial ontology libra_ext FIBO (EDM Council)
Crater financial metadata crater_ext ISO 20022 + BCBS 239 + SR 11-7
Scutum insurance ontology scutum_ext ACORD Reference Architecture v2.11
Norma insurance metadata norma_ext Solvency II Art. 44 + IFRS 17 CSM
Pyxis energy ontology pyxis_ext IEC 61970 CIM
Vela energy metadata vela_ext IEC 62325 + ENTSO-E CGMES + IEEE 1547
Columba government ontology columba_ext DCAT-US 3.0
Caelum government metadata caelum_ext NIEM 6.0 + eIDAS 2.0

Each repo carries the full public-release package from v1.3.11 scaffolding: CODE_OF_CONDUCT (Contributor Covenant 2.1), CONTRIBUTING, SECURITY, MIT LICENSE, GitHub Actions CI + release workflows, issue + PR templates, release-checklist runbook. Ports now follow the RC ADR-020 39xx block (39{vertical*10 + role}; e.g. Ophiuchus FastAPI 3900), superseding the legacy 86xx range (tolerated until 2026-Q3). All 10 map to the corresponding plugins/fcc-<codename>-plugin/ vocabulary provider inside FCC.

FCC adoption tier definitions

  • Tier 1 (Strict) — pre-commit validation against FCC schemas; breaking a contract fails CI. Used by CONSTEL, AOME, Sky-Parlour.
  • Tier 2 (Active) — regular FCC alignment releases; FCC version is pinned and bumped deliberately. Used by PAOM, distiller_ex, AI-COE-Docs.
  • Tier 3 (Minimal) — FCC is referenced but not enforced; the project can run without FCC installed. Used by CTO, Research Center.
  • Tier 4 (Autonomous) — no runtime FCC coupling; may share concepts but operates independently. Used by p1, l2_distro_hub_ext.

Vocabulary-provider plugin status (12 plugins as of v1.3.5.2)

The VocabularyProviderPlugin is the canonical runtime hook. Each plugin declares a namespace and a class_map that FCC verifies against its bundled src/fcc/data/objectmodel/{namespace}_vocabulary_mappings.yaml.

Namespace Plugin package Covers Mapping count
athenium fcc-athenium-plugin Athenium ecosystem classes see athenium_vocabulary_mappings.yaml
mnemosyne fcc-mnemosyne-plugin Mnemosyne ecosystem classes see mnemosyne_vocabulary_mappings.yaml
caelum fcc-caelum-plugin Government metadata (constellation code name) see YAML
columba fcc-columba-plugin Government ontology see YAML
crater fcc-crater-plugin Financial metadata see YAML
libra fcc-libra-plugin Financial ontology see YAML
norma fcc-norma-plugin Registry ontology see YAML
ophiuchus fcc-ophiuchus-plugin Knowledge base see YAML
pyxis fcc-pyxis-plugin Navigation ontology see YAML
scutum fcc-scutum-plugin Defense terminology see YAML
serpens fcc-serpens-plugin Data structures see YAML
vela fcc-vela-plugin Astrophysics vocabulary see YAML

The 12 plugin packages live under plugins/ in the FCC repo. Sister projects (PAOM, AOME, CTO, Sky-Parlour, distiller_ex) remain pure-data dataclass libraries with no FCC dependency; they publish their shapes, and FCC's vocabulary mappings describe the crosswalks. This is the VocabularyProviderPlugin pattern.

Port assignments (conflict-resolved)

Live-probe reality from the 2026-06-18 sweep (authoritative source is the vendored port_allocation.yaml file v3.0.0):

Port Owner Role (2026-06-18)
2000 / 2010 AURORA (Sky Parlour) UX portal api (/api/v1/health) / SPA — answering
2430 / 2440 NEXUS (Research Center) gateway (R-CPV insights only under make uat-serve) — answering
2810 CTO web-MCP (13 tools) — answering
3100 AOME MCP/A2A — answering
3201 / 3210 PAOM A2A+MCP (3201) / health (3210) — answering
8100 CONSTEL API / classification GraphQL (51 MCP tools) — answering
39xx Constellation verticals 39{vertical*10 + role} (ADR-020; 86xx tolerated until 2026-Q3)
8765 FCC backend WebSocket bridge live event stream (Phase 2 — not yet stood up)
8002 + 5175 distiller_ex backend API + Event Viewer
(none) PHOENIX no always-on daemon

Per-project integration notes

PAOM

Most mature consumer. At v4.3.0 ("Helmsman") PAOM runs FCC personas as live agents via its PAOM-pull adapter (src/paom/integrations/ fcc_ingest.py, "transport B") — it reads FCC's R.I.S.C.E.A.R. persona YAML directly via PAOM_FCC_ROOT with zero FCC code change. PAOM's HEAD carries PI-11, the FCC agent-spec handoff. PAOM derives the 8-value archetype enum and reads doc_context.constitution as authoritative; a persona missing constitution.hard_stop is rejected as non-runnable (a Phase 3 FCC data dependency). The contract doc coordination/paom-sentinel-coordination.md lands in Phase 3.

AOME

Privacy taxonomy and the most test-heavy sibling, now the ecosystem's UAT gold standard. Tier 1: AOME fails its own CI if any FCC-imposed schema check breaks. v4.16.0 ships 3,845 tests at 96.96% coverage and governs vision-diff review by USD budget ($0.10/PR, $5/mo) rather than recall/FP.

CONSTEL

Owns constellation code name assignment — whenever FCC scaffolds a new vertical project, CONSTEL hands out the next name from its registry. At v13.0.0 CONSTEL is the classification GraphQL authority only (ADR-034 D4: PAOM owns persona/R.I.S.C.E.A.R. GraphQL, CONSTEL owns classification); CONSTEL ADR-032 explicitly subordinates its codename authority to NEXUS/RC. 51 MCP tools; pre-commit validation runs against FCC plugin ABCs.

CTO

Telecom ontology. Tier 3 — the relationship is conceptual rather than enforced. v14.0.0 (UAT + vision), live on :2810 with 13 web-MCP tools; the FCC bridge surface is unchanged. CTO computes a worked R-CPV value (cto.ecosystem.rcpv=5851). Note: CTO has a conformance drift guard on FCC's EventSubscriberPlugin ABC (exactly 2 abstract methods) — that ABC is frozen so CTO CI does not break.

Sky-Parlour

Tier 1. At v3.3.0 ("portal-wiring") the UX portal answers on :2000 (/api/v1/health) with the SPA on :2010. AURORA mirrors FCC's 37 canonical archetypes and coins none of its own; near-term federation is greenfield (portal-component-v1 / ADR-026 fixture+types+route, AOME leads portal UX, WCAG 2.2 AA is a hard gate). The v1.3.5.2 skyparlour-v1352-addendum.md demo integrates Sky-Parlour's context enricher with the FCC event bus.

Research Center

NEXUS v6.2.0 — the authoritative source for ecosystem_projects.yaml, port_allocation.yaml, and the R-CPV (Research Corpus Parity Value) vocabulary-insights endpoint. RC-MP-21 added Contribution Intelligence (contributions/, ADR-067). RC is the sole R-CPV authority: its GET /v1/kb/vocabulary/insights endpoint is the canonical corpus-parity source (served only under make uat-serve, not on the bare :2430 gateway). See rcpv-reconciliation-baseline.md. Stats toolkit is used for cross-project coverage analysis but is not an FCC plugin.

AI-COE-Docs

PHOENIX v6.2.0 — the three-pillar authority for the ecosystem: (1) 61-gate quality registry (28 core + 15 plugin + 15 compliance + 3 NEXUS v1.8.0 governance gates; vendored into FCC with SHA256 drift sentinel); (2) patent-IP consolidation (consumed by FCC through the IHL + PCT personas; QG-IP-CONS is now a HARD gate on docs/patent/); and (3) open-science validation authority across the 13 OPEN-SCI templates (now including agent-card, peer-review-results, open-access-compliance) and every persona's open_science_refs declaration. No always-on daemon. Consumer of FCC's open-science persona pack; OSC (Open-Science Curator) persona enforces PHOENIX's open-science discipline during FCC forensic audits.

distiller_ex (Fornax)

Vocabulary distillation engine. The v1.3.5.2 distiller-bridge-v1352-addendum.md demo walks through the NanoCube vocabulary-evolution scenario — when Fornax ships a schema update, FCC detects the added/removed class ids through VocabularyMappingLoader.verify_against_plugin() and can drive a reconciliation.

p1

Autonomous event-capture layer (Tier 4, 1,077+ tests). Descended from Sky-Parlour's prototypes/ui/. A future Phase E integration via @crucible/shared-ui is planned but not scheduled. FCC does not depend on p1; p1 does not depend on FCC.

l2_distro_hub_ext

Release distribution hub. Holds release artifacts for the crucible ecosystem. No runtime coupling to FCC.

How to refresh this page

  1. git log -1 --format='%h %s' in each project directory to get the latest commit; paste into the table.
  2. Check each project's pyproject.toml or package metadata for the declared FCC alignment version (if any).
  3. Run python3 -c "from fcc.plugins import registry; [print(p.plugin_meta().id) for p in registry.discover('vocabulary_providers')]" to confirm the 12 plugin packages are still installed and importable.
  4. Update the "Last refreshed" date at the top.

See also