Skip to content

Platform Capability Messages

backend-core projects Fuseki-backed platform capability facts onto the NATS system subject platform.capability.changed.v1 for the platform.messaging.update-system capability.

Source of truth:

  • Fuseki graph: https://agentarmy.dev/graphs/platform/capabilities
  • SPARQL source: capability announcements and capability-announcement-channel relators
  • Event schema: contracts/platform-capability-event.schema.json
  • Example event: contracts/platform-capability-event.example.json

Publish path:

FUSEKI_URL=http://localhost:3030 \
FUSEKI_DATASET=knowledge \
NATS_URL=nats://localhost:4222 \
python scripts/publish_platform_capabilities.py

Offline doctor:

python scripts/platform_capability_projector_doctor.py

Subscriber behavior for coding-agent teams:

  • Subscribe to platform.capability.changed.v1.
  • Validate every payload against contracts/platform-capability-event.schema.json.
  • Use data.capabilityId as the MECE capability key.
  • Use data.ontology.graphIri, data.ontology.capabilityIri, and data.ontology.announcementIri to recover the Fuseki source facts.
  • Use data.adoption.hubRollupIssue and data.adoption.trackIssues to find the durable GitHub evidence lane while HVFS adoption is still in transition.
  • Treat duplicate events with the same id or identical data fingerprint as idempotent replays.

Failure behavior:

  • Fuseki query errors fail the publish run before any message is emitted.
  • Invalid ontology rows fail projection before publication.
  • Invalid CloudEvents fail schema validation before publication.
  • NATS publish errors fail the run and should be retried by the scheduler or calling workflow.