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

✓DONE wave 0 · p2 · verification profile · parallel safe

Part of development-runtime — The runtime has a development surface.

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.

Current state

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.

Desired state

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.

Scope

• docs/MAJORDOMUS_UI.md
• .ai/repo/project/issues/I2680.yaml

Out of scope

• Stating a frame rate, a memory figure or an uptime that was not measured

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

• 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

Validation

• bin/majordomus plan validate

Evidence required

• observatory_gate_manifest

Evidence

Timeline

started

2026-10-14T12:31:23Z

verified

—

completed

2026-10-14T12:31:43Z

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/I2680.yaml. Read it back with majordomus plan show I2680.