Skip to content

FCC Ecosystem Documentation

New in v1.7.1. The Tri-Authority Topology doc is now the canonical overview of how FCC coordinates with the three ecosystem authorities — NEXUS (research + JV), PHOENIX (open science + quality gates + patent IP), and ORCHESTRA (public cross-repo contract tests). Per-authority coordination records live under coordination/.

New in v1.6.1. This page is the entry point to the docs/ecosystem/ section. It indexes the operational references that collectively describe how FCC coordinates with its 22+ sibling projects — what each codename means, which services cross repo boundaries, how the canonical seed-data pipeline flows license metadata across the tree, and how FCC hands off work to the Research Center (NEXUS), ice_ext (POLARIS), ai-coe_ext (PHOENIX), and the 10 constellation vocabulary packs.

FCC is the framework owner for the R.I.S.C.E.A.R. specification, the Find → Create → Critique workflow graph, and the plugin-ecosystem ABCs. Every other project in the ecosystem is either a consumer (PAOM, AOME, CONSTEL, Sky Parlour / AURORA), an authority for a cross-cutting concern (the tri-authority model identifies NEXUS for research + JV statistics, PHOENIX for open science + quality gates + patent IP, and ORCHESTRA for public cross-repo contract tests), or a vertical plugin (the 10 constellation codenames carry per-industry vocabulary mappings). Reading these documents end-to-end takes roughly 50 minutes and gives you the operational map of the entire ecosystem.

Who is this for?

  • New to the ecosystem? Start with the Codename Decoder — it is the reference card that turns unfamiliar codenames (PHOENIX, POLARIS, LYRA, AURORA, ATHENIUM, MNEMOSYNE, DISTILLER, and the 10 constellations) into concrete projects with GitHub URLs and local clone paths.
  • Developer integrating a sibling project? Read Universal Services. It is the 22-entry coordination superset covering which services FCC exposes, which services FCC consumes, and which services are shared across three or more projects.
  • Operations / SRE? Start with Alignment Status. It documents the three-tier project registry (Core Framework, JV L2, Constellation Vocabulary Packs), per-tier responsibilities, and which project owns each port allocation.
  • Compliance / counsel? Read Seed-Canonical License Notices first — it covers the Pillar A license terms that propagate through src/fcc/data/seed/ and the ATTRIBUTION.md manifest shipped in v1.6.0. Then dive into ICE-EXT Patent Coordination for patent-delegation specifics.
  • Coordinating with the Research Center (NEXUS)? Read RC Coordination Record. It is the canonical handoff playbook covering FCC ↔ NEXUS statistics reporting, industry-paper draft coordination, and the two outstanding owner-approval-gated cross-repo PRs.
  • Patent reviewers? Read ICE-EXT Patent Coordination + the top-level docs/patent/ tree. FCC carries the counsel-gated draft package (20 provisional + 32 utility claims) while POLARIS (ice_ext) owns the downstream FTO coordination.

Document index

Document What it covers Length
Tri-Authority Topology Canonical overview of how FCC coordinates with NEXUS, PHOENIX, and ORCHESTRA. Hub-and-spoke diagram, PI cadence comparison, invariants. New in v1.7.1. ~13 KB
Coordination Records Per-authority handoff playbooks (NEXUS research, PHOENIX open science, ORCHESTRA integration tests). Shared record template for new coordination lanes. ~3-8 KB each
Codename Decoder Codename → full name + origin reasoning + GitHub URL + local clone path for every ecosystem project. Quick-lookup table + detailed sections. ~25 KB
Alignment Status 19-project registry, three-tier classification, per-tier responsibilities, ecosystem topology diagram, port allocations. ~13 KB
Universal Services 22-entry service-coordination superset. Who exposes what, who consumes what, shared-service contracts. ~14 KB
Seed-Canonical License Notices Pillar A license terms (v1.6.0) for the 10 canonical seed corpora across 5 verticals. Per-corpus attribution + SHA256 manifest pointer. ~10 KB
RC Coordination Record FCC ↔ Research Center (NEXUS) handoff playbook. Statistics reporting, industry-paper drafts, owner-approval-gated PRs. ~7 KB
ICE-EXT Patent Coordination FCC ↔ ice_ext (POLARIS) patent-delegation coordination. FTO flow, counsel-gate enforcement. ~7 KB

Ecosystem topology

The canonical ecosystem topology diagram lives alongside the alignment-status reference — see alignment-status.md#ecosystem-topology for the C4-style container view. That diagram shows FCC at the center, PHOENIX / NEXUS / POLARIS / LYRA at the tier-1 peer authority ring, AURORA / AOME / PAOM / CONSTEL at the tier-2 consumer ring, and the 10 constellation vocabulary packs at the outer plugin ring. The tier-pyramid companion diagram in the same file gives the vertical view.

For per-bridge internal diagrams (POLARIS, LYRA, GraphRAG+Zachman, CRDT multi-user, bidirectional federation, six-pillars overview), see the docs/architecture/class-diagrams/ and docs/architecture/sequence-diagrams/ trees indexed under Architecture → v1.5.0 Pillars in the site navigation.

How this ecosystem coordinates

  • FCC owns the framework. The R.I.S.C.E.A.R. specification, persona registry, workflow graph, plugin ABCs, and event-bus contracts live here. Every consumer project binds to FCC via the VocabularyProviderPlugin pattern — sister projects remain pure-data libraries with no FCC dependency; FCC ships the plugin adapters in src/fcc/plugins/.
  • PHOENIX (ai-coe_ext) is the quality-gate authority. The 58-gate PHOENIX registry is vendored into FCC at src/fcc/data/governance/quality_gates.yaml and drives fcc audit personas --strict. PHOENIX is also the patent-consolidation target once counsel engagement lands.
  • NEXUS (Research Center) is the coordination + statistics authority. NEXUS owns cross-project metrics aggregation, industry-paper coordination, and the vendored ecosystem registries (src/fcc/data/ecosystem/port_allocation.yaml + ecosystem_projects.yaml) that FCC drift-checks in CI.
  • POLARIS (ice_ext) is the patent/IP authority. FCC holds the counsel-gated draft patent package (20 provisional + 32 utility claims); POLARIS coordinates the downstream FTO work and carries the canonical IP portfolio record.
  • LYRA is the ecosystem-wide attestation bridge. Promoted from mock to live v0.1.0 in v1.6.0, LYRA exposes the attestation service that FCC and sibling projects use to assert workflow-run provenance across ecosystem boundaries.
  • AURORA (Sky Parlour) is the UX gateway. AURORA owns ports 8300–8399 (RC ADR-007) and exposes the /ecosystem-ops page backed by the v1.4.2 dual-bus event architecture.
  • The 10 constellations are vertical vocabulary plugins. Each constellation (Ophiuchus, Serpens, Libra, Crater, Scutum, Norma, Pyxis, Vela, Columba, Caelum) is an independent public GitHub repo at v0.2.0+ with its own release cadence, carrying per-industry vocabulary mappings that FCC consumes via its 12 VocabularyProviderPlugin adapters.

The full 22-entry coordination matrix is tabulated in Universal Services; the authority-chain narrative is elaborated in Alignment Status.