Standalone persistence and direct login validation.

Validation scope

This record covers two connected boundaries: portability of a compact system image to different removable media, and normal remote entry into the resulting standalone system with persistent local authentication. It records observed results and their architectural meaning without disclosing reproduction-specific implementation detail.

Completed physical observations

• A compact Dwarf Goats image was provisioned onto removable media different from the medium used for the earlier laboratory state.
• The entire physical write was read back and cryptographically verified against the source image.
• The newly provisioned medium completed two standalone boots on Raspberry Pi 4.
• GNU Mach and the GNU Hurd reached a writable persistent root on the accepted boots.
• Writable state created by the running system remained present after reboot.
• The SSH server identity remained stable across reboot.
• The accepted standalone boots did not depend on TFTP.
• The runtime storage policy operated without dependence on one exact historical removable-media identity.
• Persistent local password authentication was stored by Dwarf Goats and remained valid after reboot.
• A normal network client connected directly, authenticated with the password stored on Dwarf Goats, and received an interactive dwarf shell.
• Ordinary login required neither a project-specific client private key nor a proxy hop or auxiliary authentication system.
• The final direct-login demonstration succeeded with the recovery bridge powered off.

Architectural meaning

Media portability is established within the demonstrated boundary. Successful provisioning to different removable media, full post-write verification, and repeated hardware boots distinguish the operating environment from a one-card laboratory artifact. Generalized runtime media handling was exercised by the physical result.

Persistence is system-level behavior, not merely writable runtime state. A writable root was reached, state was changed, the machine was rebooted, and the changed state was present afterward. Stable SSH server identity supplies an additional continuity check across those boots.

Standalone operation is independent of the earlier network boot dependency. The accepted boots completed without TFTP. The operating environment and its writable state resided on the provisioned system medium during the demonstrated boundary.

Remote entry now follows an ordinary client-to-system path. Authentication material persisted locally, survived reboot, and was accepted from a normal network client. The successful session did not require a project-specific client key, proxy, auxiliary authentication service, or powered recovery bridge.

The validated unit is now an operating environment. Taken together, the observations establish repeat boot, stable identity, writable continuity, and direct interactive entry. The result moves beyond separate boot, storage, and networking demonstrations into a physically usable standalone system boundary.

Attribution and limits

Dwarf Goats builds on GNU, GNU Mach, GNU Hurd, Dropbear, and the work of their upstream contributors. The demonstrated result includes Dwarf Goats-developed GNU Mach/Hurd support implemented by the Dwarf Goats project. No endorsement by or affiliation with the GNU Project, the Free Software Foundation, Richard Stallman, or upstream GNU Mach/Hurd contributors is implied.

This is a validation record, not a reproduction guide or source release. It intentionally omits storage geometry, authentication plumbing, internal topology, build machinery, and recovery procedures.