Extension Guide

Extension Guide

Use the API owned by the plugin you need to extend.

Common paths

• Derive a configuration/profile Data Asset for authored policy.
• Implement a shared IPGX* interface for an object capability.
• Derive from the Core event-handler base for tag-selected behavior.
• Register a tagged asset or observable through its owning registry.
• Implement an audio backend or loading strategy through the domain base class.
• Implement a save provider or register a save migration with PGXSave.
• Register a Scaffold template with the public template registry.
• Add documentation roots through PGXDocs configuration.

Dependency rule

If an optional sibling feature only needs to receive state, prefer a Core message contract over adding a runtime module dependency. Keep editor integrations in an Editor module and graph-only nodes in an UncookedOnly module.

Preview rule

Before depending on an extension symbol, verify that it exists in the selected tag's public headers. PGXTutorials currently has no stable public extension headers, and automatic discovery of documentation providers is not a documented guarantee in this preview.