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-04-22 as part of the v1.3.5.4 release. Review cadence: once per FCC patch that adds or removes a plugin type.

Authoritative registries (vendored)

FCC v1.3.5.4 vendors the authoritative ecosystem registries from the Research Center (NEXUS) repo under src/fcc/data/ecosystem/:

  • port_allocation.yaml — [RC v2.0.0, 2026-04-21, ADR-007]
  • ecosystem_projects.yaml — [RC v2.0.0, 2026-04-21, RC-MP-01 F-006]

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 19-project reporting registry — see the snapshot below.

Snapshot (as of RC v2.1.0 / PHOENIX v4.0.0 / PAOM v3.2.0)

Project Codename Path (local) FCC tier FCC alignment Ports
PAOM SENTINEL .../Ideate/paom Tier 2 (Active) v3.2.0 — v1.3.3 alignment; v1.4.0 readiness in progress 9001 (MCP) + 9010-9013
AOME CRUCIBLE .../Ideate/aome_ext Tier 1 (Strict) v2.7.0 — RT-15 in flight; React admin UI + forensic auditor + 118 diagrams 3100 (MCP/A2A)
CONSTEL PRISM .../Ideate/constel_ext Tier 1 (Strict) v6.0.0 — RT-14 federation v2; JWT CLI admin + CTO drift detection + 92 diagrams 3400 (MCP/A2A, migrated from 3200 per RC AD-005)
CTO CTO .../Ideate/attic_om_poc/cto Tier 3 (Minimal) v5.1.0 + RT-3.2 tutorials 8000
Sky-Parlour AURORA .../Ideate/sky-parlour_poc/sky-parlour Tier 1 (Strict) v0.8.0, Phase 17 context enricher 3001 + 5173 + 8300-8399 (reserved)
Research Center NEXUS .../Ideate/research_center_ext Tier 3 (Minimal, promotion to Producer staged) v2.1.0 — PI-2026-Q2 close; authoritative port + inventory registry 3200 (MCP) + 3300 (A2A) + 3301 (UX gateway)
AI-COE-Docs PHOENIX .../Ideate/ai-coe-docs Tier 2 (Active) v4.0.0 — 58-gate quality registry + 12 open-science templates + patent-eval pipeline 8200 (A2A agent)
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 (new in v1.3.5.4) ATHENIUM .../crucible/L2/l2_athenium Tier 2 (JV partner, L2 library) v0.3.0 — pinned fcc>=1.2.1 (bump to >=1.3.5.4 staged with Athenium team) 8500 (library_only)
Mnemosyne (new in v1.3.5.4) 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: RC's ecosystem_projects.yaml v2.0.0 tracks 19 projects in 3 tiers (7 ecosystem partners + 2 JV partners + 10 vocabulary/constellation projects). FCC surfaces the same 19 plus 3 additional FCC-peripheral projects (Sky-Parlour, p1, l2_distro_hub_ext) that RC tracks via port_allocation.yaml or not at all. The 10 constellation codenames (Ophiuchus, Serpens, Libra, Crater, Scutum, Norma, Pyxis, Vela, Columba, Caelum) live as plugins/fcc-*-plugin/ in this repo today and are scheduled to become independent GitHub repos in v1.4.0 (Pillar 1). Their FastAPI ports shifted from 8300-8341 → 8600-8641 on 2026-04-21 (RC ADR-007) to preserve AURORA's reserved 8300-8399 range.

Known upstream gap: RC's ecosystem_projects.yaml does not yet list AURORA (Sky Parlour) even though port_allocation.yaml reserves its ports. Flagged upstream via the v1.3.5.4 coordination note. FCC's own alignment page carries AURORA explicitly so downstream tooling can discover it regardless.

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)

Port range Owner Role
8765 FCC backend WebSocket bridge live event stream for frontend
5173 distiller_ex frontend (Vite default); Sky-Parlour frontend both use default Vite
5174–5177 p1 event-capture UIs parlor-ui + flowX
8001 AOME FastAPI server
8002 distiller_ex backend API
8100 AOME MCP server (moved from 8002 after conflict)
8100 CONSTEL API (overlaps with AOME — distinct hosts)
8200/8201/8270/8271 AI-COE-Docs patent-eval + open-science surfaces
9000–9099 PAOM Ollama-facing MCP tool range
3300 Research Center stats toolkit
3001 p1 event-capture backend

Per-project integration notes

PAOM

Most mature consumer. Each FCC release gets a follow-up "FCC vN.N.N Alignment Release Train" from PAOM. Current state: on v1.3.3 alignment; v1.3.5 alignment pending on FCC side. PAOM pulls FCC's tag registry, quality gates, and vocabulary mappings at build time.

AOME

Privacy taxonomy (1,026 nodes) and the most test-heavy sibling. Tier 1: AOME fails its own CI if any FCC-imposed schema check breaks. v1.5.0 shipped 3,990 tests at 97.60% coverage.

CONSTEL

Owns constellation code name assignment — whenever FCC scaffolds a new vertical project, CONSTEL hands out the next name from its registry. v0.2.0 pre-commit validation runs against FCC plugin ABCs.

CTO

Telecom ontology, 1,520 concepts. Tier 3 — the relationship is conceptual rather than enforced. CTO's RT-3.2 tutorials (52 of them) reference FCC patterns as teaching examples but do not depend on FCC at runtime.

Sky-Parlour

Tier 1 with 218 canonical workflows. Currently at Phase 17 (context enricher). The v1.3.5.2 skyparlour-v1352-addendum.md demo integrates Sky-Parlour's new context enricher with the FCC event bus.

Research Center

Assigns constellation code names for new vertical scaffolds. Stats toolkit is used for cross-project coverage analysis but is not an FCC plugin.

AI-COE-Docs

Patent evaluation + open-science specifications surface. 141 artifacts. Consumer of FCC's open-science persona pack.

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