1Decision
Defer the independent-reproducibility requirement (supply-chain Stage 5, retained "in full" by the Personal Stable design) for stallion's Personal Stable candidates until the build host has the capacity for an independent rebuild.
2Why and evidence
An independent rebuild needs a second source tree plus a full output directory. The build host's /srv had 52G free on 2026-09-28, with out-lynx and out-stallion at 125G each, and no second tree exists. Owner decision 2026-09-28: reproducibility comes later and is not a priority now. Recorded as an explicit deferral instead of a silent skip, so the gap stays visible.
3Consequences
Until an independent rebuild matches byte-for-byte, every stallion ceremony record and docs/devices/support-policy.md entry marks the device's Personal Stable status as "reproducibility pending". What is lost meanwhile is detection of a compromised build host, or of a dirty source tree, between committed source and signed artifact (ADR-025's uncommitted frameworks/base edits are exactly the case a rebuild catches).
Mitigations kept: every build starts from committed branches with a clean git status in every touched project; candidate hashes are computed independently on the build host and on the signing host. Separately, vendor/.../guardian is not in the repo manifest, so an independent rebuild could not reproduce it today; that must be fixed before the first rebuild attempt.
4Review when
Build-host disk expanded; any sign of build-host compromise; before this device's build integrity is ever claimed to anyone other than the owner.
Read from docs/governance/decision-log.md, entry ADR-112.