Wiki · Evidence & Verdicts
VERDICT: PASS — `producer-camera-attached` (2026-07-15)
[redacted: category] — 2 internal hostname. Nothing else was altered. The document is otherwise exactly as it is written in the repository, and the sha256 below is of the original, so what was ingested stays checkable.How to read this page
Three ways to read this page. Precise is the document itself, exactly as it is written in the repository. Plain and Clear were written for this website to help you meet that document — they are about it. They are not it, and they are not evidence.
Eighty-seven dated pages: receipts, pre-registrations, handoffs, validation records and review verdicts. A receipt is written at the moment a piece of work was checked. It names what was claimed, the commit and the seed, what was actually run, and the outcome in one of a small set of controlled words. Then it names what the work did not achieve. That last part is what makes it a receipt rather than an announcement. A pre-registration is the same discipline run in advance: the conditions that would count as a pass and the conditions that would falsify the claim are written down before the run, so neither can be adjusted once the numbers arrive.
That is why so many small dated stubs are an audit trail rather than noise. No one of them is meant to be a good read. The value is in the sequence and in the dates, because you can watch a prediction be registered, then the run happen, then the verdict land — sometimes against the prediction. Pages here record a falsified result, a rejected fix, a retracted overclaim, and a green receipt that turned out not to be reproducible from the commit that carried it. A record that carried only successes would be worth a good deal less than this one.
A gentle way in is to read a pre-registration first, so the shape becomes familiar, then a result page, then one of the corrections. This section sits off the main navigation on purpose: it is the record you check the rest of the site against, not the place to begin.
What it is not: documentation, and not a summary. Nothing here has been tidied in hindsight. Every entry reads as of its date, a later entry may overturn an earlier one, and the presence of a page is not a claim that its result stood.
Your browser cannot switch reading levels, so the document itself is shown.
Precise — the source document
This is the document. Rendered from the repository at the commit above, with nothing rewritten for the web. A gate re-renders it on every deploy and fails the build if a single byte differs.
Gate: producer-camera-attached (pre-registered PENDING in evidence/gates.ndjson at commit
0ae5e6d, BEFORE deploy; pre-registration docs/receipts/producer_reattach_remote_sense_spec.md;
typed spec docs/specs/producer_remote_sense_observe_only.md; lab-team MERGED VERDICT
SIGN-WITH-CHANGES with all 19 changes integrated).
Cure (Arm B, one composite ownership variable): container uni-producer (image
uni-producer:v1 = 340fb888c2d2, built on the chip from the pushed ref 5e1ba18, tarball
sha256 87bd7afe…c176 verified both sides) + uni-cam/uni-viewer-cam-fwd stopped (kept for
rollback) + uni-viewer-cam-fwd2 re-pointing host :3020. uni-colony, mc-server, the
world, and the UNI minds were never touched (their uptimes span the whole operation;
capture-before-destroy not triggered).
The RED window (collector NDJSON — every number re-derivable)
- Collector:
runs/red_producer_camera_collector.cjs(harness-managed, ≤5 s cadence) →runs/red_producer_camera_20260715T040735Z.ndjson(committed). Analyzer:runs/red_producer_camera_verdict.cjs→runs/red_producer_camera_verdict_out.json(committed). - Window: 2026-07-15 04:07:36Z → 04:21:08Z (13.5 min, 163 samples; +8 tail samples to 04:21:48 in the continuity checks).
| Clause | Requirement | Measured | Verdict |
|---|---|---|---|
| 1 — health | 200, verdict=LIVE, driver=producer, seam-joined colony_count=6, frame advancing ≥60 s |
LIVE/producer in every sample; colony_count=6 in 171/171 samples; frame 119 (04:07:46) → 169 (04:21:48) |
PASS |
| 2 — reattachment | ≥3 discriminating subject-reattachment events (sep ≥24 blocks → dist ≤12 within ≤15 s) | 31 star-change events; 18 discriminating; 18/18 reattached (e.g. b_roll UNI-1-2→UNI-1-3, separation 63.5, camera at 10.1 blocks in the same 5 s sample) |
PASS (6× margin) |
| 3 — no mutation | UNI roster identical; zero fenced EXECUTED; only camera RCON verbs | exactly 1 distinct 6-UNI roster across all samples; fenced counters {} (zero fenced choices — population sat at its C-peak, as pre-noted); Director flaps 0 |
PASS |
| 4 — legacy liveness | :4000 narration alive all window |
/stream HTTP 200 in 163/163 samples |
PASS |
| 5 — restart repetition | mid-window Producer kill → recovery, ≥1 further reattachment, still one Director |
04:13:35Z rpc kill: pid <13247.637.0> → new <13247.1070.0> in ≤4 s; Director kept pid <13247.636.0> (survived — camera never blinked); 11 post-restart discriminating+reattached events (first at 04:13:52, 17 s after the kill); Director present in every list, 0 flaps |
PASS |
Falsifiers: none fired — no V4 (18/18 events reattached), driver=producer throughout, no
world/colony mutation, transport never broke (colony_count never left 6), no kick-fight.
INCONCLUSIVE conditions: not triggered — 38 cut directives in-window (not zero);
perseveration tripwire max same-fenced run = 0 (vs K=40).
Honest notes (limits of this verdict)
- Analyzer limitation, conservative: the event stream is keyed by producer frame; the mid-window restart resets frames, so pre/post frame-spaces overlap (110–169) — the dedup DROPS some post-restart entries there (undercount) and can fabricate ≤2 boundary artifacts. The 11 post-restart events were therefore verified by timestamp, and the ≥3 threshold holds under the worst discount. Fix belongs in the analyzer if this gate is ever re-run.
- The fenced dead limbs stayed latent (population at C-peak all window) — the observe-only
fence's perseveration regime is instrumented (
fencedcounters on/producer/health) but NOT exercised by this RED, exactly as pre-registered. No claim is made about behaviour under population loss. - Firewall persistence gap: LAN
:4200is open via a runtime nft rule (audite278400086a4484d); it dies on reboot until the nftables boot file carries it (follow-up task chip spawned; do NOTreloadnftables — it would flush netavark and break the ERP stack). The registry entry[redacted: internal-hostname]:4200carriesnvuntil its probe is wired into the observability panel. - Two Producer minds now sense the same colony (pre-registered honesty line): the living
v2 Producer inside
uni-colonykeeps its cast hands + the legacy:4000/streamnarration; the new fenced HEAD node owns the camera + its own:4200/stream. Only one mind has hands. uni-camignored SIGTERM at cutover and took podman's 10 s SIGKILL fallback (stateless camera process; no data). Its image/container are intact for rollback (deploy/uni-producer/rollback.sh= exact Arm A).
Claim fence
This gate demonstrates the named BEHAVIOUR only: the deployed Producer node's EFE decisions
measurably drive the world camera (directive → camera motion, correlated server-side). It is a
broadcast-plumbing/mechanism claim. It carries zero evidential weight for awareness,
consciousness, or life, and does not touch the science gates (forage-pureworld-graduation
remains the colony-scene-on-program blocker per goLiveGate).
Hand-off to the studio agent
producer-camera-attached = PASS unblocks the camera half of the colony scene. The narration
half: point the OBS colony-scene browser source (OVERLOOK / cap_overlook) at
http://[redacted: internal-hostname]:4200/stream (the HEAD page whose narration + cards + camera
iframe are ONE mind — VIEWER_URL is baked to the LAN :3020 camera) instead of the legacy
:4000/stream, so the on-air narration matches the picture. That re-point is a studio-track
change with its own gate (verify_overlays + the pre-air driver=producer check now answers
on :4200/producer/health).
sha256 d64fd267d7212735 — of the original file, so what was ingested stays checkable.
Plain — written for this website, not the source document
A verdict page. The gate was registered as pending before the work, then measured over a window and marked pass. The claim is narrow and mechanical: the deployed node's own decisions measurably move the world camera, so the picture follows the subject. Several clauses were checked against samples collected every few seconds, including a deliberate mid-window kill to see whether it recovered. The page then spends as much room on its limits as on the result, and ends by saying the finding carries no weight at all for awareness or life.
Plain · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is d64fd267d7212735
Clear — written for this website, not the source document
A verdict receipt: the file recording what was run and what came out. The gate was pre-registered as pending before the deploy, with a written specification and a design review behind it, and this page records the measured window that settles it.
The change under test is described as one composite variable: a new container, two older ones stopped but kept for rollback, and a forwarder re-pointed. The page is careful about what was not touched, naming the colony, the world and the minds, and noting their uptimes span the whole operation, so the capture procedure was never triggered.
The measurement is a stream of samples written to a committed file, with a committed analyser, so every number can be re-derived rather than taken on trust. Each clause gets a row. The health reading through the window, and the count of discriminating events where the camera followed a change of subject. The absence of any mutation to the world, and the continued liveness of the older narration path. One clause kills the process mid-window and requires recovery plus further events afterwards, which happened while the part that drives the camera survived untouched.
The honest notes are the most useful section. The analyser has a limitation that undercounts events after the restart, so those were re-checked by timestamp. The threshold holds even under the worst discount, and the fix is named as belonging to the analyser if this gate is ever re-run. One instrumented behaviour was never exercised, exactly as pre-registered, so no claim is made about it. A firewall rule opening a port does not survive a reboot, and a follow-up is spawned with a warning about a reload that would break something else. And two minds now sense the same colony, which is recorded as a pre-registered honesty line, with only one of them having hands.
The claim fence — the limit on what this may be said to show — is explicit. This shows the named behaviour only, that the node's decisions drive the camera, correlated on the server side. It is a plumbing and mechanism claim, it carries zero evidential weight for awareness or life, and it does not touch the science gates. A closing handoff tells the next agent what to re-point so the narration matches the picture, and notes that the change carries its own gate.
Clear · written 2026-08-01 by claude-opus-5 · not yet checked by a person · about the document whose sha256 is d64fd267d7212735