From 2fdf1d3cc4a1b9d4eff3dfb4c0b33df29c395ddd Mon Sep 17 00:00:00 2001 From: DCCONSTRUCTIONS Date: Mon, 7 Sep 2026 11:56:32 +0300 Subject: [PATCH] Record private K1 installer release and Mini installation acceptance --- .../2026-09-07-k1-private-installer-r2.md | 48 +++++++++++++++++++ 1 file changed, 48 insertions(+) diff --git a/docs/audits/2026-09-07-k1-private-installer-r2.md b/docs/audits/2026-09-07-k1-private-installer-r2.md index 37189a1..ef3d9be 100644 --- a/docs/audits/2026-09-07-k1-private-installer-r2.md +++ b/docs/audits/2026-09-07-k1-private-installer-r2.md @@ -79,3 +79,51 @@ requested. A second scanner, new firmware or different host platform is not accepted by packaging and software regression alone. Vendor reference: https://www.xgrids.com/intl/support/download?page=K1 + +## Release and installation acceptance + +Source commit `d8cc5367c4f55973d5688a0627298cf5137649a6` is published to +`origin/main`. Both package provenances bind that exact commit. The private +release directory is `private/releases/mission-core-node-k1-20260907`; it +contains the two packages, `install` and `SHA256SUMS` and is excluded from Git. + +| Package | Bytes | SHA-256 | +| --- | ---: | --- | +| `mission-core-node_0.8.0_amd64.deb` | 109813216 | `7ec59efe5b5ee6e48771f7302281d28fd96dd6d425678ddfaeff18f8fd79773e` | +| `mission-core-xgrids-k1_0.1.0+private.1_amd64.deb` | 318106524 | `ec28e0fd83db88ec37903734ae4779aea4d716fe47905ab978a64d420513b1ea` | + +The authorized build read the existing fixed application Keychain item in +memory and supplied it to the private package builder. No separate raw-key +transfer was used. The earlier rejected direct-import proposal was not run. +The prepared package was transferred over the previously trusted Mini SSH +identity into a mode-0700 release directory with mode-0600 packages. Every +transferred checksum matched. APT simulation selected one upgrade and one new +package, with no removals. + +The owner entered the normal Ubuntu administrator password in the installer +window. Installation returned exit 0. On 2026-09-07 at 08:49 UTC, the Mini +started Node 0.8.0 and K1 0.1.0+private.1. The private package's `postinst` +successfully prepared the host-encrypted material before starting the worker. +Both services are active/running with `NRestarts=0`; Bluetooth and +NetworkManager are active. Installed package provenance matches the release. + +The installed source tree has exactly the declared 85 Python modules; the old +`laboratory/execution.py` is absent after Debian migration. The new full Linux +worker, including its media imports, starts and supplies fresh/available/idle +state to Core. This closes the full Linux import check that the Mac synthetic +test could not perform. The original `ndc-rover-006` identity and binding are +preserved. Canonical Core port 8000 remains operational. No device command was +sent as part of packaging and installation acceptance. + +Five R2 structured blocks were added to Ops K1 card #3, retaining all 34 prior +blocks and its historical state. Node card #76 received progress comment +`e4f1fc04-be54-4172-ada7-9c672db4681a`; its frozen 26-block baseline was not +changed. Installer preparation is accepted separately from physical K1 +authentication, Bridge/live through both UIs, Ubuntu outage/reboot recovery and +installation on a second board. Those physical checkers remain open. + +The owner subsequently confirmed the K1 is powered and Chrome cache was +cleared for a Core Fleet UI test. Read-only observations are retained under +`private/acceptance/k1-node080-20260907-core-ui`, with UTC/monotonic timestamps, +operator notes and hashes. Starting that test does not itself establish a +successful hardware connection.