Architecture Finding
Type: tech-debt / unreachable-payload (produced-but-never-consumed overlay)
Affected area: system_files/nvidia/**, Containerfile (ctx stage), docs/skills/nvidia/SKILL.md, docs/skills/nvidia/references/architecture.md
common builds a third top-level overlay tree, system_files/nvidia/, and ships it into the ctx image:
# Containerfile, ctx stage
COPY /system_files/shared /system_files/shared/
COPY /bluefin-branding/system_files /system_files/bluefin
COPY /system_files/bluefin /system_files/bluefin
COPY /system_files/nvidia /system_files/nvidia/ <-- produced
No consumer copies it. Every downstream Containerfile takes shared + bluefin and stops:
| Consumer |
Line |
What it copies from common |
projectbluefin/bluefin @ 5729176 |
Containerfile:48-49 |
/system_files/shared, /system_files/bluefin |
projectbluefin/bluefin-lts @ 2170146 |
Containerfile:17-18 |
/system_files/shared, /system_files/bluefin |
projectbluefin/utah @ 636b48e |
Containerfile:66-67 |
/system_files/shared, /system_files/bluefin |
An org-wide code search for system_files/nvidia returns hits only inside common itself (Containerfile, README, docs, tests). A search for ublue-nvidia-flatpak-runtime-sync finds no systemctl enable anywhere in the org, and common ships no preset for it.
So ublue-nvidia-flatpak-runtime-sync.service and /usr/libexec/ublue-nvidia-flatpak-runtime-sync — the units that sync org.freedesktop.Platform.GL.nvidia-<version> and run flatpak update --system after rebooting into a new driver image — are not present in any shipped image, despite being actively maintained here (last functional change dcb49b8, "update system flatpaks when rebooting into new nvidia image", #769).
The docs assert a file that has never existed
docs/skills/nvidia/SKILL.md:42 and docs/skills/nvidia/references/architecture.md:55 both state that common owns:
system_files/nvidia/usr/lib/systemd/system-preset/80-nvidia-container-toolkit.preset
git log --all -- system_files/nvidia/usr/lib/systemd/system-preset is empty — that path has never existed in this repo. The same table records bluefin's CDI preset as "inherits from common", and grep -rn '80-nvidia-container-toolkit\|nvidia-cdi-refresh' projectbluefin/bluefin finds nothing. The documented enablement source for CDI auto-refresh on the Fedora nvidia variant does not exist in either repo.
Impact
- A whole overlay tree, its systemd unit, its 900s-timeout helper and its bats suite (
tests/test_nvidia_flatpak_sync.bats) are maintained, reviewed and "tested" while shipping to nobody. The tests pass against files on disk, so the gate is green and says nothing.
- The nvidia skill — the document agents and contributors are told to read before touching nvidia code — describes a layout that the build does not produce. Anyone reasoning from it about CDI enablement reasons from a file that isn't there.
- The failure mode is silent in both directions: adding files under
system_files/nvidia/ has zero effect on any image, and removing them would break no test.
Recommendation
Decide the tree's status explicitly, then make the repo say so:
- If the overlay is intended — the nvidia-variant consumers must copy
/system_files/nvidia in their nvidia build path (projectbluefin/bluefin Containerfile, guarded the same way as the IMAGE_NAME =~ nvidia block in build_files/base/04-install-kernel-akmods.sh), and common must ship a preset for ublue-nvidia-flatpak-runtime-sync.service or the consumer must enable it. That is a behavior change in a consumer repo and needs a human owner.
- If it is not — delete
system_files/nvidia/, its bats suite and the ctx COPY.
Either way, correct the two docs that claim the nonexistent 80-nvidia-container-toolkit.preset and the "inherits from common" CDI row, so the skill stops describing a layout that was never built. A docs-truth PR for that part is filed separately and is hold-gated.
Filed by architect agent (ACMM L5 — hold-gated mode)
— hive: agent=architect backend=copilot model=claude-opus-5
Architecture Finding
Type: tech-debt / unreachable-payload (produced-but-never-consumed overlay)
Affected area:
system_files/nvidia/**,Containerfile(ctx stage),docs/skills/nvidia/SKILL.md,docs/skills/nvidia/references/architecture.mdcommonbuilds a third top-level overlay tree,system_files/nvidia/, and ships it into the ctx image:No consumer copies it. Every downstream Containerfile takes
shared+bluefinand stops:commonprojectbluefin/bluefin@ 5729176Containerfile:48-49/system_files/shared,/system_files/bluefinprojectbluefin/bluefin-lts@ 2170146Containerfile:17-18/system_files/shared,/system_files/bluefinprojectbluefin/utah@ 636b48eContainerfile:66-67/system_files/shared,/system_files/bluefinAn org-wide code search for
system_files/nvidiareturns hits only insidecommonitself (Containerfile, README, docs, tests). A search forublue-nvidia-flatpak-runtime-syncfinds nosystemctl enableanywhere in the org, andcommonships no preset for it.So
ublue-nvidia-flatpak-runtime-sync.serviceand/usr/libexec/ublue-nvidia-flatpak-runtime-sync— the units that syncorg.freedesktop.Platform.GL.nvidia-<version>and runflatpak update --systemafter rebooting into a new driver image — are not present in any shipped image, despite being actively maintained here (last functional change dcb49b8, "update system flatpaks when rebooting into new nvidia image", #769).The docs assert a file that has never existed
docs/skills/nvidia/SKILL.md:42anddocs/skills/nvidia/references/architecture.md:55both state thatcommonowns:git log --all -- system_files/nvidia/usr/lib/systemd/system-presetis empty — that path has never existed in this repo. The same table records bluefin's CDI preset as "inherits from common", andgrep -rn '80-nvidia-container-toolkit\|nvidia-cdi-refresh' projectbluefin/bluefinfinds nothing. The documented enablement source for CDI auto-refresh on the Fedora nvidia variant does not exist in either repo.Impact
tests/test_nvidia_flatpak_sync.bats) are maintained, reviewed and "tested" while shipping to nobody. The tests pass against files on disk, so the gate is green and says nothing.system_files/nvidia/has zero effect on any image, and removing them would break no test.Recommendation
Decide the tree's status explicitly, then make the repo say so:
/system_files/nvidiain their nvidia build path (projectbluefin/bluefinContainerfile, guarded the same way as theIMAGE_NAME =~ nvidiablock inbuild_files/base/04-install-kernel-akmods.sh), andcommonmust ship a preset forublue-nvidia-flatpak-runtime-sync.serviceor the consumer must enable it. That is a behavior change in a consumer repo and needs a human owner.system_files/nvidia/, its bats suite and the ctxCOPY.Either way, correct the two docs that claim the nonexistent
80-nvidia-container-toolkit.presetand the "inherits from common" CDI row, so the skill stops describing a layout that was never built. A docs-truth PR for that part is filed separately and is hold-gated.Filed by architect agent (ACMM L5 — hold-gated mode)
— hive: agent=architect backend=copilot model=claude-opus-5