Skip to content

Altar

The Altar is the reader journey for a running Lich: the Magus offers an Intent, reviews the evidence it leaves, then consents, refuses, or corrects the next move. Its four instruments are deliberately non-universal. Each answers a different question without pretending to be one shared graph or model.

Inside Bridge, the Circle is the pinnacle: the bounded world of one Invocation, where an exact Scroll is cast under identity, Context, authority, capability, and consequence. Circle composes authorized views from the instruments; it is not a fifth instrument or a new owner of their truth.

The Altar is a contained local surface, not the body it projects: live execution remains in the Vessel, committed truth in the Phylactery, and physical readiness behind the Orchestrator. The Altar lets those boundaries be seen and answered without becoming another one. Loopback and the fixed magus:* Sigil are not caller authentication or browser-origin isolation: keep the dedicated local browser profile, literal 127.0.0.1 listener, and no proxy, tunnel, or port-forwarding described in The Awakening.

The Altar keeps its own tongue separate from the language of an Invocation. Its interface is designed to follow the Magus's selected locale while leaving prompts, answers, artifacts, and Run evidence in their attributed source form; changing the chrome never translates or rewrites what the Altar projects. The current delivered interface remains English-only. Frontend owns the localization contract, while State keeps its delivery boundary.

The Altar likewise has one canonical appearance: LychD Dark. Core focuses on making that single interface legible in bright and dim conditions rather than shipping a nominal light/system toggle. Its semantic colour seam is designed for a future validated, partial operator palette, but not for arbitrary CSS or extension-supplied UI; no palette override is delivered today. Frontend owns the complete boundary.

One Altar, Four Instruments

  • Bridge carries conversation, consent, and settled result.
  • Orb opens one Run as retained ordered evidence; scrying is that inspection.
  • Nexus makes capability readiness and physical transition legible.
  • Loom shows an exact Scroll/Pattern and its declared stations, which become Spell placements in the future; it is a declared score, never an execution trace.

Each instrument may use a graph when it is the clearest answer, but none supplies a universal graph or domain model. A Loom edge permits; an Orb relation records; a Nexus relation reports what the Orchestrator observed. Loom and Orb may share framework-neutral snapshot, identity, intent, and semantic-projection mechanics while keeping distinct view models over the designed one shared DOM renderer adapter. They do not share one graph schema or collapse permitted score into observed evidence. Nexus remains a native control board unless a measured body-map requirement earns a separate read-only lens. The distinctions stay visible.

Enter through the Bridge

After the four observations in Summoning agree on this host, enter:

http://127.0.0.1:7134/

The root opens Bridge. On a fresh Phylactery, choose New Séance, offer one bounded Intent, and answer an inline consent card only when the Run asks. That admission opens one conceptual Circle inside the continuing séance. Follow the same-host boundary in The Awakening; deeper limits remain in State of Work.

Review one Run across the Altar

  1. In Bridge, create a séance and offer one bounded Intent; treat its admitted Run projection as one Circle, not the whole séance.
  2. On its result, confirm the Run identity, Scroll/Pattern revision, and canonical status, then choose Look into the Orb.
  3. In the Orb, confirm the Run id, capture class, loaded boundary, gaps, and omissions. Select an event to give it a stable URL.
  4. Open Exact Pattern only when its pinned Scroll manifest validates. Loom verifies the declared score, never execution.
  5. Open a Nexus transition only when selected evidence supplies exact correlation. Compare a capability's checked time with the Nexus snapshot time.
  6. Treat Preview as non-binding. Request transition is a real maximum-priority lifecycle mutation.