Portal-Component Federation — AOME / AURORA Coordination Notice

FCC's record of the portal-component federation handoff. Channel-B: this is a notice; FCC does not edit AOME/AURORA repos. Mount is host-pull — FCC publishes a conformant well-known doc + serves embeddable panes; a host ingests them.

What FCC now publishes (v2.0.0)

• GET /.well-known/portal-components.json — conformant to the AOME RFC #182 portal-component-v1 contract (top-level spec; per-component keys limited to the host's _ALLOWED_COMPONENT_KEYS; persona_scope ⊆ the RT-49 personas).
• Embeddable panes at GET /embed/<slug> — server-rendered, CORS-free, JS-light, tokens-v1-themed. Initial set:
• fcc.personas → /embed/personas (persona catalog)
• fcc.ecosystem → /embed/ecosystem (ecosystem roster)
• fcc.compliance → /embed/compliance (EU AI Act risk classification)

Served by the UX gateway (default :8901). See ADR-016.

What the host (AOME / AURORA) actions

1. Ingest FCC's well-known descriptor (AOME via its POST /api/v1/admin/portal/components/ingest/fcc or the admin UI from the well-known URL; AURORA per its portal-mount path when it ships one).
2. Mount the iframe_url panes in a CSP-sandboxed frame.
3. Optionally override the tokens-v1 CSS variables to theme the panes.

FCC will not write to the host repos; coordinate any contract changes via a GitHub issue against FCC.

Open notes

• AURORA (v3.3.0) does not yet publish/consume a portal descriptor — this notice is forward-looking for when it does.
• The panes are intentionally minimal (universal, host-knowledge-free). Richer render_mode: native panels can follow if a shared kit is adopted.

Current as of v2.0.0.