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

I2678

The public Observatory replays events that were recorded, and says it is a replay

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: Let the three scenes of the mesh move on the public site without inventing a single event: from a capture of real events, redacted, with its manifest, labelled as a recorded replay with its original times.
Why: ADR 0158 refuses a scene drawn from anything that was not read, and the process that takes the public snapshot runs no mesh, so on majordomus.dev the scenes mesh, activity and coop are unavailable. The owner's specification of 2026-10-14 allows exactly one way to show them there: a replay of genuinely recorded events, never labelled live.
Now: The snapshot of /ui/observatory names mesh, activity and coop as unavailable with the reason mesh.peers gives in a process without a mesh. No capture of mesh events is tracked, and no capability answers one.
Wanted: A capture is a tracked, redacted record of real mesh events with a manifest: the window, the source capabilities, the original identities, what was removed and why. A capability answers it, the Observatory draws it under the words RECORDED REPLAY with the events' own times, and without a capture the scenes stay unavailable.
Done when: unknown: the record declares no `completion`
Risk: unknown: the record declares no `risk`

The public snapshot draws the mesh scenes only from a capture whose manifest it names, under a label that says replay, with the original times
A capture with an event whose source record is absent is refused, and the refusal names the event
Without a capture the three scenes are unavailable, as case 3011 holds today

Validation: bin/majordomus plan validatebash test/run.sh 3011_the_observatory_draws_nothing_it_did_not_read
Evidence required: recorded_replay_case
Evidence present: recorded_replay_case

Touches: apps/majordomus-cli/src/ui/observatory.rsshare/ui/observatory.jsdocs/MAJORDOMUS_UI.md.ai/repo/project/issues/I2678.yaml
Not: Synthetic events of any kind outside a test harnessPublishing intents, paths or message bodies of the mesh: an event stays its identity, kind, node and times
Depends on: none
Priority: p2
Profile: implementation
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.