Skip to content

Universal Services — Cross-Ecosystem Coordination

Status: v1.5.0 Pillar scaffolding. Lists the 15+ services FCC consumes from its ecosystem + ecosystem partners, plus the drift policy and fallback behavior for each. The superset-first principle governs this document: every FCC-owned consumer lists what it calls; the Research Center (RC) rationalizes duplicates + conflicts over time in its own roadmap.

Why this document exists

The FCC ecosystem is intentionally distributed. FCC owns the framework (personas, R.I.S.C.E.A.R., workflows); other projects own complementary capabilities — RC hosts authoritative registries; the OpenTelemetry collector provides telemetry plumbing; UX REST gateway brokers browser-to- backend traffic; PAOM decodes decision workflows; the Distiller harvests cross-vertical insights; PHOENIX coordinates patent IP; LYRA provides graph-of-thought retrieval; POLARIS preserves long-term model artifacts; ice_ext hosts Model primitives with HNAR/PHOENIX tie-in; and SAFe drives the portfolio-level operating model.

When any one of these services changes shape, FCC must either adapt or activate a degraded-mode fallback. Without a single source of truth for "what FCC expects from which service," coordinated evolution is hard. This doc is that single source of truth — scoped to the FCC consumer side. Each service entry lists:

  • Definition — what FCC calls and why.
  • SLA — what FCC treats as the contractual promise (availability, latency, schema stability).
  • Drift policy — how changes propagate (SemVer major / minor / patch; SHA-256 drift sentinel; preview-namespace window).
  • Fallback behavior — what FCC does when the service is unavailable or has drifted out of contract.

The RC owns reconciliation — if two services duplicate a capability, or if a service is in the list here but RC thinks it should be deprecated, that debate lives in RC's ADR repo, not here. FCC stays a consumer of this doc; contributions are additive.

Tier 1 — Authoritative Registries (Research Center)

1. RC ecosystem registry (ecosystem_projects.yaml)

  • Definition. RC publishes the authoritative list of 19 projects across 3 tiers (7 ecosystem partners, 2 JV L2 libraries, 10 constellation vocabularies). FCC vendors a copy under src/fcc/data/ecosystem/ecosystem_projects.yaml and runs a SHA-256 drift sentinel against the RC master.
  • SLA. Schema version v2.0.0 (declared in the file header). Additive-only within v2.x; breaking changes bump to v3.0.0 with at least a one-minor deprecation window.
  • Drift policy. SHA-256 drift check in tests/test_ecosystem_registry_drift.py compares the FCC copy against the RC copy when RC is checked out locally. CI fails on drift.
  • Fallback. When RC is not checked out locally, the drift test is skipped gracefully (exit 0) and FCC runs against the vendored copy.

2. RC port allocation registry (port_allocation.yaml)

  • Definition. RC owns the ecosystem-wide port plan (AURORA 8300-8399, FCC backend 8000, constellation FastAPI 8600-8641, admin API 8900, etc.). FCC vendors a copy + checks drift.
  • SLA. Breaking port reassignments require an RC ADR + one-minor deprecation window (see v1.3.5.4 constellation port shift 8300 → 8600 per RC ADR-007).
  • Drift policy. Same SHA-256 sentinel pattern as above.
  • Fallback. Vendored copy authoritative when RC absent.

3. RC namespace registry (11 ecosystems)

  • Definition. Cross-project entity-resolution namespace map — FCC uses it in fcc.federation.namespace for cross-project entity resolution.
  • SLA. Namespace additions are additive; renames require one-minor deprecation.
  • Drift policy. In-process check via fcc.federation.namespace registry load.
  • Fallback. Degrades to FCC-only namespace (no cross-project resolution).

Tier 2 — Telemetry + Traffic Plumbing

4. OpenTelemetry collector (vendored config)

  • Definition. RC-vendored OTEL collector config at src/fcc/data/ecosystem/otel_collector.yaml — OTLP/gRPC endpoint consumed by fcc.observability.integration when opentelemetry-api is installed under the [otel] extra.
  • SLA. OTLP/gRPC endpoint available on port 4317 (standard). Schema follows OpenTelemetry semantic conventions spec v1.27+.
  • Drift policy. OTEL spec is upstream — FCC pins opentelemetry-api>=1.27.0 and tracks OTel releases via dependabot.
  • Fallback. When [otel] extra is not installed, FCC degrades to the in-memory FccTracer + FccMetrics shipped since v1.4.x — no telemetry loss, just local-only.

5. UX REST gateway (port 8200)

  • Definition. Browser-to-backend traffic broker. Routes React frontend requests to fcc protocol ws-bridge (port 8000) + admin API (port 8900).
  • SLA. WebSocket + HTTP/1.1 supported. Backend /health returns 200 within 500ms under nominal load.
  • Drift policy. Route schema changes bump frontend minor version (see frontend/package.json). REST API contract covered by ecosystem-integration-tests offline suite.
  • Fallback. Frontend fails fast to an error page with WebSocket connection diagnostics. No silent retry.

6. PAOM decode endpoint

  • Definition. PAOM hosts the decision-workflow decode pipeline. FCC calls it via the fcc.plugins.fcc-paom-plugin surface.
  • SLA. Decode latency target <2s for a typical R.I.S.C.E.A.R. persona prompt. Availability target 99.0% (informal).
  • Drift policy. PAOM API version pinned in the plugin manifest; breaking changes require the plugin to bump major.
  • Fallback. When PAOM is absent, FCC's persona-aware prompt generation degrades to the static template rendered from the RISCEARSpec dataclass — works but is less context-aware.

Tier 3 — Domain Subsystems

7. Distiller cross-vertical harvest

  • Definition. Distiller harvests patterns across the 10 constellation verticals. FCC consumes its output through fcc.protocols.distiller_bridge (availability-sentinel pattern, mirror of POLARIS + LYRA bridges).
  • SLA. Harvest cadence is sibling-repo controlled; FCC does not pin a freshness SLA.
  • Drift policy. Bridge protocol is stable; output schema versioned per Distiller release.
  • Fallback. When Distiller is absent, fcc.protocols.distiller_bridge returns a NoOpDistillerBridge — downstream code sees empty harvest results rather than failure.

8. PHOENIX three-pillar authority (quality gates + patent IP + open-science validation)

  • Definition. PHOENIX is the ecosystem's three-pillar authority: (1) the 58-gate quality registry vendored into FCC v1.3.8 with a SHA256 drift sentinel; (2) cross-repo patent IP consolidation consumed by FCC through the IHL (Innovation Handoff Liaison) + PCT (Patent Claim Tracer) personas + docs/patent/ tree; and (3) the Open-Science Validation Authority role — PHOENIX reviews and validates the per-codename patent subtrees, the 12 OPEN-SCI templates shipped with FCC v1.3.8, and every persona's open_science_refs declaration against PHOENIX's FAIR-workflow + reproducibility-manifest discipline. The OSC (Open-Science Curator) persona enforces this discipline on the FCC side during forensic audits.
  • SLA. 58-gate registry vendored at PHOENIX Tier-1. Gate schema is stable within a minor release. The 12 OPEN-SCI templates and the OPEN-SCI-NNN reference numbers are monotonically increasing + append-only (per OSC's policy).
  • Drift policy. Vendored gate registry SHA-256 check added in v1.3.8. Open-science template changes are reviewed through PHOENIX's innovation-center workflow before FCC vendors additions.
  • Fallback. FCC's patent documentation and open-science surfaces remain self-contained — no runtime dependency on PHOENIX, only the content-layer coordination via docs/patent/ and docs/ecosystem/open-science/. Missing open-science references surface as FA audit findings, not runtime failures.

9. LYRA graph-of-thought (v1.5.0 promotion)

  • Definition. LYRA exposes graph-of-thought querying + harmonic vocabulary expansion. FCC consumes it through fcc.knowledge.lyra_bridge (promoted to stable in v1.5.0 per docs/migrations/v1.5.0-api-additions.md).
  • SLA. lyra package not yet published — sentinel returns False and the LyraMockBridge is the default return of get_lyra_bridge().
  • Drift policy. Once LYRA publishes, the bridge protocol gets a compatibility check; breaking changes bump the bridge SemVer major.
  • Fallback. LyraMockBridge walks a functional in-memory KnowledgeGraph seed — full protocol coverage without the live backend.

10. POLARIS long-term archive (v1.5.0 promotion)

  • Definition. POLARIS coordinates long-term model archive. FCC consumes it through fcc.archive.polaris_bridge (promoted to stable in v1.5.0). LTAS (Long-Term Archive Steward) persona owns the manifest-discipline contract on the FCC side.
  • SLA. When ice_ext.plugin.bridge.ICEFacadeAdapter is importable, that is the live adapter. Archive-id assignment is synchronous.
  • Drift policy. Bridge protocol is stable. The underlying ice_ext.plugin.bridge API tracks ice_ext STATUS.md §n asks that KGSE coordinates promotion for.
  • Fallback. PolarisMockBridge — in-memory dict keyed by archive-<sha256[:16]> — covers the full push/pull/query protocol.

11. ice_ext Model primitives

  • Definition. ice_ext provides Model primitives (ModelHistoryEvent streams consumed by DAR; model-storage adapters consumed by LTAS; STATUS.md §n asks tracked by KGSE).
  • SLA. API stability follows ice_ext's own SemVer line.
  • Drift policy. make ice-ext-integration runs the ice_ext test suite against the current FCC checkout (skips gracefully when ice_ext is not checked out).
  • Fallback. Every ice_ext consumer has a no-op or mock fallback (same availability-sentinel pattern as distiller/polaris/lyra).

Tier 4 — Cross-Cut Governance

12. Zachman cross-cut (rows × columns matrix)

  • Definition. Every FCC persona carries a zachman_cell declaration (ARCHITECT/HOW, ENGINEER/WHEN, EXECUTIVE/WHY, etc.) that ties the persona to the Zachman Framework row + column coordinate. Enforced in persona schema; validated at load time.
  • SLA. Zachman terminology is upstream (Zachman International); row/column names are preserved verbatim per docs/i18n/glossary.csv.
  • Drift policy. Persona loader validates zachman_cell against the canonical row × column list. New personas without a declaration fail validation.
  • Fallback. N/A — Zachman cell is a required persona field.

13. SAFe reconciliation (portfolio operating model)

  • Definition. SAFe portfolio epics + PI planning. FCC consumes via the SFBI (SAFe-FCC Bridge Interpreter) + SMC (SAFe Metrics Crafter) personas + make safe-report target.
  • SLA. SAFe terminology is upstream (Scaled Agile Inc.); SAFe is a registered trademark preserved verbatim per glossary.
  • Drift policy. Portfolio-epics front matter schema is pinned at docs/safe/portfolio/epics.md; SFBI enforces it during bridge reports.
  • Fallback. N/A — SAFe consumption is additive; absence just means no PI status table is rendered.

14. Open-Science reference (OPEN-SCI-NNN)

  • Definition. Open-science reference numbers (OPEN-SCI-001 through OPEN-SCI-014+) — FCC personas declare open_science_refs (produces + consumes) to tie FAIR workflows + reproducibility manifests to canonical artifacts.
  • SLA. Reference numbers are monotonically increasing + append-only; no reference is ever deleted (per OSC's policy).
  • Drift policy. OSC (Open-Science Curator) persona enforces the reference discipline during forensic audits.
  • Fallback. Missing references surface as FA audit findings, not runtime failures.

15. Federation namespace registry

  • Definition. fcc.federation.namespace — cross-project entity resolution namespace map (11 ecosystems).
  • SLA. Namespace entries are append-only; renames require one-minor deprecation.
  • Drift policy. Namespace registry snapshots tested in tests/test_federation_*.py.
  • Fallback. Degrades to FCC-only resolution.

16. Ecosystem-integration-tests offline suite

  • Definition. Sibling ecosystem-integration-tests repo — 49 offline contract tests covering namespace registries, plugin discovery, vocabulary round-trips, MCP contracts, A2A skill cards, event-lane boundaries, and OpenAPI aggregation.
  • SLA. All 49 tests pass offline (no network, no live services).
  • Drift policy. CI gate in v1.3.11+ (advisory in 1.3.x, required candidate in v1.5.x).
  • Fallback. make ecosystem-check skips gracefully when sibling repo is not checked out.

Superset-first principle

This list is the FCC-consumer superset. Every capability FCC calls, today or planned, shows up here. The list is deliberately longer than strictly-needed because:

  1. It documents what FCC expects — giving the RC a target for rationalization (e.g. "both items 4 and 15 could be handled by the same OTEL span attribute — let's consolidate").
  2. It documents the fallback story uniformly — every service has a graceful-degradation path, every bridge has a mock fallback, every registry has a vendored copy + SHA-256 drift check.
  3. It provides the KGSE (Knowledge Graph Serializer Elevator) persona with a single source of truth for promotion candidates — when a service listed here becomes stable, KGSE proposes promoting the corresponding bridge surface into fcc.api.*.

RC rationalization happens in RC's roadmap, not here. FCC contributions to this doc are additive: when FCC adds a new consumer seam, the entry lands here first, then RC decides whether to reconcile.

FCC ↔ RC Paper-Handoff Sequence

The v1.4.3 / v1.5.3 paper-handoff pattern in motion. FCC drafts the industry paper inside docs/papers/ using its IHL (Innovation Handoff Liaison) + RHL (Research Handoff Liaison) personas; RC reviews via the academic-lead persona and the quality-gate registry from PHOENIX; RC publishes under its authoritative-research surface; FCC tracks citations back into the PCT (Patent Claim Tracer) persona's claim-chain. Concrete examples: RC PR #79 (Graph-of-Thought paper handoff) and RC PR #80 (FTO Policy paper handoff) — both shipped in v1.5.3.

sequenceDiagram
    autonumber
    participant IHL as FCC IHL persona<br/>(Innovation Handoff Liaison)
    participant RHL as FCC RHL persona<br/>(Research Handoff Liaison)
    participant Papers as docs/papers/<br/>(FCC-side draft)
    participant RC as RC academic lead<br/>(NEXUS)
    participant PHX as PHOENIX gate registry<br/>(58 gates)
    participant Pub as RC publications/
    participant PCT as FCC PCT persona<br/>(Patent Claim Tracer)

    IHL->>Papers: draft paper.md + claims.yaml
    Papers->>RHL: hand off for ecosystem framing
    RHL->>Papers: add cross-ecosystem context<br/>(citations to 11 siblings)
    Papers->>RC: open handoff PR (e.g., RC #79, #80)
    RC->>PHX: validate against quality gates<br/>(58-gate registry)
    PHX-->>RC: gate verdict (pass/fail + evidence)
    alt Gates pass
        RC->>Pub: merge + publish under RC publications/
        Pub-->>RHL: citation-ready URL + DOI
        RHL->>PCT: register citation claim-chain
        PCT->>PCT: update docs/patent/ claim tracker
    else Gates fail
        RC-->>IHL: return with gate findings
        Note over IHL,Papers: IHL revises draft,<br/>re-submits handoff PR
    end

Invariants: - The handoff is a PR, not an imported artifact — FCC and RC remain loosely coupled across separate repos. - PHOENIX's 58-gate registry is the single validation surface; FCC and RC both consume the same vendored copy (SHA-256 drift gate). - Every accepted handoff adds a citation claim to FCC's PCT persona's claim-chain — no orphan publications. - If gates fail, the handoff is returned to the IHL; the paper is never published in an unvalidated state. - v1.4.3 introduced the scaffolding (PR templates, personas); v1.5.3 shipped the first two production handoffs (RC PR #79, #80).

Source: src/fcc/personas/_data/ihl.yaml · IHL persona definition, src/fcc/personas/_data/rhl.yaml · RHL persona definition, docs/patent/ · PCT claim tracker.

  • docs/migrations/v1.5.0-api-additions.md — POLARIS + LYRA bridge promotion (items 9 + 10 above).
  • docs/ecosystem/alignment-status.md — living alignment status across the 10 constellation verticals.
  • docs/ecosystem/rc-coordination-v143.md — v1.4.3 coordination notes.
  • docs/ecosystem/ice-ext-patent-coordination-v143.md — v1.4.3 ice_ext + patent coordination notes.
  • src/fcc/data/ecosystem/ecosystem_projects.yaml — vendored RC registry (item 1 above).