Set the qualification freeze and evidence handoff #33

New issue

Open

opened 2026-10-16 09:16:44 +00:00 by phg · 0 comments

phg commented

2026-10-16 09:16:44 +00:00

Owner

Parent: Plan the signed IODD Tool prerelease
Type: grilling
Mode: HITL
Blocked by: Define the mise release stages and signing handoff

Question

Exactly which source/toolchain/artifact identities and evidence records must the later implementation handoff bind together, and what change invalidates which evidence before the signed prerelease may be published?

Make the existing accepted gates executable as a release handoff without weakening or duplicating them: the final frozen both-runtime suites and whole-branch review, complete app smoke/accessibility and workflow checks, manual/Homebrew lifecycle outcomes, Developer ID/notary/staple results, clean-user final-download Gatekeeper/install results, and final DMG URL/hash plus matching cask. Distinguish prior slice evidence from final release evidence and simulated cases from native observations. Define the minimal release manifest/decision checklist, responsible operator acknowledgments and requalification rules after changes to code, toolchain, bundle/signing identity, installer/cask logic or final bytes.

Keep software-only scope, original independent oracles/fault gates and every recovery-evidence guarantee. Close with phg's live acceptance of a concrete implementation-ready handoff; do not run the suite, assert that it passed, waive a gate or publish a prerelease. Surface any newly precise unresolved decision as a fresh child rather than pretending the route is clear.

Parent: [Plan the signed IODD Tool prerelease](https://git.s1q.dev/phg/iodd-tool/issues/27) Type: grilling Mode: HITL Blocked by: [Define the mise release stages and signing handoff](https://git.s1q.dev/phg/iodd-tool/issues/32) ## Question Exactly which source/toolchain/artifact identities and evidence records must the later implementation handoff bind together, and what change invalidates which evidence before the signed prerelease may be published? Make the existing accepted gates executable as a release handoff without weakening or duplicating them: the final frozen both-runtime suites and whole-branch review, complete app smoke/accessibility and workflow checks, manual/Homebrew lifecycle outcomes, Developer ID/notary/staple results, clean-user final-download Gatekeeper/install results, and final DMG URL/hash plus matching cask. Distinguish prior slice evidence from final release evidence and simulated cases from native observations. Define the minimal release manifest/decision checklist, responsible operator acknowledgments and requalification rules after changes to code, toolchain, bundle/signing identity, installer/cask logic or final bytes. Keep software-only scope, original independent oracles/fault gates and every recovery-evidence guarantee. Close with phg's live acceptance of a concrete implementation-ready handoff; do not run the suite, assert that it passed, waive a gate or publish a prerelease. Surface any newly precise unresolved decision as a fresh child rather than pretending the route is clear.

phg added the

wayfinder:grilling

label

2026-10-16 09:16:44 +00:00

phg referenced this issue

2026-10-16 09:17:17 +00:00

Plan the signed IODD Tool prerelease #27

phg referenced this issue

2026-10-16 09:59:05 +00:00

Choose the prerelease identity and download coordinates #30

phg referenced this issue

2026-10-16 12:00:09 +00:00