Derive non-inventory platform references from inventory

vnprc-agent commented

2026-06-27 04:54:06 +01:00

Contributor

User story: So that I can support multiple host architectures consistently, non-inventory repos should derive platform values from inventory instead of copying hard-coded system strings.

Part of the "sshHosts derivation & inventory naming" arc.

Platform strings such as x86_64-linux should be treated as inventory-owned data. Other Allod repos should derive platform/system values from inventory outputs or local configuration derived from inventory instead of repeating the literal.

Context: vnprc/profiles#74 fixes the profiles installer and validation examples by deriving the system from inventory.lib.supportedPlatforms, but a broader source scan still finds platform literals outside inventory source-of-truth machine declarations.

Initial scan targets to audit:

allod/vm/modules/qemu-guest.nix
allod/vm/flake.nix
allod/vm/README.md
allod/secrets/flake.nix
allod/inventory/flake.nix check-system/check-output plumbing, excluding machine platform declarations
allod/strategy docs and archived plans that present current validation commands

Acceptance criteria:

Machine platform declarations remain in allod/inventory as the source of truth.
Runtime/config/build code in other repos no longer hard-codes x86_64-linux when it can consume inventory-derived platform data.
Validation commands in current docs use derived systems instead of hard-coded check paths.
Archived plans are either left intentionally historical or updated only where they are still used as active operator guidance.

**User story:** So that I can support multiple host architectures consistently, non-inventory repos should derive platform values from inventory instead of copying hard-coded system strings. _Part of the "sshHosts derivation & inventory naming" arc._ --- Platform strings such as `x86_64-linux` should be treated as inventory-owned data. Other Allod repos should derive platform/system values from inventory outputs or local configuration derived from inventory instead of repeating the literal. Context: vnprc/profiles#74 fixes the profiles installer and validation examples by deriving the system from `inventory.lib.supportedPlatforms`, but a broader source scan still finds platform literals outside inventory source-of-truth machine declarations. Initial scan targets to audit: ```text allod/vm/modules/qemu-guest.nix allod/vm/flake.nix allod/vm/README.md allod/secrets/flake.nix allod/inventory/flake.nix check-system/check-output plumbing, excluding machine platform declarations allod/strategy docs and archived plans that present current validation commands ``` Acceptance criteria: - Machine platform declarations remain in `allod/inventory` as the source of truth. - Runtime/config/build code in other repos no longer hard-codes `x86_64-linux` when it can consume inventory-derived platform data. - Validation commands in current docs use derived systems instead of hard-coded check paths. - Archived plans are either left intentionally historical or updated only where they are still used as active operator guidance.