Altar
A reply is the beginning of a review. The Altar lets you stay with one piece of work as you move from a project's concerns to conversation and evidence, from evidence to its declared score, and from a recorded transition to the state of the iron.
Bring one Intent
Establish the four observations in Summoning. That rite ends by stopping the Vessel; for a later Altar session, return through The Awakening’s startup before opening the browser. Use a dedicated profile on the same host:
http://127.0.0.1:7134/
Before entering, retrieve the dedicated local credential in a private terminal with lychd access
and answer the browser's authentication dialog as described in
The Awakening. Keep the password out of URLs and command lines.
The root then opens Bridge. On a fresh Phylactery, choose New Séance and offer a bounded Intent.
Answer an inline consent card only when the Run asks for judgment.
Keep the listener on literal loopback, with no proxy, tunnel, or forwarding. Loopback and the
fixed magus:* Sigil alone do not authenticate a caller. The separate credential proves local
possession; it supplies no remote person identity or hostile-browser isolation. The full current
boundary lives in The Awakening; State of
Work records the delivered surface.
Carry the Run with you
One séance can hold many Circles. Each Circle is one admitted Invocation, whose casting performs an exact Scroll and whose Run keeps durable execution identity. Keep that Run identity in view when changing instruments.
| What you need to establish | Instrument |
|---|---|
| What are we trying to accomplish or care for, what needs judgment, and what comes next? | Atlas |
| What was offered, what judgment is pending, and what settled? | Bridge |
| Which Runs are before us, what evidence is arriving, and where does capture run out? | Orb |
| Which stations and paths does this exact Scroll permit? | Loom |
| What was observed about readiness or a physical transition? | Nexus |
These are the Altar's five instruments. Atlas keeps a Project across conversations and Runs; it can also begin without either. Circle is the Invocation-shaped pinnacle within Bridge, not a separate instrument. Its current material form is a compact per-turn Run disclosure with supplied status, complete identity, evidence and declared-score links, and eligible cancellation. A composed Circle workspace is not delivered.
At a Bridge result, keep its Run identity and choose Look into the Orb. The leaf guides show
how to account for capture and gaps, compare the pinned score in Loom, and follow exact physical
transition correlations into Nexus. Carrying the same Run through those views keeps each
observation attached to the work that raised your question.
Open /orb for the parallel Run field: a paged catalogue and at most three bounded live lenses
share one canvas. Zoom or explicit detail controls unfold supplied Run, station, occurrence, and
record identities; deeper subworkflow structure remains unavailable without its owner's identity.
Nexus inspection changes no lifecycle state. Preview is nonbinding; Request transition performs a real maximum-priority mutation. Read the Nexus guide before making that request.
The surface and its owners
Execution belongs to the Vessel, committed truth to the Phylactery, and physical readiness to the Orchestrator. The Altar projects those accounts so the Magus can inspect and act through their admitted seams.
The delivered interface is English-only and uses LychD Dark, with no locale selector or palette override. Future locale and palette contracts belong to the Frontend Covenant; interface choices preserve retained source content.
Presentation direction
The presentation follows a quiet observatory: a readable undertaking, conversation, account, board, or score is each page's focal point. Secondary identity and history are disclosed when useful. Uncertainty, consent, capture limits, and physical consequences stay beside the choices they qualify. Frontend's reading hierarchy owns the shared design; each instrument's Reading direction distinguishes its current composition, further targets, and a practical acceptance case.
Follow Atlas's concerns and citations, Bridge's conversation and recovery, Orb's parallel evidence field, Nexus's preview and observations, or Loom's declared score. Current controls and the boundaries of graph expansion remain those described in the operating sections and State of Work.
Artwork supports the entrance rather than repeating behind work on every instrument. The existing empty-Bridge scene has a retained asset notice and generation prompt. They distinguish the generated Altar scene, the authorized character reference, and their terms. The source distribution retains third-party notices; their custody does not require a permanent footer competing with the work.