Skip to content

Pillar C: Bidirectional Federation Prompts

Seven prompts exercising v1.5.0 Pillar C — bidirectional cross-project federation — across the 11-namespace registry, with CONSTEL (PRISM) acting as the constellation-name authority and VDS patrolling vocabulary drift.

Pillar C lets FCC both publish entities outward to sister projects and consume entities inbound, with conflict detection and provenance preserved.

Context for Claude

Federation uses src/fcc/federation/resolver.py + namespace.py + tracker.py. Each federation pass emits events on PAOMBus so SMC's scorecards can track cross-project drift. Personas VDS + ZCA operate the governance layer.

Prompt 1: Outbound entity publish

Publish the persona DAR (Decision Archaeologist) outbound to 3
subscribed ecosystems (AOME, CONSTEL, PAOM). For each:
- Namespace URI
- Serialization format (from KGSE)
- Subscription contract
- Acknowledgement timing

Report the round-trip SHA so the publish is traceable.

Expected outcome: publish transcript.

Prompt 2: Inbound entity consume

Consume an inbound entity (a new MNEMOSYNE vocabulary mapping).
Walk the pipeline:
- Resolver match
- Namespace bind
- Conflict check (against existing FCC entity)
- Approval gate (auto-merge vs human review)
- Tracker event emission

Expected outcome: consume pipeline report.

Prompt 3: Conflict detection

An inbound entity collides with an existing FCC entity on 2
attributes. Produce:
- Side-by-side diff
- Recommended resolution (accept inbound, reject, merge, defer)
- Reviewer persona (VDS)
- Human-review packet

Expected outcome: conflict resolution packet.

Prompt 4: Namespace audit

Audit all 11 ecosystem namespaces:
- URI stability
- Versioning scheme
- Coexistence status (multiple versions live?)
- Recommended deprecations

Emit a registry health scorecard.

Expected outcome: registry health scorecard.

Prompt 5: Drift detection with VDS

Coordinate with VDS: run a drift-detection pass across the last
7 days of federation activity. For each drift finding:
- Direction (FCC → consumer, consumer → FCC)
- Magnitude
- Severity
- Owner persona for remediation

Expected outcome: drift pass + owner table.

Prompt 6: Federation observability

Federation events route to PAOMBus. For the last 100 events:
- Group by type
- Report p50/p95 latency per type
- Flag any event type whose p95 exceeds 500ms
- Propose a lane move (to UXBus) if latency matters for UX

Expected outcome: observability digest.

Prompt 7: Failure mode — registry offline

The CONSTEL namespace registry is offline. For Pillar C:
- Expected fallback behavior
- Queue discipline
- Retry strategy
- Data-loss boundary
- Recovery playbook

Close with the single alert that must fire within 60 seconds.

Expected outcome: failure-mode playbook.

  • Tutorial: docs/tutorials/advanced-capabilities/bidirectional-federation-patterns.md (Pool B)
  • Personas: VDS, ZCA, LAR
  • ADR: docs/decisions/ADR-013_bidirectional_federation.md (v1.5.1)
  • Decoder: docs/ecosystem/codename-decoder.md (CONSTEL + namespace registry)