Integrations
Review draft. This source page has not completed website editorial and release-specific verification.
All integrations are optional. Knowledge core remains usable when every bridge is absent.
Dialogue Director
Section titled “Dialogue Director”Dialogue access is an optional canonical DirectorBridge integration; see its integration documentation for provider behavior. It resolves the bound ParticipantObject and queries its UKnowledgeComponent; the former mirrored pairwise integration has been retired. Knowledge remains standalone and authoritative for its data and gameplay APIs, with no ownership or public-contract change.
Save Game Director
Section titled “Save Game Director”Knowledge persistence adaptation is available through optional DirectorBridge modules. Knowledge core retains snapshot capture, validation, restore, and dormant Subject authority, without a SaveGame Director dependency. The ActorComponents pairwise SaveGame bridge product is retired.
SignalBus
Section titled “SignalBus”The canonical optional SignalBus integration is provided by DirectorBridge and observes committed Knowledge events. It has no inbound Knowledge mutation path, and a disclosure event does not grant recipient Knowledge. Knowledge core remains transport-independent.
Advanced Debug Override changes do not publish these canonical routes. Restore Debug Baseline also does not synthesize acquisition or removal events; the editor-only debug notification is reserved for Inspector and editor diagnostics.