The Observatory at /ui/observatory and /ui/kiosk shows a scene only when the capabilities it requires answered with something to draw, or, for a scene of the mesh where no mesh runs, when the repository carries a recording of it, which it labels a replay; a scene without either carries no model and states the source's reason, on a server and in the published snapshot alike

The Observatory (/ui/observatory, and /ui/kiosk as its unattended preset) draws the

declared statusdeclared status: guaranteed Declared deterministic and blocking, implemented, and naming the behavioural test that is to prove it. Whether a recorded run supports it is the evidence verdict, shown beside it.

recorded evidencerecorded evidence: not run Declared guaranteed, and not supported by a recorded run: the test is named, and no passing run of the current inputs is recorded. how evidence is recorded

The case starts a server over a freshly initialised repository and takes a UI snapshot of it, and on both reads the projection the page carries: eight scenes in the declared order, every source named with its state and a failed one with a reason, an available scene with a model and an unavailable one with none and a reason, the three mesh scenes unavailable where no mesh runs, the kiosk carrying the same scenes, the two redirects, and the snapshot holding the page and its script. It reads the projection, not the canvas: what the script paints from an available scene's model is not claimed here.

What it means

The Observatory (/ui/observatory, and /ui/kiosk as its unattended preset) draws the repository and its mesh as rotating scenes. Every scene is declared once, with the capabilities it requires. A scene is available only when those capabilities answered with something to draw; otherwise it carries no model, states the source's own reason, and the rotation does not show it. A process that runs no mesh, which is what reads the published snapshot, has no live mesh scene to show: there a scene of the mesh draws the recording the repository carries and says it is a replay, and without a recording it says it is unavailable.

How it works

apps/majordomus-cli/src/ui/observatory.rs holds the one inventory, SCENES, and projects the answers of nine capabilities into one bounded document, observatory/v1, which the page carries in its data-observatory attribute. share/ui/observatory.js draws that document and decides nothing about it. The same projection is a table on the page, one row per scene, for a reader without the script.

test/cases/3011_the_observatory_draws_nothing_it_did_not_read.sh proves it on a server over a freshly initialised repository and on majordomus web report ui-snapshot:

/ui/observatory and /ui/kiosk answer, and carry the same scenes in the same order;
the document names every source with the state it answered in, and a failed one with a reason;
an available scene has a model, an unavailable one has none and has a reason, and no available semantic scene requires a source that failed;
the three scenes of the mesh are unavailable where no mesh runs and no recording is carried; with a recording, the recorded scene is available, says replay with the time it was recorded, and the scenes it does not carry stay unavailable; a recording that is not one is a failed source and is never drawn;
/ui/screensaver redirects to /ui/kiosk and /ui/obsrvatory to /ui/observatory;
the snapshot holds the page and its script.

How to see it

majordomus serve                       # logs the URL of the shared server
# open <url>/ui/observatory, or <url>/ui/kiosk for the unattended display
bash test/run.sh 3011_the_observatory_draws_nothing_it_did_not_read

What it does not cover

It proves which scenes are available and that an unavailable one carries no model. It does not prove what the canvas paints: that each mark of an available scene is placed and coloured from its model is the script's, and no test reads pixels. The unit tests of the module hold the projection itself, including that an event's body is never projected.

It does not prove frame rate, a 4K composition or that a kiosk keeps running; those are measured by scripts/lib/ui-observatory.mjs and recorded with their machine in .ai/repo/benchmarks/observatory/. The cursor the display follows between readings (observatory.events) is proven by the mesh cooperation test, not by this case.

Why it exists

A wall display is believed from across a room by people who will never open a source line. A picture that drew a healthy constellation where no mesh was running, or a river of events that never happened, would be the most persuasive false statement this repository could make. The claim makes absence a stated fact of the page, and the case holds it on the two processes that serve the page: a server, and the reader of the published snapshot.

Detail rendered from docs/claims/observatory-draws-nothing-it-did-not-read.md.

From the statement to the proof

1 · the public statement

The Observatory at /ui/observatory and /ui/kiosk shows a scene only when the capabilities it requires answered with something to draw, or, for a scene of the mesh where no mesh runs, when the repository carries a recording of it, which it labels a replay; a scene without either carries no model and states the source's reason, on a server and in the published snapshot alike

Made on Observatory.
2 · the canonical claim

observatory-draws-nothing-it-did-not-readdeclared status: guaranteed in docs/CLAIMS.yaml

Defined in read it on this site · docs/MAJORDOMUS_UI.md
3 · the implementation

apps/majordomus-cli/src/ui/observatory.rs
4 · the test and the scenarios
Test: test/cases/3011_the_observatory_draws_nothing_it_did_not_read.sh
5 · the recorded runs

recorded evidence: not run how evidence is recorded

Verify it yourself

The test runs in a disposable temporary repository and asserts the behaviour, not a string in the source.

from a clone of the repository

bash test/run.sh 3011_the_observatory_draws_nothing_it_did_not_read