On this page

🔵 Expert examples

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

Open the Expert guide · All examples

  • 🔵 Expert · 01

    Pod boot the order is the product

    BOOTING A POD. Advanced 17-18 taught checkpoint and load as two verbs you call yourself. This is the operator's version: one entry point that runs the whole restart flow in a fixed…

    ResolutionConfigurationConnectionsAgent rooms & codegenPersistence & restoreResearch & changeConcurrency
  • 🔵 Expert · 02

    Persistence mesh your code their lanes

    THE ASYMMETRY AT THE EDGE OF YOUR WORLD, demonstrated rather than described. Melder never speaks to your database - it calls YOUR callables. So the interesting question is what happens when…

    ResolutionConfigurationInspectionPersistence & restoreResearch & change
  • 🔵 Expert · 03

    Research sets lanes and residency

    MUTATION RESEARCH - melder's record of how a world CHANGED, not what it currently is. Everything up to here described a runtime. This describes its history. THE SHAPE MutationResearch the…

    ResolutionLifetimes & cleanupConfigurationInspectionAgent rooms & codegenPersistence & restoreResearch & changeConcurrency
  • 🔵 Expert · 04

    Diffs are derived never stored

    DERIVE A DIFF, THREE WAYS, AND WATCH THE ANSWER CHANGE. Version records are full objects; "what changed" is computed on demand and never written back. "A verdict is an answer, not a fact…

    ResolutionAgent rooms & codegenPersistence & restoreResearch & change
  • 🔵 Expert · 05

    Protocol crafter the tool that writes

    THE ONE TOOL THAT WRITES TO DISK. Every surface in this curriculum so far reads: viewers read, crystals read, diffs derive, research records. ProtocolCrafter is the exception, and its own…

    ResolutionConnectionsInspectionPersistence & restoreResearch & changeConcurrency
  • 🔵 Expert · 06

    Two knobs and a terminator per rung

    THE LAST TWO PUBLIC NAMES, and what they say about the whole configuration story the curriculum has been tracking since advanced 07. MutationResearchConfiguration has exactly TWO knobs:…

    ResolutionConfigurationConnectionsAgent rooms & codegenPersistence & restoreResearch & change
  • 🔵 Expert · 07

    The codegen room agents writing code

    THE CODEGEN ROOM - where an agent writes code that becomes part of a running world, and the gate it has to get through first. This is the only room kind where the caller supplies EXECUTABLE…

    ResolutionConfigurationConnectionsInspectionAgent rooms & codegenResearch & changeConcurrency
  • 🔵 Expert · 08

    Research is graduated by room

    HOW AN AGENT REACHES MUTATION RESEARCH - and the discovery that access to it is GRADUATED BY ROOM KIND, exactly the way the conduit surface was in advanced 11. MEASURE THE THREE ROOMS AND…

    Agent rooms & codegenResearch & changeConcurrency
  • 🔵 Expert · 09

    Getting data into your database

    PUT YOUR WORLD IN YOUR OWN DATABASE - and notice what melder does NOT do to get it there. This wires a real mesh, seals a real checkpoint, and watches the bytes arrive. MELDER NEVER IMPORTS…

    ResolutionConfigurationConnectionsInspectionPersistence & restore
  • 🔵 Expert · 10

    Deep overrides paths through a graph

    OVERRIDES WHEN THE GRAPH IS DEEP. Advanced 19 taught the three TARGETING FORMS - path, *unique, **broadcast - on a shallow graph where the difference between them is mostly convenience.…

    ResolutionResearch & changeConcurrency
  • 🔵 Expert · 11

    Pointing a rift at your own frame

    AR ONTO YOUR OWN WORLD. Advanced 09 built a Rift and deliberately stopped short of targeting - it said so in its own text, because until 2026-08-03 the capability was genuinely unreachable…

    ResolutionConfigurationConnectionsInspectionAgent rooms & codegenResearch & changeConcurrency
  • 🔵 Expert · 12

    The codegen loop end to end

    THE CODEGEN LOOP, ACTUALLY RUN. Expert 07 introduced the room and named its three verbs. This drives them: an agent asks permission, writes code into a named world, and reads back what it…

    Lifetimes & cleanupConfigurationInspectionAgent rooms & codegenResearch & change
  • 🔵 Expert · 13

    One workshop many worlds

    ONE CODEGEN ROOM, SEVERAL WORLDS. Expert 11 attached a rift to a frame; 12 ran the loop against one. This is the shape you actually end up with: a single workshop wired to several frames,…

    RegistrationConfigurationConnectionsAgent rooms & codegenResearch & changeConcurrency
  • 🔵 Expert · 14

    Compositions a subsystem as one unit

    COMPOSITIONS - naming a SET of spells as one thing, and then asking questions about the thing instead of about its members. Expert 03 taught residency: a spell lives in exactly one lane.…

    ResolutionInspectionAgent rooms & codegenPersistence & restoreResearch & changeConcurrency
  • 🔵 Expert · 15

    Campaigns the why that rides along

    CAMPAIGNS - the WHY, carried without anyone remembering to carry it. Expert 14 built a subsystem and left one argument dangling: `research_group_history(group_id, campaign=...)`. This is…

    RegistrationResolutionAgent rooms & codegenResearch & changeConcurrency
  • 🔵 Expert · 16

    Rewiring a running world

    CHANGING THE WIRING WHILE THE WORLD RUNS. A dynamic world can gain a relationship after it is built: two conduits link, one pulls a spell it does not own into its contract, and the next…

    RegistrationResolutionConfigurationConnectionsAgent rooms & codegenResearch & changeConcurrency
  • 🔵 Expert · 17

    Notch swapping a live object

    LINEAGES, AND THE STAGING HALF OF A HOT SWAP. An index is a version LINEAGE with exactly one SELECTED member. This lesson builds one, stages a second version onto it, and shows that staging…

    RegistrationResolutionConnectionsPersistence & restoreResearch & changeConcurrency
  • 🔵 Expert · 18

    The package reads itself to you

    YOU DO NOT READ A SYSTEM DOCUMENT, YOU ADDRESS IT. Four documents hang off the package root and answer AT IMPORT - before Aether boots, before a Spellbook exists, before anything is…

    Agent rooms & codegenResearch & changeConcurrency
  • 🔵 Expert · 19

    The codebase as a walkable graph

    THE GRAPH DOCUMENTS. Expert 18 addressed prose by section. The two graph documents carry the same prose surface AND a real graph: nodes, edges, traversal, and blast radius - answered at…

    InspectionAgent rooms & codegenResearch & change
  • 🔵 Expert · 20

    The workstation an agents workbench

    THE WORKBENCH. A codegen room is not just a place to run code - it has a WORKSTATION, a room-local canvas where an agent keeps named handles on things between commands. Advanced 12…

    RegistrationResolutionLifetimes & cleanupInspectionAgent rooms & codegenPersistence & restoreResearch & changeConcurrency
  • 🔵 Expert · 21

    Many agents writing code at once

    REAL CODEGEN, AND SEVERAL AGENTS DOING IT AT ONCE. Expert 12 drove the loop once, on one thread. This is the shape melder is actually built for: four agents, four rooms, one shared world,…

    RegistrationResolutionLifetimes & cleanupConnectionsInspectionAgent rooms & codegenConcurrency
  • 🔵 Expert · 22

    Asking what code would do before running it

    FORESIGHT. An agent about to replace a version can ask what the replacement WOULD do - what it defines, what it imports, how it differs from what is there, what it would break, and whether…

    RegistrationResolutionConfigurationAgent rooms & codegenPersistence & restoreResearch & changeConcurrency
  • 🔵 Expert · 23

    Branching the record and joining back

    BRANCHING, AND WHY A JOIN CAN REFUSE. Research lanes are melder's branches: parallel lines of versions over one world, anchored to each other, finished by joining. It looks like git until…

    RegistrationResolutionLifetimes & cleanupConnectionsInspectionAgent rooms & codegenResearch & changeConcurrency
  • 🔵 Expert · 24

    Loading a whole world back

    SEAL A WORLD, THEN UNFOLD IT AGAIN. Expert 01 taught the pod-boot ORDER; expert 09 taught what crosses the wire. This is the round trip itself - checkpoint a live world, put it in the…

    RegistrationResolutionConfigurationInspectionPersistence & restoreConcurrency
  • 🔵 Expert · 25

    Many research sets one world

    RESEARCH SETS, PLURAL. Everything so far used the default set and never said there was a choice. A ResearchSet is a whole INDEPENDENT BODY OF HISTORY over the same runtime - its own lanes,…

    ResolutionAgent rooms & codegenResearch & change
  • 🔵 Expert · 26

    Codegen create modify iterate

    THE LOOP TURNED MORE THAN ONCE - AND THE TWO BOOKS IT WRITES. Expert 12 drove the codegen verbs once. This iterates them, and in doing so hits the distinction that catches everyone: a…

    RegistrationAgent rooms & codegenResearch & change
  • 🔵 Expert · 27

    A world that outlives its own runtime

    TEAR THE RUNTIME DOWN ON PURPOSE, THEN COME BACK. Expert 24 walked the five checkpoint verbs while the world stayed up. This is the harder half: seal a world, DESTROY the Aether singleton,…

    ResolutionLifetimes & cleanupAgent rooms & codegenPersistence & restore
  • 🔵 Expert · 28

    The record crosses as a json string

    NO FILE, NO DATABASE, NO DRIVER - A PYTHON STRING. Merge two research lanes, turn the whole record into TEXT, throw the live set away, and rebuild it from that text with its identity…

    RegistrationInspectionPersistence & restoreResearch & change
  • 🔵 Expert · 29

    Reading your own recorded code

    THE CRYSTAL WELL - reading the code your world RECORDED, at four grains, and the one comparison law that makes any of it trustworthy. Expert 04 said diffs are derived, never stored. This is…

    RegistrationInspectionAgent rooms & codegenPersistence & restoreResearch & change
  • 🔵 Expert · 30

    Composing a version in the workshop

    THE HALF OF A MERGE THAT JOIN REFUSES TO DO, on code the room actually generated. Expert 23 said it outright: "Reconciliation-by- content is not a join concern: compose in the codegen…

    RegistrationResolutionConnectionsAgent rooms & codegenPersistence & restoreResearch & change
  • 🔵 Expert · 31

    Organising lanes after the fact

    LANES ARE ORGANISED AFTER THE FACT, NOT PLANNED IN ADVANCE. Expert 23 cut branches and joined them. This is the other three verbs - the ones for when you got the shape wrong the first time.…

    RegistrationResolutionPersistence & restoreResearch & change
  • 🔵 Expert · 32

    A subsystems blast radius

    ASK A WHOLE SUBSYSTEM WHAT IT WOULD BREAK. Expert 14 built compositions - a set of versions pinned as one unit. This asks the two questions you actually have about one: how far does it…

    Agent rooms & codegenPersistence & restoreResearch & changeConcurrency
  • 🔵 Expert · 33

    What a synthetic module actually is

    WHAT A SYNTHETIC MODULE ACTUALLY IS, and why one crystal shape holds both it and a file on your disk. Lessons 26, 27, 29, 30 and 32 all MAKE synthetic modules. None of them says what one…

    RegistrationResolutionConfigurationInspectionAgent rooms & codegenPersistence & restoreResearch & change
  • 🔵 Expert · 34

    Several worlds of record in one process

    KEEP TWO SEPARATE WORLDS OF RECORD IN ONE PROCESS. Every lesson so far has recorded into one nameless place. It has a name - "default" - and you can have others. A PROFILE IS WHERE…

    ResolutionConfigurationInspectionAgent rooms & codegenPersistence & restoreResearch & change
  • 🔵 Expert · 35

    The gate that waits for readers

    THE ADMISSION GATE, and why it is not a mutex. Expert 16 rewired a running world and 17 staged a swap on a live object. Neither said what makes those safe. This does. MELDER HAS THREE GATES…

    ResolutionAgent rooms & codegenPersistence & restoreConcurrency
  • 🔵 Expert · 36

    An agent builds a working system

    NOTHING IN THIS FILE EXISTS WHEN THE PROCESS STARTS. Three classes are written as text at runtime, become real importable modules with no file on disk, get bound as spells, and come out as…

    RegistrationResolutionLifetimes & cleanupAgent rooms & codegenPersistence & restore