Track Dynamic Registration Provenance
BOUNDARY-TRACK-DYNAMIC-REGISTRATION-PROVENANCE
Summary
Store stable source names, versions, paths, owners, or generated identifiers for extension, guest, generated-code, and config registrations. Provenance makes conflicts and failures diagnosable while avoiding sensitive source details.
Rule
Track provenance for registrations from extensions, guests, or generated code.
Why
When extensions, guests, generated code, or config register handlers, commands, routes, or tools, later conflicts and failures need to identify where each registration came from. Provenance turns an anonymous entry into a debuggable one.
Helps
- Makes dynamic systems auditable and easier to debug after registration conflicts or failures.
Limits
Do not store sensitive source details. Keep provenance to stable names, versions, paths, owners, or generated identifiers that support debugging.
Agent Instruction
Track provenance for extension, guest, generated-code, or config registrations so conflicts and
failures identify their source.Mechanisms
Supported by registration metadata, source IDs, version fields, conflict errors, diagnostics tables, and tests for duplicate or shadowed registrations.