SOPHIA XT live operations

This page is the operating surface of the stack described elsewhere on this site. It exists to answer one question a technical reader is entitled to ask after reading an architecture page: is any of this actually running, or is it a drawing. The console above reads the same endpoints documented below, and the escalation and release rules it replays are the server's own, moved into a shared module so the figure executes the decision logic rather than illustrating it.

What is in this document and what is not

Everything below is structural and is written at build time. No count, no timestamp and no connection state appears here, because a static document cannot hold a live number honestly. A cached copy of this page would go on reporting a value that was true once. Where a current value belongs, this document gives the address to fetch it from instead. A reader with a terminal, and an agent reading this without running scripts, get the same answer that way.

The lanes

Constellation is the router. 6 lanes are registered, each with a role, a weight in the consensus, and whether it is required to produce evidence. A round collects contributions, normalises the weights, and can escalate through depth levels with a higher release floor at each step. A lane that times out or declines is recorded as missing rather than quietly dropped, which is the part that matters: the record shows what did not answer.

  • PLANNER. Decompose the request into ordered sub-goals + propose paths.
  • CRITIC. Adversarially review plans + flag failure modes.
  • RETRIEVE. Search + cite external evidence.
  • EXECUTE. Run tools + produce concrete artifacts.
  • MEMORY SPINE. Recall + crystallize project memory via LTMi-XT.
  • VERIFIER. Independent correctness check via Q3m / XTQ3 ternary scorer.

What is public, and what is not

Public and unauthenticated: the lane registry, the recorded rounds, and the redacted activity feed. Anyone may read those without an account, and the console on this page is built from them.

Authenticated and not public: contributing to a round, posting to the feed, and every administrative path. Lane authentication uses separate token middleware from the administrative credential on purpose, so holding one does not confer the other. Raw round bodies and anything a lane exchanged privately are never served here.

Fetch the current state yourself

  • /api/arbiter/lanes is the live lane registry. It is the authority on how many lanes exist and what each is for, and it is what the count above is read from at build time.
  • /api/arbiter/rounds is the recorded round log, including rounds where a lane produced nothing.
  • /api/live/agents reports the agent slots and when each was last seen.
  • /api/live/feed is the redacted activity feed.

Read next