Skip to content

I3219 — The Observatory is told what happened over the live channel, and asks only when it cannot be told

Let /ui/observatory and /ui/kiosk be told what the journal appended: the journal tells its subscribers every append, /events serves it as a topic carrying the client's logical clock, and PR #1178's observatory-stream.js applies each frame to the scene model the page already builds; the page falls back to its cursor read of /api/v1/observatory/events only when the socket is refused, saying so; the published replay is untouched.

READY wave 0 · p2 · implementation profile · parallel safe

Part of every-surface-follows-what-changed — Every surface follows what changed in the repository by push, and a surface that does not says so.

Ready. Every dependency is done, so majordomus plan start I3219 will be accepted.

Objective

Let /ui/observatory and /ui/kiosk be told what the journal appended: the journal tells its subscribers every append, /events serves it as a topic carrying the client's logical clock, and PR #1178's observatory-stream.js applies each frame to the scene model the page already builds; the page falls back to its cursor read of /api/v1/observatory/events only when the socket is refused, saying so; the published replay is untouched.

Why

Owner, 2026-10-14: Observatory content must be live and streamed over WebSocket. ADR 0158 states the journal-follow is not a true push and anticipates a display that is told rather than asks. Proposed in ADR 0216 (Every live surface follows one channel with named follow streams, and nothing polls where a stream exists) (proposed; it carries no authority until the owner accepts it). Sources: chatgpt-majordomus:c260#0, chatgpt-majordomus:c260#3.

Current state

Verified on master 707a04c7ce8: share/ui/observatory.js fetches /api/v1/observatory/events?after=<cursor> on an interval; I2679 (DONE) made that cursor read; PR #1178 (open, conflicting) holds observatory-stream.js and names the journal follow as its next leaf; I2985 (5a, taken) adds a blackboard scene, not the transport.

Desired state

One socket client and one status machine per page, #1178's observatory-stream.js extended with the journal topic; LIVE is shown only while frames arrive.

Scope

  • share/ui/observatory.js
  • share/ui/observatory-kiosk.js
  • apps/majordomus-cli/src/ui/observatory.rs
  • docs/MAJORDOMUS_UI.md

Out of scope

  • Any write over the socket
  • New scenes

Dependencies

None. This issue is a root of the graph.

What waits on this

Acceptance criteria

  • A journal append reaches an open Observatory without its cursor read running
  • With the socket refused the page reads by cursor and labels itself so
  • The public replay still says REPLAY

Validation

  • bash test/run.sh 3011_the_observatory_draws_nothing_it_did_not_read
  • cargo test --manifest-path apps/majordomus-cli/Cargo.toml --test observatory
  • scripts/ui audit --only /ui/observatory

Evidence required

  • case_the_observatory_is_told

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started
—
verified
—
completed
—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3219.yaml. Read it back with majordomus plan show I3219.

Searches the titles and descriptions of every page this site publishes.