Iteration 38 — PARKED: Sidecar Down After Host Reboot

Iteration 38 — PARKED: Sidecar Down After Host Reboot PARKED (PREFLIGHT) CYCLE 3 OPENED

In plain words: before every shift the loop checks the machine's vital signs. This time one vital failed: the production data-collector (the "sidecar") and its self-healing companion never came back after the computer restarted around 21:54 — they are switched off at the service level, and the built-in health monitor has been raising its hand about it every five minutes. Campaign law is strict here twice over: no measurement runs while the pipeline is unhealthy, and this loop is forbidden from touching production services — restarting them is the operator's call alone. So the loop did the only two things it may do: bookkeeping (the operator merged the cycle-2 pull request minutes before this firing, so a fresh cycle-3 branch and pull request were opened per the standing rule), and this honest status note. The next candidate fight (the κ tuning-dial interrogation) stays queued, untouched, ready the moment the pipeline is green again.

Preflight (A0): 2026-07-09 — load1 2.80/32c (≤24, flat vs load15 2.88) ✓ · no heavy nasimubd jobs ✓ · 22 GiB avail, si/so≈0 ✓ · clickhouse-server active ✓ · sidecar FAIL — opendeviationbar-sidecar + opendeviationbar-kintsugi(-catchup) inactive AND disabled after host reboot ≈21:54; heartbeat standing alert kintsugi|sidecar|kintsugi_telemetry|yesterday_completion (journal 23:19–23:45). Per A0 + rule 3c → PARKED; no compute.

What this firing did (and deliberately did not do)

Item	Detail	Ruling
Campaign-PR lifecycle	PR #591 (cycle 2, 42 commits, iters 21–37, LEDGER rows 28–46) MERGED by the operator 2026-07-09T23:44:31Z as `d5f75694` — an operator milestone. Fresh branch `loop/matrix-admission-campaign-cycle-3` cut off current main; cycle-3 campaign PR opened this firing (number in LEDGER row 49). No push to the dead cycle-2 branch.	DONE (rows 47, 49)
Preflight health	Sidecar + kintsugi systemd units inactive and disabled (did not survive the reboot); only the unrelated `fxview-sidecar` runs. Heartbeat (the repo's own check) alerting since at least 23:19.	FAIL → PARKED
Compute (H-017 κ sweep + M3)	Next frontier item per row 46 — requires capped runs against the campaign panel while the pipeline is healthy.	NOT RUN — queued, untouched
Prod services	Rule 6: this loop never touches systemd/monit/sidecar or any prod service. No restart attempted, no unit edited, no message sent.	UNTOUCHED
Ledger hygiene	Date-drift correction recorded (row 47): rows dated 2026-07-10→13 actually landed 2026-07-08/09 (commit timestamps); real dates resume from row 47. Sync note: main-checkout `git pull --ff-only` blocked by 344 dirty generated dashboard pages (only the two registry deploy artifacts may be discarded per rule A) — cycle-3 based on fetched `origin/main` directly.	RECORDED

Item

Detail

Ruling

Campaign-PR lifecycle

PR #591 (cycle 2, 42 commits, iters 21–37, LEDGER rows 28–46) MERGED by the operator 2026-07-09T23:44:31Z as d5f75694 — an operator milestone. Fresh branch loop/matrix-admission-campaign-cycle-3 cut off current main; cycle-3 campaign PR opened this firing (number in LEDGER row 49). No push to the dead cycle-2 branch.

DONE (rows 47, 49)

Preflight health

Sidecar + kintsugi systemd units inactive and disabled (did not survive the reboot); only the unrelated fxview-sidecar runs. Heartbeat (the repo's own check) alerting since at least 23:19.

FAIL → PARKED

Compute (H-017 κ sweep + M3)

Next frontier item per row 46 — requires capped runs against the campaign panel while the pipeline is healthy.

NOT RUN — queued, untouched

Prod services

Rule 6: this loop never touches systemd/monit/sidecar or any prod service. No restart attempted, no unit edited, no message sent.

UNTOUCHED

Ledger hygiene

Date-drift correction recorded (row 47): rows dated 2026-07-10→13 actually landed 2026-07-08/09 (commit timestamps); real dates resume from row 47. Sync note: main-checkout git pull --ff-only blocked by 344 dirty generated dashboard pages (only the two registry deploy artifacts may be discarded per rule A) — cycle-3 based on fetched origin/main directly.

RECORDED

Exactly what is awaited (rule 7)

#	Awaited	Who	Then
1	`opendeviationbar-sidecar` + `opendeviationbar-kintsugi` restored (or an explicit operator ruling that pipeline-down is intended, with a superseding preflight amendment)	Operator	Loop resumes at H-017 StabReg: κ-sensitivity sweep + M3 vs the six-instrument stack (row 46)
2	73 cycle-1 draft statuses (iters 11/13) review	Operator	First official FAIL/FRAGILE/CONDITIONAL declarations
3	Frontier #4 expiry-monitor precondition review (deferred 2026-07-03)	Operator	CTM-WATCH + e-detectors build

Awaited

Who

Then

opendeviationbar-sidecar + opendeviationbar-kintsugi restored (or an explicit operator ruling that pipeline-down is intended, with a superseding preflight amendment)

Operator

Loop resumes at H-017 StabReg: κ-sensitivity sweep + M3 vs the six-instrument stack (row 46)

73 cycle-1 draft statuses (iters 11/13) review

Operator

First official FAIL/FRAGILE/CONDITIONAL declarations

Frontier #4 expiry-monitor precondition review (deferred 2026-07-03)

Operator

CTM-WATCH + e-detectors build

▶ Next iteration

Next firing: re-run preflight. If the pipeline is green → H-017 StabReg ladder: κ-sensitivity sweep (does any defensible κ produce a non-trivial stable family on the 130-subject grid?) + M3 (selection-weight readouts vs the six-instrument stack); κ-fragile or stack-redundant → clean EXCLUDE, then B-01 advances to H-021 EILLS. If still red → one-line PARKED checkpoint row, no page spam, end the firing.

Iteration 38 · 2026-07-09 · PARKED (rows 47–49) — preflight A0-4 FAIL · cycle 3 opened · zero compute · zero synthetic data · append-only · prod services untouched