# 🟡 Intermediate examples

**37 saved lessons.** Follow their order or choose a topic that answers your question.

[Open the Intermediate guide](../../intermediate/index.md) · [All examples](../index.md)

<ul class="example-list">
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;]" data-search="scan bind decorator declarative binding - tag classes where they live with @md.scan_bind, then register the whole module in one scan() call. the decorator stores intent only; nothing binds until scan time. md.scan_bind, md.spellbook.scan, md.existence, md.permissions registration"><span class="example-level">🟡 Intermediate · 01</span><h3><a href="01-scan-bind-decorator.html">Scan bind decorator</a></h3><p>Declarative binding - tag classes where they live with @md.scan_bind, then register the whole module in one scan() call. The decorator stores intent only; nothing binds until scan time.</p><div><span class="example-topic">Registration</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;, &quot;Connections&quot;]" data-search="spellbinder full chain every link in the fluent chain, one binder reused across registrations: existence (explicit and shorthand), permissions, spellframe grouping, binding names, and constructor kwargs. md.spellbinder full chain, md.existence, spellframes registration connections"><span class="example-level">🟡 Intermediate · 02</span><h3><a href="02-spellbinder-full-chain.html">Spellbinder full chain</a></h3><p>Every link in the fluent chain, one binder reused across registrations: existence (explicit and shorthand), permissions, spellframe grouping, binding names, and constructor kwargs.</p><div><span class="example-topic">Registration</span><span class="example-topic">Connections</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;]" data-search="registration hooks hooks ride the registration, not the call site - pre, activation, and post hooks attach through the fluent chain and fire around instance creation. the printed order is the documentation; the 3.14t run records the exact firing points. md.spellbinder.with_pre_hook / with_activation_hook / with_post_hook registration"><span class="example-level">🟡 Intermediate · 03</span><h3><a href="03-registration-hooks.html">Registration hooks</a></h3><p>Hooks ride the registration, not the call site - pre, activation, and post hooks attach through the fluent chain and fire around instance creation. The printed order IS the documentation;…</p><div><span class="example-topic">Registration</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[]" data-search="spellspace scoped resolution spellspaces are entered resolution rooms - one conduit can open many, and unique_per_spell_space pins one instance per room: stable inside a space, separate across spaces. md.conduit.enter_spellspace, md.spellspace, md.existence.unique_per_spell_space"><span class="example-level">🟡 Intermediate · 04</span><h3><a href="04-spellspace-scoped-resolution.html">Spellspace scoped resolution</a></h3><p>Spellspaces are entered resolution rooms - one conduit can open many, and unique_per_spell_space pins one instance per room: stable inside a space, separate across spaces.</p><div></div></li>
<li class="example-item" data-level="intermediate" data-topics="[]" data-search="existence unique per conduit lineage unique_per_conduit_lineage - one instance per family: the root and every lesser descendant share the same object. a second family would need its own book (one book conjures one root - beginner law), so the lineage boundary is the book boundary. md.existence.unique_per_conduit_lineage, create_lesser_conduit"><span class="example-level">🟡 Intermediate · 05</span><h3><a href="05-existence-unique-per-conduit-lineage.html">Existence unique per conduit lineage</a></h3><p>unique_per_conduit_lineage - one instance per FAMILY: the root and every lesser descendant share the same object. A second family would need its own book (one book conjures ONE root -…</p><div></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;, &quot;Agent rooms &amp; codegen&quot;, &quot;Concurrency&quot;]" data-search="spell metadata kwargs spell metadata via bind kwargs (landed 2026-07-19): any extra keyword on bind() threads into the spell&#x27;s own kwargs channel and lands on spell.metadata - tag your registrations with ownership, tiers, or agent breadcrumbs. native bind values are unstealable: declared parameters capture their names before **kwargs collects. bind(**extras) -&gt; spell.metadata, find_spell_by_id registration agent rooms &amp; codegen concurrency"><span class="example-level">🟡 Intermediate · 06</span><h3><a href="06-spell-metadata-kwargs.html">Spell metadata kwargs</a></h3><p>Spell metadata via bind kwargs (landed 2026-07-19): any extra keyword on bind() threads into the Spell&#x27;s own kwargs channel and lands on spell.metadata - tag your registrations with…</p><div><span class="example-topic">Registration</span><span class="example-topic">Agent rooms &amp; codegen</span><span class="example-topic">Concurrency</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Resolution&quot;, &quot;Lifetimes &amp; cleanup&quot;]" data-search="lesser conduits child scopes lesser conduits - lightweight child scopes grown from a root with create_lesser_conduit(). a lesser conduit rides its root&#x27;s world: it resolves the same spells without being a second root (one book still conjures one root). lessers are unnamed by design; naming and upgrade_to_normal() belong to dynamic mode (lesson 21+). teardown stays an explicit verb - cleanup() is yours to call. create_lesser_conduit, meld through a child scope, explicit cleanup() resolution lifetimes &amp; cleanup"><span class="example-level">🟡 Intermediate · 07</span><h3><a href="07-lesser-conduits-child-scopes.html">Lesser conduits child scopes</a></h3><p>Lesser conduits - lightweight CHILD SCOPES grown from a root with create_lesser_conduit(). A lesser conduit rides its root&#x27;s world: it resolves the same spells without being a second root…</p><div><span class="example-topic">Resolution</span><span class="example-topic">Lifetimes &amp; cleanup</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;, &quot;Resolution&quot;, &quot;Configuration&quot;, &quot;Research &amp; change&quot;]" data-search="spell override construction two honest ways to construct with configuration: a factory that closes over its config (bind-site), and override at meld - a flat dict of keyword overrides for the melded spell&#x27;s own constructor. simple and top-level on purpose; targeting objects deeper in the graph is an advanced-tier lesson. (bind(**kwargs) is a different channel entirely: it lands on spell.metadata - lesson 06.) factory spells, meld(override={...}) registration resolution configuration research &amp; change"><span class="example-level">🟡 Intermediate · 08</span><h3><a href="08-spell-override-construction.html">Spell override construction</a></h3><p>Two honest ways to construct with configuration: a factory that closes over its config (bind-site), and override at meld - a FLAT dict of keyword overrides for the melded spell&#x27;s OWN…</p><div><span class="example-topic">Registration</span><span class="example-topic">Resolution</span><span class="example-topic">Configuration</span><span class="example-topic">Research &amp; change</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Connections&quot;]" data-search="permissions block sharing block, the third permission - declared today, felt when sharing and contracting exist (intermediate+). a beginner learns the word and that the book accepts it. md.permissions.block (declaration only) connections"><span class="example-level">🟡 Intermediate · 09</span><h3><a href="09-permissions-block-sharing.html">Permissions block sharing</a></h3><p>block, the third permission - declared today, felt when sharing and contracting exist (intermediate+). A beginner learns the word and that the book accepts it.</p><div><span class="example-topic">Connections</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;]" data-search="spellbinder fluent basics the fluent registration hand - spellbinder reads like a sentence: bind(x).as_unique().named(&quot;primary&quot;).finalize(). finalize() returns the spell id string and resets the binder for the next registration. md.spellbinder, md.spellbook, finalize() -&gt; str registration"><span class="example-level">🟡 Intermediate · 10</span><h3><a href="10-spellbinder-fluent-basics.html">Spellbinder fluent basics</a></h3><p>The fluent registration hand - SpellBinder reads like a sentence: bind(X).as_unique().named(&quot;primary&quot;).finalize(). finalize() returns the spell id string and resets the binder for the next…</p><div><span class="example-topic">Registration</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;, &quot;Resolution&quot;, &quot;Connections&quot;]" data-search="permissions linking vocabulary permissions are linking vocabulary (owner ruling): read / create / block govern what linked conduits may do with your bindings in dynamic worlds - they are not a local-meld concept at all. read = resolve-only across links; create implies read; block stops sharing entirely. md.permissions.read registration resolution connections"><span class="example-level">🟡 Intermediate · 11</span><h3><a href="11-permissions-linking-vocabulary.html">Permissions linking vocabulary</a></h3><p>Permissions are LINKING vocabulary (owner ruling): read / create / block govern what LINKED conduits may do with your bindings in dynamic worlds - they are not a local-meld concept at all.…</p><div><span class="example-topic">Registration</span><span class="example-topic">Resolution</span><span class="example-topic">Connections</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;, &quot;Resolution&quot;]" data-search="bind lambda spells even a lambda is a spell - it must carry a binding_name (the law the runtime enforces); melds address it by (frame, name) because binding_name alone is never an address. callable = unique. bind(spell=&lt;lambda&gt;), binding_name, callable-unique law registration resolution"><span class="example-level">🟡 Intermediate · 12</span><h3><a href="12-bind-lambda-spells.html">Bind lambda spells</a></h3><p>Even a lambda is a spell - it MUST carry a binding_name (the law the runtime enforces); melds address it by (frame, name) because binding_name alone is never an address. Callable = unique.</p><div><span class="example-topic">Registration</span><span class="example-topic">Resolution</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;]" data-search="spell ids and lookup bind() answers with the spell&#x27;s id string - keep it, and the book will hand the living spell record back on request. bind() -&gt; str, md.spellbook.find_spell_by_id, md.spell registration"><span class="example-level">🟡 Intermediate · 13</span><h3><a href="13-spell-ids-and-lookup.html">Spell ids and lookup</a></h3><p>bind() answers with the spell&#x27;s id string - keep it, and the book will hand the living Spell record back on request.</p><div><span class="example-topic">Registration</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;, &quot;Inspection&quot;]" data-search="introspect the book the book is inspectable - the spells mapping hands back every registration as spellindex -&gt; spell, the system&#x27;s two domain nouns, straight off the root namespace. md.spellbook.spells, md.spellindex, md.spell registration inspection"><span class="example-level">🟡 Intermediate · 14</span><h3><a href="14-introspect-the-book.html">Introspect the book</a></h3><p>The book is inspectable - the spells mapping hands back every registration as SpellIndex -&gt; Spell, the system&#x27;s two domain nouns, straight off the root namespace.</p><div><span class="example-topic">Registration</span><span class="example-topic">Inspection</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Resolution&quot;]" data-search="constructor di by annotation the di heart - annotate a constructor parameter with a bound class and melder injects it. dependencies resolve recursively; you meld the top and the graph assembles itself. type-hint constructor di (single_by_annotation) resolution"><span class="example-level">🟡 Intermediate · 15</span><h3><a href="15-constructor-di-by-annotation.html">Constructor di by annotation</a></h3><p>THE DI heart - annotate a constructor parameter with a bound class and melder injects it. Dependencies resolve recursively; you meld the top and the graph assembles itself.</p><div><span class="example-topic">Resolution</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;, &quot;Resolution&quot;]" data-search="spellmap defaults spellmap - the declarative di placeholder. as a constructor default it declares exactly which spell fills the parameter, including frame + binding_name targeting. exactly-one law: ambiguous or missing targets fail at conjure, not at runtime. md.spellmap as a constructor default registration resolution"><span class="example-level">🟡 Intermediate · 16</span><h3><a href="16-spellmap-defaults.html">Spellmap defaults</a></h3><p>SpellMap - the declarative DI placeholder. As a constructor DEFAULT it declares exactly which spell fills the parameter, including frame + binding_name targeting. Exactly-one law: ambiguous…</p><div><span class="example-topic">Registration</span><span class="example-topic">Resolution</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;, &quot;Resolution&quot;]" data-search="collection di collection di - annotate list[shape] and receive every bound implementation in registration order. the plugin pattern in one annotation; zero matches is a legal empty list. list[frametype] collection injection registration resolution"><span class="example-level">🟡 Intermediate · 17</span><h3><a href="17-collection-di.html">Collection di</a></h3><p>Collection DI - annotate list[Shape] and receive EVERY bound implementation in registration order. The plugin pattern in one annotation; zero matches is a legal empty list.</p><div><span class="example-topic">Registration</span><span class="example-topic">Resolution</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Resolution&quot;, &quot;Inspection&quot;, &quot;Agent rooms &amp; codegen&quot;]" data-search="live creation probe &quot;is it already alive?&quot; without creating it - has_live_creation mirrors meld&#x27;s exact lookup but stops before construction. doc-canon: the no-create probe for agents and diagnostics. conduit.has_live_creation / describe_live_creation_status resolution inspection agent rooms &amp; codegen"><span class="example-level">🟡 Intermediate · 18</span><h3><a href="18-live-creation-probe.html">Live creation probe</a></h3><p>&quot;Is it already alive?&quot; without creating it - has_live_creation mirrors meld&#x27;s exact lookup but stops before construction. Doc-canon: the no-create probe for agents and diagnostics.</p><div><span class="example-topic">Resolution</span><span class="example-topic">Inspection</span><span class="example-topic">Agent rooms &amp; codegen</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Configuration&quot;, &quot;Agent rooms &amp; codegen&quot;, &quot;Research &amp; change&quot;]" data-search="spellbook configuration basics spellbookconfiguration - the book&#x27;s policy object. with_defaults() is easy mode; set_property tunes the knobs; conjure validates and freezes it (frozen config refuses mutation - fail fast, not drift). md.spellbookconfiguration, set_property, the freeze law configuration agent rooms &amp; codegen research &amp; change"><span class="example-level">🟡 Intermediate · 19</span><h3><a href="19-spellbook-configuration-basics.html">Spellbook configuration basics</a></h3><p>SpellbookConfiguration - the book&#x27;s policy object. with_defaults() is easy mode; set_property tunes the knobs; conjure VALIDATES AND FREEZES it (frozen config refuses mutation - fail fast,…</p><div><span class="example-topic">Configuration</span><span class="example-topic">Agent rooms &amp; codegen</span><span class="example-topic">Research &amp; change</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Configuration&quot;]" data-search="phase scheduler knobs conjure runs the compile pipeline (phases 1-11) through the phasescheduler - a worker pool with a barrier timeout. two config knobs tune it: workers per spellbook and the barrier timeout. slow ci boxes raise the timeout; tiny worlds run one worker. phase_scheduler_workers_per_spellbook, phase_scheduler_barrier_timeout_milliseconds configuration"><span class="example-level">🟡 Intermediate · 20</span><h3><a href="20-phase-scheduler-knobs.html">Phase scheduler knobs</a></h3><p>Conjure runs the compile pipeline (phases 1-11) through the PhaseScheduler - a worker pool with a barrier timeout. Two config knobs tune it: workers per spellbook and the barrier timeout.…</p><div><span class="example-topic">Configuration</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Resolution&quot;, &quot;Configuration&quot;, &quot;Connections&quot;]" data-search="dynamic linking basics dynamic mode end to end under the settle-then-inherit law: 1) a fresh world has no mode yet. the first conjure(dynamic=true) settles the world dynamic - and the posture locks. 2) every later book just attaches: a plain conjure() inherits the world&#x27;s mode. you never repeat the flag to stay dynamic. 3) link() opens a contract between two named conduits, and add_spell_to_contract shares one spell across it. conjure(dynamic=true) settlement, plain-conjure inheritance, link, add_spell_to_contract, meld resolution configuration connections"><span class="example-level">🟡 Intermediate · 21</span><h3><a href="21-dynamic-linking-basics.html">Dynamic linking basics</a></h3><p>Dynamic mode END TO END under the settle-then-inherit law: 1) A fresh world has no mode yet. The FIRST conjure(dynamic=True) SETTLES the world dynamic - and the posture locks. 2) Every…</p><div><span class="example-topic">Resolution</span><span class="example-topic">Configuration</span><span class="example-topic">Connections</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Resolution&quot;, &quot;Connections&quot;]" data-search="permissions create vs read permissions live - they are the sharing policy on a contract. &quot;create&quot; lets the borrower construct/resolve fully; &quot;read&quot; is resolve-only across the link. this is where the vocabulary from the cheatsheet finally does something. add_spell_to_contract(permissions=&quot;read&quot;/&quot;create&quot;) resolution connections"><span class="example-level">🟡 Intermediate · 22</span><h3><a href="22-permissions-create-vs-read.html">Permissions create vs read</a></h3><p>Permissions LIVE - they are the sharing policy on a contract. &quot;create&quot; lets the borrower construct/resolve fully; &quot;read&quot; is resolve-only across the link. This is where the vocabulary from…</p><div><span class="example-topic">Resolution</span><span class="example-topic">Connections</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Connections&quot;]" data-search="transfer of ownership ownership is transferable (dynamic mode) - a spell&#x27;s stewardship moves to another conduit with an auditable preflight summary. creations can move too; contracts unshare; lineage revalidates. transfer_spell_ownership connections"><span class="example-level">🟡 Intermediate · 23</span><h3><a href="23-transfer-of-ownership.html">Transfer of ownership</a></h3><p>Ownership is transferable (dynamic mode) - a spell&#x27;s stewardship moves to another conduit with an auditable preflight summary. Creations can move too; contracts unshare; lineage revalidates.</p><div><span class="example-topic">Connections</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Connections&quot;]" data-search="conduit cloud the conduitcloud - the world&#x27;s phone book for dynamic named roots. reached publicly from any conduit; look peers up by name instead of passing references around. conduit.get_conduit_cloud, has_conduit_name, get_conduit connections"><span class="example-level">🟡 Intermediate · 24</span><h3><a href="24-conduit-cloud.html">Conduit cloud</a></h3><p>The ConduitCloud - the world&#x27;s phone book for dynamic NAMED roots. Reached publicly from any conduit; look peers up by name instead of passing references around.</p><div><span class="example-topic">Connections</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Connections&quot;]" data-search="clusters unique per cluster clusters - named groups of dynamic conduits that auto-share cluster-scoped spells. unique_per_conduit_cluster finally comes alive: one instance per cluster, shared by every member. (this completes the declaration parked in the expert tier&#x27;s example 01.) create_cluster, add_conduit_to_cluster, existence=&quot;unique_per_conduit_cluster&quot; connections"><span class="example-level">🟡 Intermediate · 25</span><h3><a href="25-clusters-unique-per-cluster.html">Clusters unique per cluster</a></h3><p>Clusters - named groups of dynamic conduits that AUTO-SHARE cluster-scoped spells. unique_per_conduit_cluster finally comes alive: one instance per cluster, shared by every member. (This…</p><div><span class="example-topic">Connections</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;, &quot;Resolution&quot;, &quot;Connections&quot;]" data-search="conduit categories as factories conduit categories are your factory layer. instead of writing an abstract factory in front of your scopes, name conduits after the resolution ideas your app already has - &quot;platform&quot;, &quot;services&quot;, &quot;workflows&quot; - and late-bind the dependencies between categories with spellcontract sockets. order of operations is the law (owner ruling 2026-07-20). per dependency edge, in this exact order: 1) conjure the provider conduit 2) conjure the consumer conduit (the spellcontract side) 3) link() - only after both conduits are built 4) the consumer pulls the provider spell into the contract 5) meld after the fact - completing the late binding for that world&#x27;s products assemble the chain edge by edge, in dependency order. no factory objects exist anywhere - the conduit names are the factory types. the arc: this is beginner lesson 25 one level up. spellframes categorize spells within one world; conduits categorize worlds - each category gains an owner, and permissions + contracts + links set the resolution conditions at the category boundary. md.spellcontract, link, add_spell_to_contract, named category conduits registration resolution connections"><span class="example-level">🟡 Intermediate · 26</span><h3><a href="26-conduit-categories-as-factories.html">Conduit categories as factories</a></h3><p>Conduit CATEGORIES are your factory layer. Instead of writing an abstract factory in front of your scopes, NAME conduits after the resolution ideas your app already has - &quot;platform&quot;,…</p><div><span class="example-topic">Registration</span><span class="example-topic">Resolution</span><span class="example-topic">Connections</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Resolution&quot;, &quot;Connections&quot;]" data-search="sever link sever_link - the undo of the whole dynamic arc. contracts ride links, so when the link dies, everything shared across it dies with it: the borrower loses resolution of every pulled spell on its very next meld. nothing is torn down eagerly - the owner&#x27;s live instances stay alive in the owner&#x27;s world; what the borrower loses is the right to resolve them. severing an already-severed pair refuses (there is no contract left to remove). sever_link, post-sever meld refusal resolution connections"><span class="example-level">🟡 Intermediate · 27</span><h3><a href="27-sever-link.html">Sever link</a></h3><p>sever_link - the UNDO of the whole dynamic arc. Contracts ride links, so when the link dies, everything shared across it dies with it: the borrower loses resolution of every pulled spell on…</p><div><span class="example-topic">Resolution</span><span class="example-topic">Connections</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[]" data-search="upgrade to normal upgrade_to_normal - a lesser conduit grows up in place. lessers are unnamed child scopes (lesson 07); in a dynamic world one can be promoted to a full named citizen: registered in the world, discoverable by name in the cloud, able to do everything a normal conduit does. the promotion keeps what the child already built - its creations ride through the upgrade untouched. dynamic-only verb: in a static world the same call refuses. create_lesser_conduit, upgrade_to_normal, cloud name lookup after promotion"><span class="example-level">🟡 Intermediate · 28</span><h3><a href="28-upgrade-to-normal.html">Upgrade to normal</a></h3><p>upgrade_to_normal - a lesser conduit GROWS UP in place. Lessers are unnamed child scopes (lesson 07); in a dynamic world one can be promoted to a full named citizen: registered in the…</p><div></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Resolution&quot;, &quot;Lifetimes &amp; cleanup&quot;]" data-search="scoped cleanup lesser conduits scopes that end. a lesser conduit is a scope you can throw away: build one for a job, meld what the job needs, then cleanup() the child - its per-conduit creations are disposed through the book&#x27;s disposal vocabulary, and the root keeps working untouched. the lifecycle law: with a di runtime you own the lifecycles. the runtime holds references to what it built, so the gc cannot free what the world still holds - cleanup() is how memory comes back. (beginner lesson 41 proves this with a weakref; here it becomes a working pattern.) create_lesser_conduit as a disposable scope, conduit.cleanup() on the child only, disposal_method_names firing scope-locally resolution lifetimes &amp; cleanup"><span class="example-level">🟡 Intermediate · 29</span><h3><a href="29-scoped-cleanup-lesser-conduits.html">Scoped cleanup lesser conduits</a></h3><p>Scopes that END. A lesser conduit is a scope you can THROW AWAY: build one for a job, meld what the job needs, then cleanup() the child - its per-conduit creations are disposed through the…</p><div><span class="example-topic">Resolution</span><span class="example-topic">Lifetimes &amp; cleanup</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;, &quot;Resolution&quot;, &quot;Lifetimes &amp; cleanup&quot;, &quot;Configuration&quot;, &quot;Inspection&quot;]" data-search="config disposal and the frozen law spellbookconfiguration, knob by knob - part 1: disposal. two set-once properties describe teardown policy: disposal (bool) - stored flag; matched names drive calls disposal_method_names (list) - the ordered book-wide vocabulary enforce_priority_disposal_methods places the book block first when true or last when false (default). the book owns shared names in both modes. both are idempotent properties: set once, immutable after - the teardown story of a world must not change mid-flight. and the whole configuration freezes at conjure: any set_property after that refuses. configuration is a pre-flight surface, period. spellbookconfiguration.set_property, with_enforce_priority_disposal_methods, bind, meld, cleanup registration resolution lifetimes &amp; cleanup configuration inspection"><span class="example-level">🟡 Intermediate · 30</span><h3><a href="30-config-disposal-and-the-frozen-law.html">Config disposal and the frozen law</a></h3><p>SpellbookConfiguration, knob by knob - part 1: DISPOSAL. Two set-once properties describe teardown policy: disposal (bool) - stored flag; matched names drive calls disposal_method_names…</p><div><span class="example-topic">Registration</span><span class="example-topic">Resolution</span><span class="example-topic">Lifetimes &amp; cleanup</span><span class="example-topic">Configuration</span><span class="example-topic">Inspection</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;, &quot;Lifetimes &amp; cleanup&quot;, &quot;Configuration&quot;, &quot;Concurrency&quot;]" data-search="spellbook config defined spellbookconfiguration defined - the core settings you can set, what each one means, and the four laws that guard them. this is the book&#x27;s policy object: it decides teardown and how hard the conjure pipeline works. nothing here is exotic - explicit values, four rules. the core settings disposal (bool) stored configuration metadata; matched method names drive disposal calls. disposal_method_names (list[str]) the teardown vocabulary - the method names that mean &quot;clean yourself up&quot; in this system. cleanup calls whichever of them each object actually has (beginner 08 showed it firing). enforce_priority_disposal_methods (bool, default false) place the matching book block last (false) or first (true). shared names always keep the book&#x27;s order; spell-only names keep their own order. set this before binding. phase_scheduler_workers_per_spellbook (int) how many worker threads run the conjure pipeline. conjure compiles and validates every spell in phases - more workers means more of that in parallel. phase_scheduler_barrier_timeout_milliseconds (int) how long a phase barrier waits for a straggler before refusing loudly. this is the anti-hang knob: a broken spell fails your startup with an error, never a frozen process. the four laws 1) closed registry - an unknown key refuses. no typo silently becomes a setting. 2) idempotent pair - the two disposal items are set-once. a world&#x27;s teardown story must not change mid-flight. 3) freeze - conjure validates and freezes the whole object. configuration is a pre-flight surface, period. 4) completion - hand a book your configuration and you own completing it. with_defaults() is easy mode; a bare config refuses at conjure-time validation. core configuration settings, the four refusal laws registration lifetimes &amp; cleanup configuration concurrency"><span class="example-level">🟡 Intermediate · 31</span><h3><a href="31-spellbook-config-defined.html">Spellbook config defined</a></h3><p>SpellbookConfiguration DEFINED - the core settings you can set, what each one means, and the four laws that guard them. This is the book&#x27;s policy object: it decides teardown and how hard…</p><div><span class="example-topic">Registration</span><span class="example-topic">Lifetimes &amp; cleanup</span><span class="example-topic">Configuration</span><span class="example-topic">Concurrency</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Resolution&quot;, &quot;Configuration&quot;]" data-search="config meld hooks spellbookconfiguration hooks, family 1: the meld pipeline. add_hook(spellbook_id, name, fn) registers callbacks keyed to a book - the configuration can serve many books, so hooks say whose melds they watch. two hook points: on_meld_pre_resolve - before resolution on_meld_post_resolve - after the instance is handed back hooks observe; they do not replace resolution. add_hook, on_meld_pre_resolve, on_meld_post_resolve resolution configuration"><span class="example-level">🟡 Intermediate · 32</span><h3><a href="32-config-meld-hooks.html">Config meld hooks</a></h3><p>SpellbookConfiguration hooks, family 1: the MELD PIPELINE. add_hook(spellbook_id, name, fn) registers callbacks keyed to a BOOK - the configuration can serve many books, so hooks say whose…</p><div><span class="example-topic">Resolution</span><span class="example-topic">Configuration</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Lifetimes &amp; cleanup&quot;, &quot;Configuration&quot;]" data-search="config conduit lifecycle hooks spellbookconfiguration hooks, family 2: the conduit lifecycle. five moments of a conduit&#x27;s life are observable: on_conduit_pre_created / on_conduit_post_created / on_conduit_activated at conjure, and on_conduit_cleanup_start / on_conduit_cleanup_complete at the end. register before conjure; watch the whole life. conduit lifecycle hooks, firing order lifetimes &amp; cleanup configuration"><span class="example-level">🟡 Intermediate · 33</span><h3><a href="33-config-conduit-lifecycle-hooks.html">Config conduit lifecycle hooks</a></h3><p>SpellbookConfiguration hooks, family 2: the CONDUIT LIFECYCLE. Five moments of a conduit&#x27;s life are observable: on_conduit_pre_created / on_conduit_post_created / on_conduit_activated at…</p><div><span class="example-topic">Lifetimes &amp; cleanup</span><span class="example-topic">Configuration</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Configuration&quot;, &quot;Connections&quot;]" data-search="config link and contract hooks spellbookconfiguration hooks, families 3+4: linking and contracts - the dynamic arc becomes observable. register on the owner book and watch its side of the story: on_conduit_post_link - a link opened on_contract_created - a spell entered a contract on_contract_removed - it left on_conduit_post_unlink - the link died (lesson 27&#x27;s sever) this closes the loop: everything lessons 21-27 do, these hooks see. linking + contract hooks across link -&gt; pull -&gt; sever configuration connections"><span class="example-level">🟡 Intermediate · 34</span><h3><a href="34-config-link-and-contract-hooks.html">Config link and contract hooks</a></h3><p>SpellbookConfiguration hooks, families 3+4: LINKING and CONTRACTS - the dynamic arc becomes observable. Register on the owner book and watch its side of the story: on_conduit_post_link - a…</p><div><span class="example-topic">Configuration</span><span class="example-topic">Connections</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;, &quot;Lifetimes &amp; cleanup&quot;, &quot;Configuration&quot;, &quot;Agent rooms &amp; codegen&quot;, &quot;Research &amp; change&quot;]" data-search="one config every book one spellbook configuration shared by every book. when several books make up one subsystem, per-book configs drift - one book&#x27;s teardown vocabulary says &quot;close&quot;, another forgot it. the fix is one spellbookconfiguration for the whole subsystem. know which object you are talking about. a frame has two: * the frame posture (aethericframeconfiguration) - narrow: system state, ai-native, rift, the devops brakes. it is shared with every book on the frame already, by default, with no opt-in. the frame mints exactly one and every spellbook only borrows that reference. set posture through any one book and every book on that frame reads it. * the rich config (spellbookconfiguration) - wide: disposal, disposal method names, scheduler workers, barrier timeout, singleton specialization. this one is per-book by default. two books on the same frame mint two separate ones. this lesson is about making the rich one shared. two shapes: shape 1 - manual share (fully public, works today, shown below): 1. build one spellbookconfiguration for the frame 2. set the policy on it once 3. hand the same object to every spellbook you construct every book now reads one policy, by reference. the first conjure freezes that object; every later book&#x27;s conjure re-enters the freeze and locks against the same object. shape 2 - frame-owned share (the frame holds the config and later books adopt it with nothing passed). the machinery is complete and it takes exactly two things, in this order: 1. the switch - the frame posture must carry shared_framewide_spellbook_configuration=true. every sharing path early-outs while it is false. it must be flipped before the frame&#x27;s first conjure, because the posture freezes on that first bind and the switch is refused once frozen. 2. publication - one book binds its rich config to the frame. two doors do this, whichever runs first: configure_aether_ frame(), and conjure() itself (conjure freezes and binds whenever the book is not already locked). first one wins. then every book constructed after that adopts the frame-owned object at construction and reports is_configuration_locked() true; a book that already existed converges at its own conjure, swapping to the shared object and cleaning up its local one. handing a different config to a later book on that frame is refused. adoption is total - no per-book override - and a book&#x27;s cleanup() leaves the shared object alone. honest gap: shape 2 has no public switch today. nothing in the public api sets shared_framewide_spellbook_configuration - every construction site in the runtime passes false or omits it, and no spellbook door exposes the retained posture. so shape 1 is the answer to &quot;one config for every book&quot; until a door exists. the probes pin shape 2&#x27;s machinery through the private seam so it cannot rot while it waits. one configuration object across multiple books registration lifetimes &amp; cleanup configuration agent rooms &amp; codegen research &amp; change"><span class="example-level">🟡 Intermediate · 35</span><h3><a href="35-one-config-every-book.html">One config every book</a></h3><p>ONE SPELLBOOK CONFIGURATION SHARED BY EVERY BOOK. When several books make up one subsystem, per-book configs drift - one book&#x27;s teardown vocabulary says &quot;close&quot;, another forgot it. The fix…</p><div><span class="example-topic">Registration</span><span class="example-topic">Lifetimes &amp; cleanup</span><span class="example-topic">Configuration</span><span class="example-topic">Agent rooms &amp; codegen</span><span class="example-topic">Research &amp; change</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;, &quot;Resolution&quot;, &quot;Connections&quot;, &quot;Research &amp; change&quot;]" data-search="late binding with spellcontract spellcontract - the late-bound socket. a spellmap says &quot;resolve this from my book&quot; and must be satisfiable at conjure. a spellcontract says &quot;someone will hand me this later&quot;, and stays open until a linked conduit supplies the provider. that is the difference: spellmap is a lookup, spellcontract is a promise. the socket closes with normal verbs only - link, grant, meld. nothing reaches into another book; the provider conduit grants the spell across the link and the consumer melds as usual. contracts are dynamic-mode only. in an automatic world phase 4 refuses them outright, which is why this lesson settles a dynamic world first. md.spellcontract(spellframe=..., binding_name=...), conduit.link(...), conduit.add_spell_to_contract(...) registration resolution connections research &amp; change"><span class="example-level">🟡 Intermediate · 36</span><h3><a href="36-late-binding-with-spellcontract.html">Late binding with spellcontract</a></h3><p>SpellContract - the LATE-BOUND socket. A SpellMap says &quot;resolve this from MY book&quot; and must be satisfiable at conjure. A SpellContract says &quot;someone will hand me this later&quot;, and stays OPEN…</p><div><span class="example-topic">Registration</span><span class="example-topic">Resolution</span><span class="example-topic">Connections</span><span class="example-topic">Research &amp; change</span></div></li>
<li class="example-item" data-level="intermediate" data-topics="[&quot;Registration&quot;, &quot;Resolution&quot;, &quot;Lifetimes &amp; cleanup&quot;, &quot;Configuration&quot;, &quot;Connections&quot;, &quot;Inspection&quot;, &quot;Research &amp; change&quot;, &quot;Concurrency&quot;]" data-search="the frame conduit cloud the conduit cloud - the frame&#x27;s shared registry of conduits, and the first object in this tier that is owned by the world rather than by you. you reach it from any conduit: cloud = conduit.get_conduit_cloud() and here is the sentence that matters, from melder&#x27;s own contract: &quot;reaches through the aetheric frame to the frame-owned cloud, so the returned object is shared by every conduit on the frame.&quot; so `get_conduit_cloud()` is not a factory and not a per-conduit view. two conduits on the same frame hand you the same object. ask any of them, get the same registry - which is what makes it a trustworthy place to answer &quot;what conduits exist here?&quot; frames are worlds (advanced 03), and the cloud is a world-level object. different frame, different cloud - the wall holds here too. what it answers - all cheap reads over the frame&#x27;s conduits: frame_name which world am i the registry for count_conduits() how many list_conduit_ids() by id list_conduit_names() by name has_conduit_id/name() membership without fetching find_conduit_id_by_name(name) -&gt; id or none get_conduit_by_id/name() the actual object and the cluster half, which is dynamic-mode territory: list_cloud_names() / has_cluster_name() / get_cluster() create_cluster() / delete_cluster() add_conduit_to_cluster() / remove_conduit_from_cluster() get_clusters_for_conduit() / refresh_cluster_shares_for_conduit() clusters are how conduits share lineage as a group. this lesson names that surface and stays on the registry half; the cluster lifecycle is its own subject. why the reads matter more than they look `find_conduit_id_by_name` returning optional rather than raising is the honest shape for a lookup that may legitimately miss - and it pairs with has_conduit_name() so you can ask the membership question without paying for the object. cheap questions before expensive ones, the same discipline as the describe ladder at advanced 16. you reach this object; you never name it. `conduitcloud` is not on the package root (owner ruling 2026-08-04) and that is deliberate, not an oversight. its constructor needs an `aethericframe` and a `devopsinformationregistry` - neither exported, neither defaulted - so `md.conduitcloud(...)` could never have been called. its own docstring says it: &quot;users do not construct one.&quot; an exported name you cannot construct advertises a door that is painted on. it is the same ruling `scan` got: `spellbook.scan(module)` is the api because it applies the posture gate and the bind transaction, so exporting the class only advertised a way around them. here there is not even a way around - just a name. the reach is unchanged. `conduit.get_conduit_cloud()` still hands you the live object and every verb below still works. what you lose is `isinstance(cloud, md.conduitcloud)`, and the honest replacement is to test what the object does - which is what this lesson now does, and arguably what it should have done from the start. conduit.get_conduit_cloud(), the frame-shared registry law, the read surface. note: no `md.conduitcloud` - the type is reached, never named. registration resolution lifetimes &amp; cleanup configuration connections inspection research &amp; change concurrency"><span class="example-level">🟡 Intermediate · 37</span><h3><a href="37-the-frame-conduit-cloud.html">The frame conduit cloud</a></h3><p>THE CONDUIT CLOUD - the frame&#x27;s shared registry of conduits, and the first object in this tier that is owned by the WORLD rather than by you. You reach it from any conduit: cloud =…</p><div><span class="example-topic">Registration</span><span class="example-topic">Resolution</span><span class="example-topic">Lifetimes &amp; cleanup</span><span class="example-topic">Configuration</span><span class="example-topic">Connections</span><span class="example-topic">Inspection</span><span class="example-topic">Research &amp; change</span><span class="example-topic">Concurrency</span></div></li>
</ul>

```{toctree}
:hidden:

Scan bind decorator <01-scan-bind-decorator>
Spellbinder full chain <02-spellbinder-full-chain>
Registration hooks <03-registration-hooks>
Spellspace scoped resolution <04-spellspace-scoped-resolution>
Existence unique per conduit lineage <05-existence-unique-per-conduit-lineage>
Spell metadata kwargs <06-spell-metadata-kwargs>
Lesser conduits child scopes <07-lesser-conduits-child-scopes>
Spell override construction <08-spell-override-construction>
Permissions block sharing <09-permissions-block-sharing>
Spellbinder fluent basics <10-spellbinder-fluent-basics>
Permissions linking vocabulary <11-permissions-linking-vocabulary>
Bind lambda spells <12-bind-lambda-spells>
Spell ids and lookup <13-spell-ids-and-lookup>
Introspect the book <14-introspect-the-book>
Constructor di by annotation <15-constructor-di-by-annotation>
Spellmap defaults <16-spellmap-defaults>
Collection di <17-collection-di>
Live creation probe <18-live-creation-probe>
Spellbook configuration basics <19-spellbook-configuration-basics>
Phase scheduler knobs <20-phase-scheduler-knobs>
Dynamic linking basics <21-dynamic-linking-basics>
Permissions create vs read <22-permissions-create-vs-read>
Transfer of ownership <23-transfer-of-ownership>
Conduit cloud <24-conduit-cloud>
Clusters unique per cluster <25-clusters-unique-per-cluster>
Conduit categories as factories <26-conduit-categories-as-factories>
Sever link <27-sever-link>
Upgrade to normal <28-upgrade-to-normal>
Scoped cleanup lesser conduits <29-scoped-cleanup-lesser-conduits>
Config disposal and the frozen law <30-config-disposal-and-the-frozen-law>
Spellbook config defined <31-spellbook-config-defined>
Config meld hooks <32-config-meld-hooks>
Config conduit lifecycle hooks <33-config-conduit-lifecycle-hooks>
Config link and contract hooks <34-config-link-and-contract-hooks>
One config every book <35-one-config-every-book>
Late binding with spellcontract <36-late-binding-with-spellcontract>
The frame conduit cloud <37-the-frame-conduit-cloud>
```