I2697 — The public snapshot carries the p5 library, or says which scenes it cannot draw
The kiosk on the public site draws the proof scenes with p5, from the one reading taken at the published commit.
DONE wave 0 · p3 · implementation profile · parallel safe
Part of development-runtime — The runtime has a development surface.
Objective
The kiosk on the public site draws the proof scenes with p5, from the one reading taken at the published commit.
Why
A published UI snapshot (ADR 0141) must serve vendor/p5.min.js beside the scenes script, or the kiosk there draws the new scenes as unavailable.
Current state
ADR 0160 proposes the scenes; the Observatory of ADR 0158 has eight.
Desired state
The kiosk on the public site draws the proof scenes with p5, from the one reading taken at the published commit.
Scope
- scripts/site-build
- apps/majordomus-cli/src/ui/mod.rs
Out of scope
- Stating a frame rate or a figure that was not measured
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- The snapshot lists vendor/p5.min.js among its assets
- The snapshot status word is SNAPSHOT on every new scene
Validation
- bin/majordomus plan validate
Evidence required
- observatory_proof_scenes
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| observatory_proof_scenes | artifact | git show origin/gh-pages:ui/snapshot.json | jq -c .assets; node <scratch>/scenes.mjs (playwright chromium) reading [data-state] on https://majordomus.dev/ui/observatory/_scene/<scene>/ | published gh-pages 73a02db2f36 (master d11626680361): snapshot assets list assets/vendor/p5.min.js; on 2026-10-16T16:5xZ the seven ADR 0160 scenes proof, claims, surface, waves, matrix, registry, ladder each read 'SNAPSHOT · read once at d11626680361' with window.p5 loaded (the replayed ADR 0158 scenes activity, mesh, coop read REPLAY by design); case 3014_the_kiosk_draws_what_the_repository_proves ok at 09c334079f5 | 09c3340 |
Timeline
- started
- 2026-10-16T16:53:48Z
- verified
- 2026-10-16T16:53:54Z
- completed
- 2026-10-16T16:54:05Z
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/I2697.yaml. Read it back with majordomus plan show I2697.