On this page
Connect Independently Owned Subsystems๏
Reader Question๏
How can two subsystems keep separate registries while sharing selected capabilities?
Short Answer๏
Give each subsystem its own spellbook and conduit, enable dynamic posture, link the
conduits, and let the consumer pull selected spells across the contract boundary. A
SpellContract can leave a dependency socket intentionally unresolved until that link
provides its provider.
Representative Shape๏
platform = platform_book.conjure(dynamic=True, name="platform")
services = services_book.conjure(name="services")
platform.link(services)
services.add_spell_to_contract(
spell_id=config_id,
conduit=platform,
permissions="create",
)
services.validate_contracts_and_define()
service = services.meld("Service")
The provider keeps ownership. The borrower receives only the contracted visibility and permissions it requested. Links remain inside one aetheric frame.
Why This Design Is Strong๏
Subsystems compile, configure, and clean up independently.
Sharing is explicit and consumer-pulled.
Permission and contract state remain inspectable.
Late binding connects categories without forcing provider imports into consumers.
Tradeoffs๏
Dynamic composition requires ordering: both conduits exist, the link is established, the consumer requests providers, and contract validation runs before use. That choreography buys an explicit boundary instead of a single registry where every subsystem sees everything.
Where to Go Next๏
Isolate worlds for boundaries that must not link.
Runtime model for ownership details.
Evidence: