GNU Guix System

System ownership

Require evidence that Guix supplies the system configuration and lifecycle.

1. What evidence establishes that this installation is GNU Guix System rather than another distribution running Guix? definition
2. Which observed configurations belong to the system, Guix Home or personal package profiles? boundary

Variant and target

Record the target environment and departures introduced by custom channels or system components.

1. Which image, configuration repository and channel revisions establish this installation's origin? provenance
2. Which custom components affect whether the installation should be described as stock GNU Guix System or a derivative? boundary

Declaration completeness

Assess whether the retained declaration and supporting inputs explain the generated system.

1. Which operating-system expression, imported modules, local files and invocation options produced this generation? provenance
2. Which inputs depend on local paths, environment values or external resources that another builder would lack? boundary

Service effects

Trace how declared services contribute accounts, files, activation work and runtime services.

1. Which service types and extensions supply each relevant account, configuration file and Shepherd service? definition
2. What dependent configuration or runtime behaviour would change if this service declaration were modified? action

Revision reconstruction

Require recoverable channel revisions and distinguish recorded inputs from demonstrated reproducibility.

1. Which exact channel commits and authentication information accompanied the Guix used to build this system? provenance
2. Can those revisions and the configuration inputs still be retrieved and evaluated with an appropriate Guix invocation? action

Substitutes and build evidence

Separate acceptance of signed substitutes from evidence that independent builds agree.

1. Which system dependencies were built locally, obtained from substitutes or imported through another route? provenance
2. Which keys authorise accepted substitutes, and what independent rebuild evidence exists for critical outputs? provenance

Transition readiness

Establish evidence and authority for moving a candidate into service.

1. Which generation is built, selected, booted and scheduled for the next boot? measurement
2. Which changes require service intervention or reboot, and what validation must precede reconfiguration? action

Recoverable generation

Identify a usable recovery target without assuming that switching generations restores mutable state.

1. Which retained generation has evidence of successful operation, and are its required store items and boot entry available? provenance
2. Which database migrations, secrets or persistent files could prevent that generation from working after a rollback? boundary
3. How can an authorised operator select the recovery generation if normal boot or remote access fails? action

Boot path fit

Assess the path from firmware to a mounted root filesystem and usable system.

1. Do the declared kernel, firmware and initrd support the target's storage, network and other required devices? measurement
2. Do bootloader targets, filesystem identifiers and mapped-device declarations match the intended installation? measurement

Shepherd service health

Relate Shepherd observations and service-specific probes to the selected system configuration.

1. Which expected Shepherd services are running, stopped or failing, and what do application-level probes show? measurement
2. Which intervention belongs in the operating-system declaration, and which is a temporary runtime action? action

State and secret boundary

Assess persistence, backup and secret provisioning independently of system generations.

1. Which service data, home directories and machine-specific files require separate backup and restoration? boundary
2. How are credentials provisioned without embedding sensitive contents in readable store artifacts or shared configuration? action

Collection consequences

Evaluate what can be reclaimed while retaining required rollback and rebuild options.

1. Which profiles, generations and explicit garbage-collection roots retain the store items required for recovery? relation
2. How much space could be reclaimed, and which recovery options would disappear after deleting generations and collecting unreferenced items? measurement

Check these first

Recalled without web access and unsourced; every item is a lead to verify.

1. Which of these check these first hold for the sense of GNU Guix System this model covers, and on what evidence? provenance

Standards and regulation

Recalled without web access and unsourced; every item is a lead to verify.

1. Which of these standards and regulation hold for the sense of GNU Guix System this model covers, and on what evidence? provenance

Real-world use

Recalled without web access and unsourced; every item is a lead to verify.

1. Which of these real-world use hold for the sense of GNU Guix System this model covers, and on what evidence? provenance

Failure modes and hazards

Recalled without web access and unsourced; every item is a lead to verify.

1. Which of these failure modes and hazards hold for the sense of GNU Guix System this model covers, and on what evidence? provenance

Neighbouring kinds and how to tell them apart

Recalled without web access and unsourced; every item is a lead to verify.

1. Which of these neighbouring kinds and how to tell them apart hold for the sense of GNU Guix System this model covers, and on what evidence? provenance