Registration & Ownership

Every consumer mod should establish one owner identity and use it consistently for content and subscriptions.

The runtime tests prove that the ExampleMod can register, look itself up again, read dependency metadata and receive an owner context. They also prove ownership isolation in the custom-ability path: another registered owner can inspect content but cannot remove content owned by community.example.

Ownership rules

• Treat the registered owner ID as persistent public identity, not a display name.
• Register custom content under the same owner namespace.
• Do not attempt to deactivate or mutate another mod's content.
• Keep owner-scoped handles/disposables and release them through the documented lifecycle.

This design prevents two mods from accidentally claiming the same custom identity or cleaning up each other's registrations.