# Independent uptime onboarding ## Historical evidence Names, paths, findings and gate counts below describe the recorded tree, not today's onboarding contract. Current contract: [onboarding](../../specs/NL-SPEC-A7K4QX2M-nuguland-agent-onboarding/index.md). Step 5 re-measure, 2026-11-14: a new ordinary popup after every legacy feature moved onto the registry. A fresh child agent (Claude Opus, high reasoning) worked in a throwaway `just worktree` checkout from the public contracts: `.system/`, `Registry.qml`, `FeatureEntry.qml`, and `features/` as references. The feature, `uptime`, reads `/proc/uptime` and `/proc/loadavg`, formats them in a pure model, and shows them in a popup with the bar label "up" and one `uptime` IPC handler. Neither run was merged; both worktrees were removed after the parent checked their trees. ## Result | Metric | Pilot prediction | OSD | Tray | Uptime | | --- | --- | --- | --- | --- | | Production files changed outside the feature | 2 | 8 | 7 | 2 | | Test and harness files changed | 4 | 9 | 9 | 0 | | Host-internal files read | 0 | about 12 | about 14 | about 6 | | Gate runs to first green | unmeasured | 11 (6 red) | 9 (2 red) | 1 red `ui-test`, then green | The two production files are `Registry.qml` (import, service, one entry) and `shell.qml` (the IPC handler RULES keeps explicit there). The parent confirmed both commits with `git show --stat` and a search for `uptime` outside `features/uptime/`, and viewed the suite's screenshots. The phase exit "one registry entry plus feature-local files is the entire wiring for an ordinary feature" holds, with IPC in `shell.qml` as RULES requires. ## Contamination Child sessions run an automatic adversarial advisor (the `dilemma` extension) that may read host internals. - First run: the advisor told the child, before it wrote any QML, which hidden rules the catalog test and the double check enforce. Same file counts; its process metrics are not credited. - Second run: the advisor was meant to be off, but a project setting in the untrusted worktree did not disable it. Up to the first red `just ui-test uptime` the run was clean: the child wrote all ten files, and `just fmt`, `just lint` and `just test` passed. The advisor then diagnosed the failure from host internals; the fix and the `open()` gap below came through it. The file counts come from the child's own authoring in both runs. The gate-run count after the first failure is advisor-assisted. ## Contract gaps found and closed - An entry's `height` is the popup card including 48 px padding; `FeatureEntry.qml` now says so. - Every popup entry must set `component`, `source` and `visual`; `FeatureEntry.qml` now says so. - Doubles must pass `assertPureService`; RULES now lists its rules. - A suite's `open(name, ready)` uses `ready`'s return value as the primary control's rect and asserts it on screen; RULES now says so. ## Open - `FileView.reload()` returns the previous text until the load finishes; the child found `features/system/Resources.qml` reading right after `reload()`, which would show values one refresh behind. Not checked by the parent. - Undocumented: when `opening` fires relative to the panel loading, how first focus enters a popup, and that `Registry.qml` entries must keep the layout `test-fixtures/sources.js` parses. - No contract says how a time-based value refreshes without events; the child polled while open via `opening`/`dismissed`.