| title | Map |
|---|---|
| icon | material/map-marker-path |
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.
flowchart LR
subgraph U["Human purpose"]
M["Magus<br/>intent and authority"] --> C["Call<br/>addressable intent"]
C --> A["Composition or Suite<br/>application purpose"]
end
subgraph L["Logical execution"]
A --> W["Weaver<br/>Pattern admission"]
W --> G["Invocation + Graph<br/>Agents and deterministic steps"]
end
subgraph P["Physical embodiment"]
G --> D["Dispatcher<br/>semantic demand"]
D --> O["Orchestrator<br/>readiness"]
O --> N["Animator<br/>local or external capability"]
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, or interface is the whole by itself.
Extensions contribute mechanisms; Patterns make work repeatable; Compositions make it useful to an operator. Suites connect applications without erasing their independent data, policy, identity, or authority. Weaver registers, pins, schedules, and admits logical movement; it does not own every thread it weaves.
The shortest vocabulary is:
Extension = how implementation enters the body
Pattern = one immutable workflow score
Composition = the application the Magus operates
Suite = independently owned Compositions related by typed handoffs
Weaver = logical admission and time
Invocation = one admitted performance of an exact Pattern revision
Enter the Composition Portfolio for application contracts and candidate studies. Enter Weaver for Pattern lifecycle, logical time, admission, schedules, and the boundary between coordination and ownership.
Weaver admits purpose and logical time. Workers and Ghouls carry durable hops; Graph owns typed movement and checkpoints. Dispatcher resolves capability demand, Orchestrator readiness, and an Animator supplies local or external capability. Phylactery retains run and checkpoint truth. A Pattern asks for capability without commanding hardware; a provider cannot choose application purpose.
| Your question | Begin here | Continue through |
|---|---|---|
| What can this revision actually do? | State of Work | cited source, tests, lockfiles, and maintained receipts |
| How does Intent become an application and a run? | Composition Portfolio | Weaver → Pattern → Invocation → Graph |
| Which organ owns a physical mechanism? | Sepulcher | Vessel, Phylactery, Animators, and Extensions |
| How do observations become evidence and memory? | Lich | Riddle/Oculus → Phylactery/Memory → correction or Recall |
| Which law governs a change? | Covenants | owning ADR → topic page → State → source evidence |
| What is the Great Work ultimately trying to cultivate? | Transcendence | Nigredo → Albedo → Citrinitas → Rubedo → Infinity |
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.