Map

One body, many roads, one return.

This is an orientation, not architectural law or a release roadmap. State of Work records what has entered matter.

Choose your road

One body in one breath

flowchart LR
    subgraph U["Human purpose"]
        M["Magus<br/>intent and authority"] --> C["Call<br/>addressable intent"]
        C --> T["Composition Pattern or Suite<br/>technical realization"]
        CO["Composition owner(s)<br/>domain truth"] --> T
        PR["Product + use case<br/>optional operator package"] -. "selects and presents" .-> CO
        PR -. "supports" .-> T
    end
    subgraph L["Logical execution"]
        T --> I["Invocation<br/>Circle opens"]
        I --> W["Spellweaver<br/>Scroll admission"]
        W --> G["Casting + Graph<br/>Spell placements in motion"]
    end
    subgraph P["Physical embodiment"]
        PR -. "instantiated as" .-> DP["Deployment<br/>configured Product context"]
        DP -. "context when present" .-> I
        G --> D["Dispatcher<br/>interface + profile demand"]
        D --> O["Orchestrator<br/>readiness"]
        O --> N["Animator + Connector<br/>local or external surface"]
        N --> G
    end
    subgraph E["Evidence and authority"]
        G --> R["Artifact, observation<br/>or effect receipt"]
        R --> V["Riddle + Oculus<br/>evaluation and observability"]
        V --> H["Magus / HitL<br/>consent, correction, refusal"]
        R --> K["Phylactery + Memory<br/>governed evidence"]
        H --> C
        K --> C
    end

The Lich names the recurrent whole sustained across this return. No model, Agent, database, workflow, Composition, Product, or interface is the whole by itself.

The application road

Extension Domains receive typed Contributions. Extension packages are selected code/distribution units that may submit Contributions across several Domains; Providers are concrete engines or services bound behind an accepted contract. A Manifestation names the form a Domain takes in one body or profile. Scrolls make work repeatable; Compositions own reusable application truth. When present, a Product packages one or more Compositions for a profession or market and names the concrete use cases offered to its operator; current native Patterns do not require a Product selector. A settled foreign reference does not create a Suite; live coordination across several Composition-owned Invocations does. Suites preserve each member's independent data, policy, identity, and authority. Spellweaver registers, pins, schedules, and admits logical movement; it does not own every thread it weaves.

The shortest vocabulary is:

Extension Domain = stable jurisdiction that receives mechanisms without becoming an application
Extension package = selected code/distribution unit; it may contribute across Domains
Contribution     = one typed addition admitted by its owning Domain
Provider         = concrete engine or service behind a typed contract
Manifestation    = the Domain's concrete form in one body/profile
Spell            = one independently named semantic action contract
Scroll           = one immutable Pattern revision containing Spell placements and their paths
Pattern          = the technical executable-score family
Composition      = reusable application capability and domain truth
Product          = professional or market package of Compositions and use cases
Use case         = one concrete class of operator job supported by a Product
<kind> profile   = owner-qualified specialization preserving the same truth and finish
Suite            = live lifecycle coordination of independently owned Compositions
Deployment       = one configured installation of an exact Product revision
Spellweaver      = logical admission and time
Invocation       = one admitted Circle
Run              = durable execution and ledger identity representing that Invocation
Casting          = performance of one exact Scroll inside that Circle

Enter the Composition Portfolio for reusable application contracts, Product boundaries, and candidate studies. Enter Spellweaver for Scroll/Pattern lifecycle, logical time, admission, schedules, and the boundary between coordination and ownership.

From logical work to iron

Spellweaver admits purpose and logical time. Workers and Ghouls carry durable hops; Graph owns typed movement and checkpoints. Dispatcher resolves exact interface/profile demand, Orchestrator owns local readiness, and an Animator plus its Connector supplies the admitted invocation surface. Phylactery retains run and checkpoint truth. A Pattern asks for capability without commanding hardware; a provider cannot choose application purpose.

Identity, presentation, media, and place

These nearby offices meet often without nesting inside one another:

Avatar may bind one presentation to several simultaneous physical, ambient, social, or virtual projections, but every target and local controller retains its own truth and refusal. A Spectre participant may meet the Lich through an Avatar inside VR; Spectre still owns that Encounter. An admitted phone is a Familiar body; Companion is the mobile-client/session Composition over it, not the Lich's identity or a generic personal endpoint.

What the Map does not own

Definitions belong to the Lexicon, law to the Covenants, application contracts to the Composition Portfolio, anatomy to the Sepulcher, formation to Transcendence, and delivery to State of Work. When a relationship changes, its owner changes first; this page then redraws the route.