Altar
In plain words: Control Panel overview
Overview of the web Control Panel (Altar) at http://127.0.0.1:7134/: how to log in locally, send a request in Chat, and follow a Job Record across the Project Board, Run Inspector, Workflow Viewer and Model Status Board.
- 1Access is same-host loopback only, with a local credential from lychd access; no proxy or tunnel.
- 2Each Chat turn opens a Task Bubble with a Job Record id you can follow in every instrument.
- 3The fuller Task Bubble workspace is not yet delivered.
Partial Instruments work locally; remote access and some views are not built.
Words on this page, decoded click one for its card
Control Panel Altar
The web app where you talk to the assistant and see what it is doing.
It's like: The cockpit dashboard.
Click a dot to open that part's card.
In this section 7 pages
Bring a piece of work to the AltarControl Panel, then follow it beyond the reply. You can keep a project's concerns beside its conversation, inspect the evidence behind a result, read the score that guided the RunJob Record, and examine any recorded change to the iron. Each instrument answers a different part of that inquiry.
Bring one Intent
Begin with Summoning, including its four observations of the bound body
and first reply. Before starting services, read its closure limitation:
lychd stop currently refuses an active VesselEngine Room, so the trial needs a separately authorized
recovery plan. SummoningInstallation does not supply a working end-to-end start/stop procedure.
For startup and local access, follow The Awakening. With the VesselEngine Room running under that trial boundary, open the AltarControl Panel in 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 BridgeChat. On a fresh PhylacteryMemory Vault, choose New Séance and offer a bounded IntentRequest.
Answer an inline consent card only when the RunJob Record asks for judgment.
Keep the listener on literal loopback, with no proxy, tunnel, or forwarding. Loopback and the
fixed magus:* SigilID Badge 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
Follow one admitted conversation turn from your offered request to its result. Its RunJob Record identity lets you find the same act in each instrument. The conversation, or séance, can hold many such turns.
Each admitted turn opens a Circle: one InvocationJob Request. Within that CircleTask Bubble, the casting performs an exact ScrollWorkflow Version, the workflow score; its RunJob Record keeps durable execution identity. Keep that 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 RunsJob Records are before us, what evidence is arriving, and where does capture run out? | Orb |
| Which stations and paths does this exact ScrollWorkflow Version permit? | Loom |
| What was observed about readiness or a physical transition? | Nexus |
AtlasProject Board, OrbRun Inspector, LoomWorkflow Viewer and NexusModel Status Board appear in the top navigation. Bridge remains available as a conversation panel beside the selected work. Icons accompany their visible names; hover, click or keyboard opens the menu. Applications opens the admitted application list, including Canvas and Scavenger market.
AtlasProject Board gives a larger undertaking continuity across conversations and RunsJob Records, and can begin before either exists. Inside BridgeChat, a CircleTask Bubble gathers one InvocationJob Request. Its current form is a compact per-turn RunJob Record disclosure: supplied status, complete identity, evidence and declared-score links, and eligible cancellation. Circle is the Invocation-shaped pinnacle within BridgeChat; a composed CircleTask Bubble workspace is not yet delivered.
Start with Look into the OrbRun Inspector beside a BridgeChat result. Keep the same RunJob Record identity as you inspect capture limits and gaps, compare its pinned score in LoomWorkflow Viewer, or follow an exact physical-transition correlation into NexusModel Status Board. The leaf guides explain each step. That shared identity keeps an observation attached to the work that prompted your question.
For several RunsJob Records, open /orb. Its parallel field combines a paged catalogue with at most three
bounded live lenses on one canvas. Zoom or explicit detail controls reveal supplied RunJob Record, station,
occurrence, and record identities. Deeper subworkflow structure needs an identity from its owner;
the view cannot infer it.
NexusModel Status Board inspection changes no lifecycle state. Preview is nonbinding; Request transition performs a real maximum-priority mutation. Read the Nexus guide before making that request.
Keep Bridge beside the work
Use BridgeChat in the masthead to open or collapse the conversation panel. Drag its divider to change its width, or focus the divider and use its arrow keys. Dock left and Dock right choose the side. A wide window makes room beside the panel; a narrow window opens it as a modal sheet with Escape and a return to the opener. Layout preferences may be remembered in this browser; conversation drafts and unresolved requests retain their existing open-document boundary.
Switching instruments keeps the selected conversation. Collapsing BridgeChat does not cancel its RunJob Record, submit a draft or approve a request. The context label identifies the work you are viewing; it does not transmit the work to a model. Exact BridgeChat session, RunJob Record and consent links remain valid, including links from OrbRun Inspector. Investigation and public-note focus stay distinct from the ordinary conversation. Read Bridge for those operations and recovery boundaries.
The surface and its owners
Execution belongs to the Vessel, committed truth to the Phylactery, and physical readiness to the OrchestratorStage Manager. The AltarControl Panel projects those accounts so the MagusYou, the Operator 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 CovenantDesign Rule (ADR); interface choices preserve retained source content.
Presentation direction
Each page is arranged as a quiet observatory around the work you came to read: an undertaking, conversation, account, board, or score. Identity and history unfold as needed, while uncertainty, consent, capture limits, and physical consequences stay beside the choices they qualify. Frontend's reading hierarchy owns this shared design. Each instrument's Reading direction explains 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 AltarControl Panel 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.