Skip to content

Professional Use Cases

This diagram maps enterprise architects, compliance officers, and platform engineers to the FCC subsystems they exercise when deploying the framework inside a regulated organisation. Professionals enter through docs/for-professionals/ and lean on the FederationRegistry, ComplianceAuditor, ModelFacade, EventBus, the 30-plus quality gates, and the VocabularyProviderPlugin extension point (12 plugins currently ship). Procurement-facing outputs include model cards, audit reports, and standards-export bundles (RDF, OWL, SKOS, JSON-LD).

The diagram below traces the professional audience-to-subsystem mapping.

graph LR
    A((Professional))
    UC1[/"Enterprise deployment"/]
    UC2[/"Governance and compliance"/]
    UC3[/"CI integration"/]
    UC4[/"Production monitoring"/]
    UC5[/"Standards export"/]
    UC6[/"Multi-project federation"/]
    S1[FederationRegistry]
    S2[ComplianceAuditor]
    S3[ModelFacade]
    S4[EventBus + DLQ]
    S5[VocabularyProviderPlugin]
    S6[Quality gates]
    S7[Docs-as-code generator]
    A --> UC1
    A --> UC2
    A --> UC3
    A --> UC4
    A --> UC5
    A --> UC6
    UC1 --> S7
    UC1 --> S3
    UC2 --> S2
    UC2 --> S6
    UC3 --> S4
    UC3 --> S6
    UC4 --> S4
    UC5 --> S3
    UC6 --> S1
    UC6 --> S5

Enterprise Deployment is the anchor task: the docs-as-code generator emits 56 files per persona, which feed into a review-and-publish pipeline. Governance and Compliance combines the ComplianceAuditor (256-plus EU AI Act requirements) with the 30-plus quality gates so release readiness is a single pass-or-fail verdict.

CI Integration wires the event bus into build pipelines, producing structured logs the platform team can pipe into OpenTelemetry collectors. Production Monitoring closes the loop with dead-letter queues, circuit breakers, and priority queues. Standards Export and Multi-Project Federation complete the procurement story: RDF-class deliverables plus an 11-ecosystem federation registry demonstrate interoperability without runtime coupling.

Use-case detail

  • Use case 1 - Enterprise deployment: Platform engineer stands up a managed FCC instance with the docs-as-code pipeline; docs/for-professionals/enterprise-deployment.md.
  • Use case 2 - Governance and compliance: Compliance officer runs the EU AI Act auditor and quality-gate suite; docs/for-professionals/governance-compliance.md.
  • Use case 3 - CI integration: Platform engineer wires event bus, quality gates, and OpenTelemetry into CI; docs/for-professionals/integration-guide.md.
  • Use case 4 - Production monitoring: SRE subscribes to the event bus with a DLQ-aware consumer; hits EventBus plus circuit breakers.
  • Use case 5 - Standards export: Architect exports personas and knowledge graphs to RDF, OWL, SKOS, and JSON-LD; hits ModelFacade and serializers.
  • Use case 6 - Multi-project federation: Architect registers peer projects via FederationRegistry and VocabularyProviderPlugin; docs/for-professionals/security-review.md.

See also

  • Source: src/fcc/federation/registry.py, src/fcc/compliance/auditor.py
  • Source: src/fcc/objectmodel/facade.py, src/fcc/messaging/bus.py, src/fcc/messaging/dlq.py
  • Related class diagram: ../class-diagrams/federation.md
  • For audience tier: docs/for-professionals/index.md