Skip to content

FCC Ecosystem Codename Decoder

The FCC ecosystem uses mythological and astronomical codenames extensively — PHOENIX, POLARIS, AURORA, the ten constellation verticals, and more. This document is the single canonical place to translate any codename you see in source, CHANGELOG entries, ADRs, or sibling-repo commit messages back to its full project name, current status, and the reasoning behind the name.

When you encounter a codename in an FCC artifact that is not listed here, that is a bug — open an issue. When a codename's canonical link changes (new GitHub repo, archived project, renamed module) update the relevant row in the quick lookup table and the per-entry section below.

Authoritative sources consumed to build this document:

  • Context diagram — codename authority for framework/project tier (C4 Level 1).
  • Ecosystem alignment status — tier + status + external repo links.
  • Universal services — bridge-status authority for POLARIS + LYRA + Distiller.
  • CHANGELOG entries v1.3.5.4 through v1.5.0 — constellation port plan and adoption history.

Quick lookup table

The Local path column records the best local clone on the owner's development host at v1.9.0. When a clone is absent for an entry, the cell reads not cloned locally verbatim. Paths are absolute and stable; they are the resolution target for relative-path tooling (e.g. ecosystem-integration-tests conftest).

Codename Full name / Role Tier Status Canonical link Local path
FCC Find → Create → Critique framework (this repo) Framework Stable l2_fcc_agent_team_ext /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/l2_fcc_agent_team_ext
PHOENIX AI-COE-Docs — quality gates + patent IP + open-science validation Project Active (Tier 2) ai-coe_ext /mnt/d/VirtualDataRoom/Technology/Software/Ideate/ai-coe-docs (authoritative)
/mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/ai-coe_ext (staging)
NEXUS Research Center — authoritative registries Project Active (Tier 3, promotion staged) research_center_ext /mnt/d/VirtualDataRoom/Technology/Software/Ideate/research_center_ext (authoritative)
/mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/research_center_ext (staging)
BOREAS ice_ext — long-term model archive (RC ADR-017 registry codename; self-identity ice_ext per ICE ADR-006; ICE #10 silent-ack pending) Project Stable bridge (v1.5.0), archive semantics ice_ext /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/ice_ext
ATLAS l2_siis_ext — SIIS US 11,222,274 B2 Tier-1-Strict consumer (4-pillar cache / NLP / coupling / lifecycle) Project Active (Tier 1; v1.0.0 archival 2026-05-05) l2_siis_ext /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/l2_siis_ext
IRIS l2_iris_ext — US 9,942,398 B2 (AT&T) Tier-1-Strict consumer Project Incubating (pre-alpha v0.9.0.dev1, 230 tests / 95.74% cov) l2_iris_ext /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/l2_iris_ext
LYRA Graph-of-thought + harmonic vocabulary expansion Project v0.1.0 live (private); mock bridge remains default fallback lyra_ext /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/lyra_ext
AURORA Sky Parlour — live trace viewer + UX frontend Project Active (Tier 1) sky-parlour /mnt/d/VirtualDataRoom/Technology/Software/Ideate/sky-parlour_poc/sky-parlour
CONSTEL PRISM — federation v2 + constellation-name registry Project Active (Tier 1) constel_ext /mnt/d/VirtualDataRoom/Technology/Software/Ideate/constel_ext
AOME CRUCIBLE — React admin UI + forensic auditor Project Active (Tier 1) aome_ext /mnt/d/VirtualDataRoom/Technology/Software/Ideate/aome_ext
PAOM SENTINEL — LLM router + budget manager Project Active (Tier 2) paom /mnt/d/VirtualDataRoom/Technology/Software/Ideate/paom
DISTILLER FORNAX — vocabulary distillation engine Project Active (Tier 2) distiller_ex /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/distiller_ex
ATHENIUM Analytics JV L2 library Project Active (Tier 2 JV) l2_athenium /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/l2_athenium
MNEMOSYNE Memory JV L2 library Project Active (Tier 2 JV) l2_mnemosyne /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/l2_mnemosyne
CTO Canonical Tabular Ontology — optional object-model bridge Project Optional dep (Tier 3 — library only) cto /mnt/d/VirtualDataRoom/Technology/Software/Ideate/attic_om_poc/cto
DATALOCK l2_distro_hub_ext — release-asset distribution hub Tooling & Integration Active — audience-bundle releases l2_distro_hub_ext /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/l2_distro_hub_ext
ORCHESTRA ecosystem-integration-tests — cross-repo contract gate Tooling & Integration Active (public) ecosystem-integration-tests /mnt/d/VirtualDataRoom/Technology/Software/Ideate/ecosystem-integration-tests
FLOWX p1 — event-capture + OTel + shared UI backend Tooling & Integration Active p1 /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/p1
Ophiuchus Medical ontology vertical Constellation Vertical v0.2.0 public ophiuchus_ext /mnt/d/VirtualDataRoom/Technology/Software/Ideate/ophiuchus_ext
Serpens Medical metadata vertical (ICSR, pharmacovigilance) Constellation Vertical v0.2.0 public serpens_ext /mnt/d/VirtualDataRoom/Technology/Software/Ideate/serpens_ext
Libra Financial ontology vertical (FIBO) Constellation Vertical v0.2.0 public libra_ext /mnt/d/VirtualDataRoom/Technology/Software/Ideate/libra_ext
Crater Financial metadata vertical (ISO 20022, BCBS 239, SR 11-7) Constellation Vertical v0.2.0 public crater_ext /mnt/d/VirtualDataRoom/Technology/Software/Ideate/crater_ext
Scutum Insurance ontology vertical (ACORD) Constellation Vertical v0.2.0 public scutum_ext /mnt/d/VirtualDataRoom/Technology/Software/Ideate/scutum_ext
Norma Insurance metadata vertical (Solvency II, IFRS 17) Constellation Vertical v0.3.0 public norma_ext /mnt/d/VirtualDataRoom/Technology/Software/Ideate/norma_ext
Pyxis Energy ontology vertical (IEC 61970 CIM) Constellation Vertical v0.2.0 public pyxis_ext /mnt/d/VirtualDataRoom/Technology/Software/Ideate/pyxis_ext
Vela Energy metadata vertical (IEC 62325, CGMES, IEEE 1547) Constellation Vertical v0.2.0 public vela_ext /mnt/d/VirtualDataRoom/Technology/Software/Ideate/vela_ext
Columba Government ontology vertical (DCAT-US 3.0) Constellation Vertical v0.2.0 public columba_ext /mnt/d/VirtualDataRoom/Technology/Software/Ideate/columba_ext
Caelum Government metadata vertical (NIEM 6.0, eIDAS 2.0) Constellation Vertical v0.2.0 public caelum_ext /mnt/d/VirtualDataRoom/Technology/Software/Ideate/caelum_ext

Tier legend. Framework — the FCC framework itself (this repo). Project — a sibling project in the Ideate/crucible monorepo or a published public repo that co-evolves with FCC as a first-class producer/consumer. Constellation Vertical — one of the ten industry-specific vocabulary-provider verticals (v1.4.0 made them independent public repos). Tooling & Integration — support projects that do not themselves ship personas or RISCEA R specs but enable ecosystem operation (release-asset distribution, cross-repo contract gates, event capture / OTel).

Status legend. Stable — production-ready, SemVer 1.x. Active — co-evolving with FCC, contract-tested. Incubating — scaffolded with a mock/sentinel fallback, live backend not yet published. Archive — retained for historical reference only. Mock bridge stable — the bridge protocol + mock backend are stable even though the live backend is not yet available.

Reserved codenames. POLARIS is reserved by FCC for the Find → Create → Critique framework patent disclosure and is not an ecosystem-project codename. It was previously (incorrectly) applied to ice_ext; corrected in v1.8.0. ice_ext's authoritative ecosystem-registry codename is BOREAS (RC ADR-017, RC-side accepted; ICE-side silent-ack pending via ICE issue #10, filed 2026-05-09). ICE retains the self-identity ice_ext per ICE ADR-006. If ICE counter-rejects, the fallback is the dual-name BOREAS (RC) / ice_ext.

Note on Local-path column. Rows with two paths show (authoritative) — the canonical working location — followed by (staging) — the FCC-side secondary clone used for cross-repo handoff staging work. Single-path rows have only one clone locally. For normal reading of these projects, use the (authoritative) path. The (staging) clones exist to stage PRs before pushing to origin. At v1.7.1, PHOENIX and NEXUS are the two dual-path rows: their authoritative clones live under /mnt/d/VirtualDataRoom/Technology/Software/Ideate/, and their staging clones live alongside FCC under /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/.

Framework & Project Codenames (rollup)

The following 13 entries cover the FCC framework itself and the twelve non-constellation ecosystem projects (including the CTO object-model bridge). Tooling & Integration entries (DATALOCK, ORCHESTRA, FLOWX) appear in a separate rollup below.

FCC

  • Full name / role. Find → Create → Critique Agent Team Framework. The central Python package under src/fcc/ that owns the canonical persona catalog (149 personas), R.I.S.C.E.A.R. spec, workflow graph models, simulation engine, plugin system, and governance surface.
  • Origin reasoning. Acronym-first naming. The three-phase workflow cycle (Find → Create → Critique) drives every scenario: agents find relevant context, create candidate output, then critique the result against discernment + design-target-factor dimensions. The team extension (Agent Team) emphasises multi-persona collaboration over single-agent execution.
  • Tier. Framework (this repo).
  • Status. Stable — v1.9.0 as of 2026-06-18 (ecosystem re-sync).
  • Canonical link. rollingthunderfourtytwo-afk/l2_fcc_agent_team_ext

PHOENIX — ai-coe-docs

  • Full name / role. AI Center of Excellence Documentation Hub. PHOENIX carries three pillars of authority for the FCC ecosystem: (1) the 61-gate quality registry (28 core + 15 plugin + 15 compliance + 3 NEXUS v1.8.0 governance gates) vendored into FCC with a SHA256 drift sentinel; (2) the canonical patent-IP consolidation workflow consumed by FCC via the IHL (Innovation Handoff Liaison) + PCT (Patent Claim Tracer) personas (QG-IP-CONS is now a HARD gate on docs/patent/); and (3) the Open-Science Validation Authority role — PHOENIX reviews and validates the per-codename open-science artifacts produced across the ecosystem against the 13 OPEN-SCI templates (now including agent-card, peer-review-results, open-access-compliance), and enforces cross-project citation discipline through the OSC (Open-Science Curator) persona's forensic audit.
  • Open-Science Validation pillar. PHOENIX is the ecosystem's innovation-center for open-science artifacts: it validates per- codename patent subtrees under docs/patent/ (disclosure, provisional, utility, FTO, prior-art, drawings), vets the open_science_refs declarations on every persona, and certifies that FAIR workflows + reproducibility manifests track back to canonical OPEN-SCI-NNN reference numbers (the EIF construct freeze is its v6.2.0 keystone). When an FCC release extends the open-science surface (new templates, new reference numbers), PHOENIX reviews the additions before they land as authoritative.
  • Origin reasoning. The phoenix is a mythological firebird that cyclically regenerates from its own ashes — the perfect metaphor for a quality-gate surface that continuously rebuilds the docs pipeline each release, for a patent-consolidation hub that regenerates authoritative IP records from cross-repo source evidence, and for an open-science validation authority that repeatedly certifies that artifacts remain FAIR-compliant across every release cycle.
  • Tier. Project (Tier 2 — Active).
  • Status. Active — v6.2.0; FCC v1.9.0 re-vendored PHOENIX's 61-gate registry with SHA256 drift sentinel and the 13 OPEN-SCI templates. No always-on daemon.
  • Canonical link. rollingthunderfourtytwo-afk/ai-coe_ext (private). Local clones: authoritative at /mnt/d/VirtualDataRoom/Technology/Software/Ideate/ai-coe-docs; staging at /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/ai-coe_ext. See alignment-status.md for mono-repo path history and the Local-path column footnote above for the dual-entry convention.

NEXUS — Research Center

  • Full name / role. Research Center authoritative registry hub — and the sole codename authority for the ecosystem (CONSTEL ADR-032 subordinates its codename issuance to NEXUS/RC). Publishes the two ecosystem-wide YAML registries that FCC vendors under src/fcc/data/ecosystem/: ecosystem_projects.yaml (23 projects, file v2.3.0) and port_allocation.yaml (file v3.0.0: RC [2400,2599] band at 2430/2440, constellation 39xx block per ADR-020, with 86xx legacy-tolerated until 2026-Q3). NEXUS is also the sole R-CPV (Research Corpus Parity Value) vocabulary-insights authority.
  • Origin reasoning. "Nexus" is Latin for a connection, binding, link — NEXUS is the central connection point where every ecosystem project registers its ports, tiers, and contracts so downstream consumers (FCC, AOME, CONSTEL, AURORA) have a single source of truth.
  • Tier. Project (Tier 3 — Minimal, with staged promotion to Producer).
  • Status. Active — v6.2.0 authoritative as of 2026-06-18 (RC-MP-21 Contribution Intelligence). Live on :2430 (bare gateway; R-CPV insights endpoint served only under make uat-serve).
  • Canonical link. rollingthunderfourtytwo-afk/research_center_ext (private). Local clones: authoritative at /mnt/d/VirtualDataRoom/Technology/Software/Ideate/research_center_ext; staging at /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/research_center_ext. See the Local-path column footnote above for the dual-entry convention.

POLARIS — Archive coordination

  • Full name / role. ice_ext Model Creation and Management Extension. Coordinates long-term model archive with manifest discipline. Consumed by FCC via fcc.archive.polaris_bridge (promoted to stable in v1.5.0) and the LTAS (Long-Term Archive Steward) persona. Implements the US20250272473A1 structural concepts with Zachman classification cross-cut.
  • Origin reasoning. Polaris — the North Star — is the mariner's anchor for navigation. Its stable, unmoving position in the northern sky stood for constancy, guidance, and steadfast direction across cultures (Hindu "Dhruva" meaning immovable; Egyptian soul-guide). A long-term archive is exactly the North Star of the ecosystem — everything else can drift; POLARIS must not.
  • Tier. Project (Tier 1 — Strict, via overlay).
  • Status. Stable bridge (v1.5.0); PolarisMockBridge is the default when the live ice_ext adapter is not importable.
  • Canonical link. rollingthunderfourtytwo-afk/ice_ext (private — FTO posture preserved per v1.4.3 coordination note). Local clone at /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/ice_ext.

LYRA — Graph-of-thought

  • Full name / role. Graph-of-thought querying + harmonic vocabulary expansion. Consumed by FCC via fcc.knowledge.lyra_bridge (promoted to stable in v1.5.0). Augments GraphRAG results via get_lyra_bridge() sentinel-guarded calls.
  • Origin reasoning. Lyra is Orpheus's lyre — the instrument whose music could charm Hades himself, quell the Sirens, and move even inanimate objects. The Greeks took the lyre as a symbol of harmony, balance, elevation of the soul, and the guiding-out of souls from confusion. A graph-of-thought engine that expands vocabularies harmonically (via SKOS-proxy edges, broad-match chains) is the exact metaphorical fit.
  • Tier. Project (Alpha, private).
  • Status. v0.1.0 live (private). lyra.api.LyraAdapter implements LyraBridgeProtocol with the same 7-node / 6-edge seed graph the in-tree LyraMockBridge uses as reference. FCC's get_lyra_bridge() resolves to LyraAdapter when lyra_ext is installed, and falls back to the mock otherwise — FCC remains hermetic (no runtime dep). KGSE (Knowledge-Graph Serializer Elevator) persona coordinates the v0.2.0 graph-of-thought engine integration. Shipped v1.6.0 (2026-04-23).
  • Canonical link. https://github.com/rollingthunderfourtytwo-afk/lyra_ext (private). Local sibling checkout expected at /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/lyra_ext/.

AURORA — Sky Parlour

  • Full name / role. Sky Parlour live-trace viewer + UX portal. Subscribes to FCC's WebSocket event bus, renders live workflow traces on a D3 visualization, and exposes a UX portal/api on :2000 (/api/v1/health) with the SPA on :2010. Mirrors FCC's 37 canonical archetypes and coins none of its own.
  • Origin reasoning. Aurora is the Roman goddess of the dawn (Greek Eos) — she opens the gates of day and renews herself every morning. A live-trace visualizer is the dawn of visibility over a running simulation; each event it renders makes dark state newly visible. The "sky parlour" surface name extends the metaphor: a parlour under the sky where traces are displayed as they arrive.
  • Tier. Project (Tier 1 — Strict).
  • Status. Active — v3.3.0 ("portal-wiring"); live on :2000 / :2010.
  • Canonical link. rollingthunderfourtytwo-afk/sky-parlour (private). Local clone at /mnt/d/VirtualDataRoom/Technology/Software/Ideate/sky-parlour_poc/sky-parlour.

CONSTEL — PRISM

  • Full name / role. Classification GraphQL authority + constellation-codename registry. When FCC scaffolds a new vertical project, CONSTEL issues the next constellation name — but its codename authority is subordinate to NEXUS/RC per CONSTEL ADR-032. Per ADR-034 D4, CONSTEL owns the classification GraphQL only (PAOM owns the persona/R.I.S.C.E.A.R. GraphQL). 51 MCP tools; live on :8100.
  • Origin reasoning. A constellation is a coordinated set of named stars visible together; CONSTEL manages the ecosystem's own constellation of vocabularies (the ten fcc-*-plugin verticals). PRISM evokes light-splitting — federation splits one query into per-namespace sub-queries across the ecosystem, then reassembles.
  • Tier. Project (Tier 1 — Strict).
  • Status. Active — v13.0.0 (symbolic major; real changes landed in v12.1/v12.2).
  • Canonical link. rollingthunderfourtytwo-afk/constel_ext (private). Local clone at /mnt/d/VirtualDataRoom/Technology/Software/Ideate/constel_ext.

AOME — CRUCIBLE

  • Full name / role. React admin UI + forensic auditor, and the ecosystem's UAT gold standard. Consumes FCC's persona events over the WebSocket bridge and renders them in admin dashboards. Owns the privacy taxonomy; 3,845 tests at 96.96% coverage; governs vision-diff review by USD budget ($0.10/PR, $5/mo). Live on :3100 (MCP/A2A).
  • Origin reasoning. A crucible is the vessel that withstands the highest temperatures during metallurgical transmutation — the place where raw metal becomes refined. The forensic-auditor role subjects FCC events to intense scrutiny and renders them into admin-grade evidence, making the crucible a fitting metaphor for the transmutation of raw telemetry into governance artifacts.
  • Tier. Project (Tier 1 — Strict).
  • Status. Active — v4.16.0 (UAT gold standard); 3,845 tests at 96.96%.
  • Canonical link. rollingthunderfourtytwo-afk/aome_ext (private). Local clone at /mnt/d/VirtualDataRoom/Technology/Software/Ideate/aome_ext.

PAOM — SENTINEL

  • Full name / role. Decision-workflow decode pipeline + LLM router with a budget manager that now runs FCC personas as live agents. Consumes FCC persona + R.I.S.C.E.A.R. specs over A2A+MCP (:3201, health on :3210) via its PAOM-pull adapter (src/paom/integrations/ fcc_ingest.py, "transport B") — it reads FCC's persona YAML directly via PAOM_FCC_ROOT with zero FCC code change. Treats doc_context.constitution as authoritative and rejects any persona missing constitution.hard_stop. Most mature FCC consumer; pins FCC explicitly.
  • Origin reasoning. A sentinel is a watchful guard posted at a gate to control what passes through. PAOM guards the LLM cost + latency gate — every call through PAOM is scrutinised against budget rules before reaching a backend model. The sentinel metaphor encapsulates "watchful routing" perfectly.
  • Tier. Project (Tier 2 — Active).
  • Status. Active — v4.3.0 ("Helmsman"); HEAD on PI-11 (FCC agent-spec handoff). Live on :3201 / :3210.
  • Canonical link. rollingthunderfourtytwo-afk/paom (private). Local clone at /mnt/d/VirtualDataRoom/Technology/Software/Ideate/paom.

DISTILLER — FORNAX

  • Full name / role. Vocabulary distillation engine. Harvests patterns across the ten constellation verticals. Consumed by FCC via fcc.protocols.distiller_bridge (availability-sentinel pattern, mirror of POLARIS + LYRA bridges). 96% coverage, 1,781 backend tests.
  • Origin reasoning. Fornax is Latin for "furnace" (also a constellation name). Distillation requires heat and concentration — Fornax transforms wide, noisy vocabulary candidates into a refined, concentrated VocabularyMapping. The furnace metaphor matches the transformation operation (melt down → extract refined output).
  • Tier. Project (Tier 2 — Active).
  • Status. Active — ports 8002 + 5175.
  • Canonical link. rollingthunderfourtytwo-afk/distiller_ex (private). Local clone at /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/distiller_ex.

ATHENIUM

  • Full name / role. JV L2 library for analytics. Ships as a PyPI package declaring fcc.vocabulary_providers entry points. Port 8500 (library_only).
  • Origin reasoning. Athena — called Pallas Athena, born fully grown and armored from Zeus's forehead after he swallowed Metis (wisdom personified) — is the Greek goddess of wisdom, strategic intelligence, tactical war, crafts, and justice. Unlike Ares, whose domain is chaotic warfare, Athena represents applied intelligence: defensive strategy, reasoned judgment, and the disciplined arts. Her emblem, the little owl glaux (Athene noctua), was stamped on the obverse of the Athenian tetradrachm after 510 BC; the owl's nocturnal vision stood for intellectual insight that pierces darkness — the clarity to perceive truth in conditions that defeat ordinary sight. Analytics is the contemporary expression of this same faculty: it takes observations clouded by volume and noise and converts them into refined, actionable insight. The -ium suffix completes the metaphor. In chemistry nomenclature, -ium is the Latin-derived ending for elements and substances that have been isolated into their pure, refined form (calcium, titanium, helium, cesium). An analytics library is precisely the library-form extraction of Athena's analytic wisdom: the refined, importable, entry-point-addressable distillation of strategic intelligence, ready to be composed into FCC workflows via fcc.vocabulary_providers. ATHENIUM therefore reads as "the refined element of Athena's wisdom" — a disciplined name that simultaneously signals the mythic origin (wisdom) and the delivery form (refined library, not a running service).
  • Tier. Project (Tier 2 — JV partner, L2 library).
  • Status. Active — v0.3.0 pinned fcc>=1.2.1 (bump to >=1.3.5.4 staged with Athenium team).
  • Canonical link. rollingthunderfourtytwo-afk/l2_athenium (private). Local clone at /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/l2_athenium.

MNEMOSYNE

  • Full name / role. JV L2 library for memory subsystems. Ships as a PyPI package declaring fcc.vocabulary_providers entry points. Port 8510 (library_only).
  • Origin reasoning. Mnemosyne — Greek Titaness, personification of memory and mother of the nine Muses. Her name derives from mnēmē (remembrance). Ancient bards invoked her at the opening of epic poems to ensure accurate recall. A memory subsystem that ensures accurate recall across sessions is the literal application of the myth.
  • Tier. Project (Tier 2 — JV partner, L2 library).
  • Status. Active — unreleased (dynamic) pinned fcc>=1.2.1 (bump staged).
  • Canonical link. rollingthunderfourtytwo-afk/l2_mnemosyne (private). Local clone at /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/l2_mnemosyne.

CTO — Canonical Tabular Ontology

  • Full name / role. CTO is the optional object-model bridge FCC uses when the cto extra is installed. FCC's src/fcc/objectmodel/cto_bridge.py provides CTOFacadeAdapter and CTORepositoryAdapter that lift CTO tables into FCC's RepositoryProtocol[T] / ModelFacade shapes, preserving provenance without a hard runtime dependency.
  • Origin reasoning. CTO is a literal acronym — Canonical Tabular Ontology — not a metaphor. It names the form of the artifact (ontology expressed as canonical tables) rather than invoking a myth. The deliberate contrast with the mythological codenames around it signals that CTO is an object model format, not a running service: it is a data shape other projects align against.
  • Tier. Project (Tier 3 — library only, optional extra).
  • Status. Active — v14.0.0 (UAT + vision); live on :2810 with 13 web-MCP tools; bridge surface unchanged. Tracked by cto_available() sentinel in fcc.objectmodel.cto_bridge; mock/example repository takes over when not installed. CTO computes a worked R-CPV value (cto.ecosystem.rcpv=5851) and runs a conformance drift guard on FCC's EventSubscriberPlugin ABC (2 abstract methods, frozen).
  • Canonical link. rollingthunderfourtytwo-afk/cto (private). Local checkout at /mnt/d/VirtualDataRoom/Technology/Software/Ideate/attic_om_poc/cto.

Tooling & Integration Codenames (rollup)

The following three entries are support projects. They do not ship personas or R.I.S.C.E.A.R. specs and they are not counted in the 23 project inventory tracked by NEXUS. They make the ecosystem operate: release-asset distribution, cross-repo contract enforcement, and event capture with OpenTelemetry.

DATALOCK — l2_distro_hub_ext

  • Full name / role. DataLock Distribution Hub — hosts downloadable audience-bundle release assets (executive, technical, market, demos, industry variants) for the Findings Summary presentation package and related ecosystem publications. Each bundle ships a manifest.json with SHA-256 checksums.
  • Origin reasoning. "DataLock" evokes verifiable custody — once a release bundle is published and checksummed, it is locked to its exact contents. The codename signals "this is the tamper-evident distribution locker", mirroring the G1 data-immutability gate that applies to numeric metrics across industry variants. It is descriptive, not mythological — fitting for a support tier.
  • Tier. Tooling & Integration.
  • Status. Active — audience-bundle releases shipping (Executive / Technical / Market / Demos / Industry).
  • Canonical link. rollingthunderfourtytwo-afk/l2_distro_hub_ext (private). Local clone at /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/L2/l2_distro_hub_ext.

ORCHESTRA — ecosystem-integration-tests

  • Full name / role. Cross-repo integration-test harness for the FCC-L2 constellation. Verifies that FCC + CTO + CRUCIBLE + PRISM + AURORA + NEXUS + optionally SENTINEL share compatible federation contracts, namespace registries, vocabulary class-maps, and event shapes. Public repo; the one public-tier ecosystem project. Pinned in CI as the ecosystem-integration-tests gate (v1.3.11).
  • Origin reasoning. An orchestra is what happens when independent instrumentalists — each with their own score, technique, and instrument — play together from a shared conductor's baton. A cross-repo contract-test suite plays exactly that role: each partner repo has its own release cadence and build, and ORCHESTRA is the shared baton that proves they still play in tune every release.
  • Tier. Tooling & Integration (PUBLIC).
  • Status. Active — CI gate; five partners exercised (CTO / CRUCIBLE / PRISM / AURORA / NEXUS), SENTINEL via live-mode marker.
  • Canonical link. rollingthunderfourtytwo-afk/ecosystem-integration-tests (public). Local clone at /mnt/d/VirtualDataRoom/Technology/Software/Ideate/ecosystem-integration-tests.

FLOWX — p1

  • Full name / role. FlowX Event Capture System — unified event capture for Parlor UI + Event Viewer + Multi Ontology Explorer + Context Explorer, backed by a shared event-collector that also accepts OTLP traces (/v1/traces). Acts as the ecosystem's developer-side observability companion.
  • Origin reasoning. "FlowX" names the primary artifact the system was built to capture — flow-graph (D3) events from the legacy flowX viewer — while the x generalises to any traceable flow (UI interaction → OTel span → ETL → analysis store). The name reads as "flow, plus a pluggable axis": one backend, several UI flows, all converging on a single OTLP-compatible capture pipe.
  • Tier. Tooling & Integration.
  • Status. Active — Parlor (5174), Event Viewer (5175), Multi Ontology Explorer (5176, Phase B), Context Explorer (5177, Phase C.1); event-collector on 3001 with Swagger + OTLP.
  • Canonical link. rollingthunderfourtytwo-afk/p1 (private). Local checkout at /mnt/d/VirtualDataRoom/TechnologyArchitecture/Ideate/crucible/p1.

Constellation Vertical Codenames (rollup)

CONSTEL is the authority that issues the next constellation name when FCC scaffolds a new vertical project. The ten current verticals split across five industry domains (two verticals each — one ontology, one metadata). All ten became independent public GitHub repos at v0.2.0 in FCC v1.4.0 (2026-04-22). 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).

Ophiuchus — Medical ontology

  • Full name / role. Medical ontology vertical: HL7 FHIR Genomics IG + DICOM PS3 + IEC 62304.
  • Origin reasoning. Ophiuchus is Greek for "serpent-bearer" and represents the healer Asclepius grasping a snake. Asclepius learned the secrets of keeping death at bay after watching one serpent bring another healing herbs — the founding myth of medicine. The serpent-and-rod is still the universal symbol of medical practice. No constellation is more medically apt.
  • Tier. Constellation Vertical.
  • Status. v0.2.0 public.
  • Canonical link. ophiuchus_ext

Serpens — Medical metadata

  • Full name / role. Medical metadata vertical: ICH E2B(R3) ICSR + EudraVigilance (adverse-event reporting + pharmacovigilance metadata).
  • Origin reasoning. Serpens is the snake held by Ophiuchus — the two constellations are paired across the sky. Just as Serpens complements Ophiuchus in the heavens, medical metadata (pharmacovigilance, ICSR, drug safety) complements medical ontology. The pairing is deliberately preserved in the codename assignment.
  • Tier. Constellation Vertical.
  • Status. v0.2.0 public.
  • Canonical link. serpens_ext

Libra — Financial ontology

  • Full name / role. Financial ontology vertical: FIBO (EDM Council).
  • Origin reasoning. Libra is Latin for "the scales" — the balance held by the Greek goddess of justice Dike / Astraea. Libra is the only zodiac constellation representing an inanimate object, and that object is a weighing instrument. Financial ontologies (FIBO, double-entry accounting, equity-balance invariants) rest on the same balance metaphor — assets equal liabilities plus equity.
  • Tier. Constellation Vertical.
  • Status. v0.2.0 public.
  • Canonical link. libra_ext

Crater — Financial metadata

  • Full name / role. Financial metadata vertical: ISO 20022 + BCBS 239 + SR 11-7 (payment messaging + risk-data aggregation + model risk management).
  • Origin reasoning. Crater is Greek krater — the wide mixing-bowl used to dilute wine with water at ancient symposia. It appears in the sky as the cup the crow/raven fetched water for Apollo with. A mixing-bowl is the apt metaphor for financial metadata: it mixes and normalises heterogeneous payment messages (ISO 20022), risk aggregates (BCBS 239), and model-governance artifacts (SR 11-7) into a coherent exchange layer.
  • Tier. Constellation Vertical.
  • Status. v0.2.0 public.
  • Canonical link. crater_ext
  • Producer trajectory (2026-05-28). CraterVocabularyProvider ships in-repo at src/crater/federation/fcc/vocabulary.py and is registered via the fcc.plugins.vocabulary_providers entry-point group (Crater PR #10, commit 4c0017f). The standalone fcc-crater-plugin package is retired per Crater ADR-001. Crater pins its FCC parity baseline to FCC v1.8.2 (Crater PR #11, commit 6f1dc9e; report at docs/fcc/parity/v1.8.2-alignment.md). Ecosystem Best-Practices Charter posture: S1 and S6 In-flight, S2–S5/S7 Acked.

Scutum — Insurance ontology

  • Full name / role. Insurance ontology vertical: ACORD Reference Architecture v2.11.
  • Origin reasoning. Scutum is Latin for "shield" — named by the astronomer Hevelius in 1684 to honour King Jan III Sobieski's shield-like military defense of Europe against Ottoman expansion at the Battle of Vienna. Insurance is the financial shield against risk — the underwriting profession has always framed itself as protection against loss. Scutum is the ideal emblem for the insurance-ontology vertical.
  • Tier. Constellation Vertical.
  • Status. v0.2.0 public.
  • Canonical link. scutum_ext

Norma — Insurance metadata

  • Full name / role. Insurance metadata vertical: Solvency II Art. 44
  • IFRS 17 CSM (contractual service margin reporting + capital requirements).
  • Origin reasoning. Norma is Latin for "normal" — specifically a carpenter's right-angle set-square. Named by Nicolas Louis de Lacaille in the 18th century from l'Equerre et la Regle (square and rule). Insurance metadata is precisely the machinery of regulatory conformance — Solvency II capital rules, IFRS 17 reserve measurements, supervisory reporting squared against audit. A carpenter's square (ensuring structures are truly square) is the perfect metaphor for regulatory normalisation.
  • Tier. Constellation Vertical.
  • Status. v0.3.0 public.
  • Canonical link. norma_ext

Pyxis — Energy ontology

  • Full name / role. Energy ontology vertical: IEC 61970 CIM (Common Information Model for power systems).
  • Origin reasoning. Pyxis is abbreviated from Pyxis Nautica, Latin for "mariner's compass". It was carved out of the old Argo Navis constellation by Lacaille. A compass provides directional guidance — and power-system operators fundamentally navigate directional guidance of energy flows across a grid (generation → transmission → distribution → load). Pyxis matches the navigational, flow-aware character of energy ontologies.
  • Tier. Constellation Vertical.
  • Status. v0.2.0 public.
  • Canonical link. pyxis_ext

Vela — Energy metadata

  • Full name / role. Energy metadata vertical: IEC 62325 + ENTSO-E CGMES + IEEE 1547 (market exchange + transmission data + distributed energy resources).
  • Origin reasoning. Vela is Latin for "the sails" — the sails of Argo Navis, the ship on which Jason and the Argonauts sailed in search of the Golden Fleece. Lacaille split Argo Navis into Carina, Puppis, and Vela. Sails capture flow (wind) and convert it into motion — exactly what energy metadata surfaces do: they capture flow data (market clearing, generation schedules, grid telemetry) and convert it into actionable signals for settlement + dispatch.
  • Tier. Constellation Vertical.
  • Status. v0.2.0 public.
  • Canonical link. vela_ext

Columba — Government ontology

  • Full name / role. Government ontology vertical: DCAT-US 3.0 (data catalog vocabulary for US federal open data).
  • Origin reasoning. Columba is Latin for "dove". Introduced in the 1500s, it represents the dove Noah sent out to determine whether the Flood was receding — the dove returned with an olive branch, the first civic messenger across water. Government ontologies codify civic communication — the structured vocabulary by which a state's data speaks to its citizens — making the messenger-dove metaphor apt.
  • Tier. Constellation Vertical.
  • Status. v0.2.0 public.
  • Canonical link. columba_ext

Caelum — Government metadata

  • Full name / role. Government metadata vertical: NIEM 6.0 + eIDAS 2.0 (National Information Exchange Model + European digital identity regulation).
  • Origin reasoning. Caelum is Latin for "the engraver's chisel" — another Lacaille coinage from the 18th century. Government metadata is the engraving discipline of the public record: every digital identity attestation under eIDAS, every NIEM exchange packet, must be engraved permanently into the official record with cryptographic attestation. A chisel carves durably and precisely, and that is what a government metadata surface must do.
  • Tier. Constellation Vertical.
  • Status. v0.2.0 public.
  • Canonical link. caelum_ext

Codename Family Tree

The "who descends from whom" view of the ecosystem codenames. FCC is the lineage root; the project-tier siblings branch directly; CONSTEL is the root-authority for the ten constellation-vertical descendants; the three JV library peers (ATHENIUM, MNEMOSYNE, DISTILLER-lib) and the three Tooling & Integration peers (DATALOCK, ORCHESTRA, FLOWX) are peers of the projects rather than descendants. This tree is not a dependency graph — it is a codename-lineage graph, answering "which codename issued which".

flowchart TD
    FCC[FCC<br/>Framework root]

    subgraph ProjectTier["Project tier"]
        direction LR
        NEXUS_T[NEXUS / Research Center]
        PHOENIX_T[PHOENIX / AI-COE-Docs]
        AURORA_T[AURORA / Sky Parlour]
        AOME_T[AOME / CRUCIBLE]
        CONSTEL_T[CONSTEL / PRISM]
        PAOM_T[PAOM / SENTINEL]
        DIST_T[DISTILLER / FORNAX]
        CTO_T[CTO]
        POLARIS_T[POLARIS / ice_ext]
        LYRA_T[LYRA]
    end

    subgraph JVPeer["JV library peers (3)"]
        direction LR
        ATH_T[ATHENIUM]
        MNEM_T[MNEMOSYNE]
        DISTLIB_T[DISTILLER-lib]
    end

    subgraph ToolingPeer["Tooling & Integration peers (3)"]
        direction LR
        DATALOCK_T[DATALOCK<br/>l2_distro_hub_ext]
        ORCHESTRA_T[ORCHESTRA<br/>ecosystem-integration-tests]
        FLOWX_T[FLOWX<br/>p1]
    end

    subgraph ConstelDesc["10 constellation descendants (CONSTEL-issued)"]
        direction LR
        subgraph MedDomain["Medical domain"]
            OPH_D[Ophiuchus]
            SER_D[Serpens]
        end
        subgraph FinDomain["Financial domain"]
            LIB_D[Libra]
            CRA_D[Crater]
        end
        subgraph InsDomain["Insurance domain"]
            SCU_D[Scutum]
            NOR_D[Norma]
        end
        subgraph EneDomain["Energy domain"]
            PYX_D[Pyxis]
            VEL_D[Vela]
        end
        subgraph GovDomain["Government domain"]
            COL_D[Columba]
            CAE_D[Caelum]
        end
    end

    FCC --> NEXUS_T
    FCC --> PHOENIX_T
    FCC --> AURORA_T
    FCC --> AOME_T
    FCC --> CONSTEL_T
    FCC --> PAOM_T
    FCC --> DIST_T
    FCC --> CTO_T
    FCC --> POLARIS_T
    FCC --> LYRA_T

    FCC -.-> ATH_T
    FCC -.-> MNEM_T
    FCC -.-> DISTLIB_T

    FCC -.-> DATALOCK_T
    FCC -.-> ORCHESTRA_T
    FCC -.-> FLOWX_T

    CONSTEL_T ==>|issues codename| OPH_D
    CONSTEL_T ==>|issues codename| SER_D
    CONSTEL_T ==>|issues codename| LIB_D
    CONSTEL_T ==>|issues codename| CRA_D
    CONSTEL_T ==>|issues codename| SCU_D
    CONSTEL_T ==>|issues codename| NOR_D
    CONSTEL_T ==>|issues codename| PYX_D
    CONSTEL_T ==>|issues codename| VEL_D
    CONSTEL_T ==>|issues codename| COL_D
    CONSTEL_T ==>|issues codename| CAE_D

Invariants: - FCC is the lineage root; every codename in the ecosystem descends from it (directly or via CONSTEL). - CONSTEL is the only codename-issuing authority for constellation verticals — FCC does not issue vertical names directly. - JV library peers + Tooling & Integration peers (dotted arrows) are not descendants; they are independently-named sibling products that integrate with FCC via entry points or contract tests. - The ten constellations split evenly across five industry domains (two per domain: one ontology + one metadata). - Adding a new vertical requires a CONSTEL-issued codename — FCC scaffolding refuses to proceed without one.

Source: docs/ecosystem/codename-decoder.md (this document), CONSTEL codename registry (external — constel_ext repo).

POLARIS Archive Flow

End-to-end flow of a long-term model archive through POLARIS. An FCC agent pushes a model artifact; the POLARIS bridge (live ICEFacadeAdapter when ice_ext.plugin.bridge is importable; PolarisMockBridge in-memory dict otherwise) assigns an archive-id; the archive store receives a tar-manifest with SHA-256 attestation; the LTAS (Long-Term Archive Steward) persona audits manifest discipline asynchronously. The restore path is symmetric.

sequenceDiagram
    autonumber
    participant Agent as FCC agent
    participant Bridge as polaris_bridge.get_polaris_bridge()
    participant Live as ICEFacadeAdapter<br/>(live, private ice_ext)
    participant Mock as PolarisMockBridge<br/>(in-memory dict)
    participant Store as Archive store<br/>(tar-manifest + SHA-256)
    participant LTAS as LTAS persona<br/>(Long-Term Archive Steward)

    Agent->>Bridge: push_archive(model, metadata)
    Bridge->>Bridge: sentinel probe:<br/>import ice_ext.plugin.bridge?
    alt ice_ext available
        Bridge->>Live: forward push
        Live->>Store: write tar + SHA-256 manifest
        Store-->>Live: archive-id = "archive-<sha256[:16]>"
        Live-->>Bridge: archive-id
    else ice_ext absent
        Bridge->>Mock: forward push
        Mock->>Mock: in-memory dict keyed by archive-id
        Mock-->>Bridge: archive-id (same shape)
    end
    Bridge-->>Agent: archive-id

    Note over Agent,LTAS: Later — audit pass
    LTAS->>Bridge: query_manifest(archive-id)
    Bridge->>Store: read manifest
    Store-->>Bridge: {sha256, created_at, artifact_list}
    Bridge-->>LTAS: manifest record
    LTAS->>LTAS: assert manifest-discipline rules<br/>(retention · integrity · attribution)

    Note over Agent,Store: Restore path (symmetric)
    Agent->>Bridge: pull_archive(archive-id)
    Bridge->>Store: fetch tar + re-verify SHA-256
    Store-->>Bridge: artifact bytes + manifest
    Bridge-->>Agent: restored model

Invariants: - get_polaris_bridge() always returns a working bridge — either live or mock; callers never crash on POLARIS absence. - Archive-id assignment is synchronous + deterministic (keyed on SHA-256 of the canonical artifact bytes). - Manifest discipline (retention + integrity + attribution) is enforced by LTAS during audits, not at push time — push is fire-and-forget. - Mock bridge provides full protocol coverage so tutorials + CI run hermetic (no private ice_ext dependency). - Restore verifies SHA-256 on read — corrupted artifacts surface at pull time with a canonical integrity error.

Source: src/fcc/archive/polaris_bridge.py, src/fcc/data/personas/ltas.yaml · LTAS persona.

LYRA Integration Sequence

GraphRAG query augmentation through LYRA's graph-of-thought surface. FCC's GraphRAG pipeline probes the LYRA availability sentinel; if lyra_ext is installed the LyraAdapter resolves; otherwise the LyraMockBridge walks a 7-node / 6-edge in-memory seed graph. Either way the KGSE (Knowledge Graph Serializer Elevator) persona sees a KnowledgeGraph result and harmonic-vocabulary-expansion artifacts.

sequenceDiagram
    autonumber
    participant GR as FCC GraphRAG pipeline
    participant Factory as get_lyra_bridge()
    participant Sentinel as LYRA sentinel probe
    participant Live as LyraAdapter<br/>(lyra_ext.api, private)
    participant Mock as LyraMockBridge<br/>(7-node / 6-edge seed)
    participant KG as KnowledgeGraph
    participant KGSE as KGSE persona

    GR->>Factory: get_lyra_bridge()
    Factory->>Sentinel: import lyra.api?
    alt lyra_ext installed
        Sentinel-->>Factory: True
        Factory-->>GR: LyraAdapter
    else lyra_ext absent
        Sentinel-->>Factory: False
        Factory-->>GR: LyraMockBridge
    end

    GR->>Live: graph_of_thought_query(prompt, namespace)
    Note over Live,Mock: Mock path identical — same protocol
    Live->>Live: expand harmonic vocabulary<br/>(SKOS broad-match chains)
    Live->>KG: augment with 7-node / 6-edge seed<br/>(or live graph when real)
    KG-->>Live: enriched KnowledgeGraph
    Live-->>GR: result (nodes + edges + citations)

    GR->>KGSE: register result for serializer elevation
    KGSE->>KGSE: assess stability for fcc.api.* promotion

Invariants: - get_lyra_bridge() never returns None — the sentinel guarantees a functional bridge (live or mock). - Mock walks the same 7-node / 6-edge seed graph the live adapter uses as reference, so tutorials produce reproducible results. - The live LyraAdapter lives in the private lyra_ext repo; FCC stays hermetic (no runtime dep). - KGSE persona is the elevation authority — no bridge surface gets promoted to fcc.api.* without a KGSE assessment. - v1.6.0 promoted the LYRA bridge protocol to stable; the live backend publication date is owner-gated.

Source: src/fcc/knowledge/lyra_bridge.py, src/fcc/data/personas/kgse.yaml · KGSE persona.

Constellation Cross-Wire

The ten constellations are siblings — all descendants of CONSTEL, all in the 39xx port block (RC ADR-020), all at v0.2.0 public release. This diagram shows them grouped by vertical-plugin affinity (the five industry domains) so you can see at a glance which ontology pairs with which metadata vertical.

flowchart TD
    CONSTEL_ROOT[CONSTEL / PRISM<br/>codename-issuing authority<br/>federation v2]

    subgraph Medical["Medical · 39xx block (ADR-020)"]
        direction LR
        OPH_X[Ophiuchus<br/>HL7 FHIR Genomics · DICOM · IEC 62304]
        SER_X[Serpens<br/>ICH E2B R3 · EudraVigilance]
    end

    subgraph Finance["Finance · 39xx block (ADR-020)"]
        direction LR
        LIB_X[Libra<br/>FIBO]
        CRA_X[Crater<br/>ISO 20022 · BCBS 239 · SR 11-7]
    end

    subgraph Insurance["Insurance · 39xx block (ADR-020)"]
        direction LR
        SCU_X[Scutum<br/>ACORD v2.11]
        NOR_X[Norma<br/>Solvency II · IFRS 17]
    end

    subgraph Energy["Energy · 39xx block (ADR-020)"]
        direction LR
        PYX_X[Pyxis<br/>IEC 61970 CIM]
        VEL_X[Vela<br/>IEC 62325 · CGMES · IEEE 1547]
    end

    subgraph Government["Government · 39xx block (ADR-020)"]
        direction LR
        COL_X[Columba<br/>DCAT-US 3.0]
        CAE_X[Caelum<br/>NIEM 6.0 · eIDAS 2.0]
    end

    CONSTEL_ROOT --> Medical
    CONSTEL_ROOT --> Finance
    CONSTEL_ROOT --> Insurance
    CONSTEL_ROOT --> Energy
    CONSTEL_ROOT --> Government

    OPH_X <-->|ontology ⇄ metadata| SER_X
    LIB_X <-->|ontology ⇄ metadata| CRA_X
    SCU_X <-->|ontology ⇄ metadata| NOR_X
    PYX_X <-->|ontology ⇄ metadata| VEL_X
    COL_X <-->|ontology ⇄ metadata| CAE_X

Invariants: - All ten constellations share the same public-release scaffolding (MIT · Contributor Covenant 2.1 · CI + release workflows · issue + PR templates). - Ports follow the 39xx block (39{vertical*10 + role}) per RC ADR-020 (tier-3 cutover; 86xx legacy-tolerated until 2026-Q3). - Every constellation is paired ontology-⇄-metadata within its domain — neither half is expected to run standalone in a real deployment. - Adding a sixth industry domain requires two new constellation codenames (one ontology + one metadata), issued by CONSTEL + bumped under a new port-range. - All ten map 1:1 to a plugins/fcc-<codename>-plugin/ vocabulary provider inside the FCC repo.

Source: docs/ecosystem/alignment-status.md · constellation table, plugins/ · vocabulary-provider plugins for each codename.

See also