Skip to content

Latest commit

 

History

History
114 lines (83 loc) · 5.75 KB

File metadata and controls

114 lines (83 loc) · 5.75 KB
title Orb
icon material/crystal-ball

:material-crystal-ball: Orb

The Orb opens one selected Invocation, represented in the UI as a Run, as ordered structural evidence. Looking through it is scrying. It shows records and explicit gaps; it does not fill missing history with inference.

The Run owns canonical ledger status; the Orb exposes only the bounded trace available to its sources. A trace may gap or disappear and cannot replace Run, consent, grant, effect, or artifact truth. Under separate Memory policy some residue may become a Seed, but observation alone gives it no power to return.

Enter from a Bridge result with Look into the Orb, or open /orb/{run_id} directly. The bare /orb route asks you to open Bridge because there is no authorized run list.

The Orb and the Eye

The Orb is the Altar surface; Oculus is the evidence office. Native durable Oculus storage is not delivered. The current Orb reads evidence available through this running Vessel and labels capture process local or durable best effort.

The First Invocation

Start at the run header:

  1. Confirm the Run id, canonical status, and capture class.
  2. Follow Bridge to return to the owning conversation.
  3. Use Exact Pattern only when the pinned manifest still validates. Its Loom URL carries ?run={run_id} as return context; it does not change Pattern identity.
  4. Read the coverage strip: snapshot, retained through (ledger head), loaded through (this page), and live updates. Current snapshots say not available for live updates.
  5. Choose Refresh to request a new bounded snapshot.

The first request loads up to 100 evidence records. Load more retained evidence requests the next page while more records exist. A visible #start–end gap means unknown or omitted interval; the Orb does not decide why those sequence numbers are absent.

Designed: Ask Why It Waits

There is no Why waiting? analysis. The Orb shows recorded status, phase, subject, occurrence, and transition correlation when present. A generic wait does not reveal its cause.

Not Yet in the Orb

The current Orb has no searchable run list, multi-run field, graph canvas, time lens, historical replay, or live tail. Select another Run in Bridge.

Designed graph boundary

The accepted future direction is the one DOM renderer Orb shares with Loom, reached through a LychD-owned Svelte adapter over the shared projection supply. Neither dependency nor a graph field is delivered. The renderer would hold only a disposable view of the selected authoritative snapshot and ordered evidence; its arrays, camera, animation, and hit-testing state could never become Run, capture, gap, annotation, or settlement truth.

Orb is bounded by folding, not by a dense engine. A separate WebGL renderer would double the adapter, semantic twin, teardown audit, and licence review while supplying no accessible surface, and no measured Orb field requires it. Sigma with Graphology and cosmos.gl remain mapped in the Frontend Covenant against a later field that folding cannot bound; G6 was evaluated and rejected. That Covenant owns the choice, and State of Work owns whether any part has entered matter.

Folding and bounded expansion

The field never renders a whole trace. Folding keeps the rendered set bounded at every camera scale, because a field no reader can read is not evidence.

Folding follows structure this Vessel already declares: Run, then station subject, then occurrence, then event, with delegated jobs as their own declared groups. A group carries its declared name and membership count and stays selectable and expandable through the same typed identities. Geometric or computed clustering is not admitted; proximity would assert a relation no authority declared.

Bounded progressive loading is a Vessel contract, not a renderer feature: authority serves what was asked for, and the browser holds only what it was served. An unexpanded group whose members were never served is an explicit unknown, exactly like a #start–end sequence gap, and the Orb does not infer across it.

Folding is presentation only. A group is never an evidence record, and collapsing never merges, omits, or reorders retained sequence truth.

Inspect One Event

Select an evidence row to open Selected event. The URL becomes /orb/{run_id}?event={event_id}, so the same retained event can be revisited. The inspector shows only recorded structural fields: sequence, kind, subject, phase, occurrence, and capture class. A correlated transition adds Open transition in Nexus and carries the selected event id.

If the linked event is outside the loaded page, load more. If it is no longer retained, the Orb says so.

When delegated work exists, Delegated jobs shows at most the newest 32 summaries. Each gives the AgentJob identity, runtime, Coffin profile, station, status, bounded-result presence, artifact-reference count, and up to the latest 64 lifecycle events. Truncation and older omitted jobs are explicit. Prompts, output text, and private errors are not exposed.

Projection and Annotation Law

Selection and pagination do not change Run state. The Orb has no annotation, retry, cancellation, approval, publication, or transition action. The Nexus link changes instruments; it does not claim that viewing requested a mutation.

Witness Without Possession

The current journey is exact:

  1. Select or create a Run in Bridge.
  2. Look into the Orb and confirm identity, status, capture, coverage, gaps, and omissions.
  3. Select an event for a stable review URL.
  4. Open Loom only for a validated exact Pattern.
  5. Open Nexus only from an event with transition correlation.