A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I2680

The Observatory's gates are closed with evidence: screenshots, measured frame rates, a soak, the recovery drills

Where it stands

Readiness: complete completion is recorded and every required evidence token is present
Status: DONE
Can start: not now
Milestone: development-runtime
Milestone status: ACTIVE
Wave: 0
Waiting on: none
Holds back: none
Behind it in all: 0
Evidence: 1 of 1

Objective: Close each acceptance gate of the owner's Observatory specification with a command, its result, its environment and a path to the evidence, or record it as not run.
Why: The specification of 2026-10-14 names eight gates, G0 to G7, and says that PASS, FAIL, BLOCKED and NOT RUN are different words and that a checked box cannot stand in for an execution. Case 3011 covers the data contract; nothing yet covers what the display looks like, how fast it draws or how it survives a night.
Now: Held by case 3011: the routes, the scene inventory, the projection, unavailable scenes with their reasons, the rows without script, the snapshot. Not run: screenshots at 1080p and 4K, frame rates on named hardware, reduced motion, a soak of the kiosk, the drills for a lost server, an expired reading and a failed scene. No figure about the display's performance is stated anywhere.
Wanted: A tracked manifest names the revision, the routes and, for each gate, its verdict with the command, the environment and the evidence path. The browser checks that can run in CI run there; the ones that need hardware are run on named hardware and recorded with it.
Done when: unknown: the record declares no `completion`
Risk: unknown: the record declares no `risk`

Each of G0 to G7 has a verdict of PASS, FAIL, BLOCKED or NOT RUN with its command, environment and evidence path
Screenshots of an available scene at 1920x1080 and 3840x2160 are evidence of a named revision
The display honours reduced motion, and a browser check proves it
A kiosk left running for a stated number of hours has its memory read at the start and at the end, on named hardware

Touches: docs/MAJORDOMUS_UI.md.ai/repo/project/issues/I2680.yaml
Not: Stating a frame rate, a memory figure or an uptime that was not measured
Depends on: none
Priority: p2
Profile: verification
Parallel safe: true
Owner: unknown: the record declares no `owner`

Adapter: scripts/github-sync
Repository: unknown: the derived plan's header carries no repository
External issue: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Nothing is wrong with these records.