# Phase 6 — the untouched observer's verdict. **FAIL, and it is the night's most valuable finding.**

`demo-felhom` was hand-deployed to 0.231.0 at 22:40 and **not touched again**. Its whole nightly cycle
was recorded by a follow stream on the PVE host.

## Did every job run? Yes — all eight, on time.

| job | CEST | duration | outcome |
|---|---|---|---|
| db-dump | 02:30 | 674 ms | completed, `db_dump_completed (info)` |
| tier2-backup | 03:30 | **3 ms** | completed — **a no-op** |
| fill-watch | 03:30 | 0 s | completed |
| metrics-prune | 04:00 | 3 ms | completed |
| offbox-backup | 04:15 | **46.9 s** | completed |
| offsite-abandon-sweep | 05:10 | 0 s | completed |
| **offsite-proof** | **05:30** | 2.6 s | **REFUSED — could not run** |
| offsite-integrity | 06:00 | 0 s | **not due** (last success 24 h ago) — correct due-ness |

## Did any two overlap, and did the flag hold?

No two scheduled jobs overlapped on this box — the schedule spaces them 45–90 min apart and the
longest took 47 s. The flag was never contended here, so this box proves the **schedule**, not the
lock. Contention was tested on `demo-hp` (Phase 1).

## Did the proof pick one app and record a snapshot? **No — and that is the finding.**

```
03:30:02 [WARN] [offbox] proof: opengist has nowhere to restore to: nincs regisztralt
adatmeghajto, ezert nincs hova visszaallitani — a meghajtok megvannak, csak ujra kell...
```

**Cause established, not inferred:** `storage_paths: []` — zero registered storage paths, so
`offboxRestoreScratchDir` has nowhere to write a scratch and returns R-252's refusal. The same absence
explains `tier2-backup` at 3 ms: no second drive to mirror to.

`last_proof_result` is **ABSENT** and `proved_snapshots` is **ABSENT** — the error path reaches no
verdict, so nothing is recorded, so the hub cannot tell this from a controller too old to have the
feature. Filed **R-414**.

**The box is not unprotected**: its off-site backup ran normally in 46.9 s, because recovery units
live on the system data path, which needs no registration. It is the PROOF that cannot run.

## Did the integrity check run at full depth? No — and correctly.

`not due (last successful check 24h0m0s ago)`. The 7-day max age had not elapsed. Due-ness working as
designed; this box's last real full-depth check was 2026-08-31 04:00.

## **Did anything alarm on a healthy box?**

**No.** One event in the whole night — `db_dump_completed (info)`, which `severityNotifies` drops.
**Zero ERROR lines. One WARN**, and it is the R-414 refusal above. On a box left completely alone for
seven hours, the product was silent, and silence was the correct answer.