Skip to content

Knowledge Federation Prompts

Six prompts for operators working across FCC's federation layer: NamespaceRegistry (11 ecosystems), EntityResolver, ChangeTracker, and FederatedKnowledgeGraph. These prompts demonstrate how to broker shared vocabularies between FCC and sibling projects (Athenium, Mnemosyne, AOME, CTO, Distiller, Sky-Parlour) via the VocabularyProviderPlugin contract shipped in v1.2.1.

Personas Used

Persona ID Full Name Category Role in Prompts
KB Knowledge Broker knowledge_graph Cross-namespace resolution
OA Ontology Architect knowledge_graph Schema/ontology design
FC Federation Coordinator knowledge_graph (champion-style) Cross-project governance
SDE Semantic Data Engineer data_engineering Extraction, mapping, loading

Prompt 1: Namespace Registry Expansion

Audience: Advanced Difficulty: intermediate Personas: FC, OA

Context

A new sibling project ("Calliope") wants to join the federation.

Prompt

FC leads; OA advises.

Find: inventory the existing 11 ecosystems in the NamespaceRegistry
and identify naming conventions, URI patterns, and change-tracker
subscriptions.

Create: draft a NamespaceRegistry entry for Calliope including
prefix, base URI, maintainer email, plugin dependencies, and the
set of shared vocabularies it provides. Ensure URI patterns do not
collide with any existing namespace.

Critique: OA to identify two potential semantic overlaps with
Mnemosyne that should be resolved before onboarding.

Expected Output

  • Registry YAML entry
  • Collision and overlap analysis

Prompt 2: Cross-Project Entity Resolution

Audience: Advanced Difficulty: advanced Personas: KB, SDE

Prompt

Resolve the entity "Customer" across FCC (core domain), Athenium
(market domain), and Mnemosyne (memory domain). Using EntityResolver,
produce a resolution report that:
- Lists each source's canonical definition
- Identifies shared attributes (identifier, name, lifecycle state)
- Flags non-overlapping attributes
- Proposes a canonical definition hosted under the `fcc:` namespace
- Records crosswalks in VocabularyMapping YAML

Expected Output

  • Resolution report
  • Canonical definition
  • VocabularyMapping YAML

Prompt 3: EntityResolver Disambiguation

Audience: Advanced Difficulty: advanced Personas: KB

Prompt

EntityResolver returned three candidates for the term "Event" with
confidence 0.82, 0.79, and 0.68 drawn from the messaging namespace,
the knowledge-graph namespace, and the distiller namespace. Describe
the disambiguation algorithm you would apply (context window,
persona-provided hints, namespace priority) and produce the final
decision with a reproducible tiebreaker rule.

Expected Output

  • Disambiguation algorithm write-up
  • Final decision with tiebreaker

Prompt 4: Federated Query Across Ecosystems

Audience: Advanced Difficulty: advanced Personas: SDE, KB

Prompt

Construct a federated SPARQL-style query that joins (a) FCC personas
tagged with risk-category "high," (b) Athenium market datasets owned
by the same stakeholder, and (c) Mnemosyne long-term memory of prior
audits for those personas. Return a table with persona id, linked
dataset, and last audit date. Explain how the FederatedKnowledgeGraph
dispatches sub-queries and reconciles results.

Expected Output

  • Federated query text
  • Execution-plan walkthrough

Prompt 5: ChangeTracker Review

Audience: Advanced Difficulty: intermediate Personas: FC

Prompt

Review the past 14 days of ChangeTracker entries across all
registered namespaces. Produce a change digest that groups entries
by impact tier (breaking/additive/cosmetic), names affected downstream
plugins, and proposes which changes warrant a federation-wide
announcement. Include a draft announcement for the single highest-
impact change.

Expected Output

  • Change digest
  • Draft announcement

Prompt 6: Vocabulary Contract Authoring

Audience: Advanced Difficulty: advanced Personas: OA, SDE

Prompt

Author a VocabularyProviderPlugin adapter that exposes the 175
packaged YAML mappings under `src/fcc/data/objectmodel/` to a sibling
project. Include the ABC methods (get_namespace, list_terms,
resolve_term), the plugin manifest, and three unit tests that
exercise the provider contract. Finish with a short rationale for
why this indirection avoids runtime imports between sister projects.

Expected Output

  • Adapter source
  • Manifest and tests
  • Architecture rationale

See Also

  • src/fcc/federation/ and src/fcc/knowledge/
  • v1.2.1 VocabularyProviderPlugin release notes
  • docs/tutorials/sample-prompts/federation-prompts.md