feat(contracts): TMPL01A0 publication contract artifacts - #8
Open
NWarila wants to merge 3 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TMPL01A0 — publication contract artifacts for
NWarila/ubi9-application-template. Files only; no workflow YAML. A later reusable workflow (A1) consumes these to publish signed multi-arch images.Built and verified by a construction spike (built + run, not authored from prose), then hardened across seven windows under a clean-room review that split cross-model: a Codex reviewer found a signer bypass, a mode-dependent suite, a vacuous mutation harness, and a provenance-completeness gap — all fixed and reproduced-as-closed.
Verification (reproducible from a clean
umask 0007clone →tools/install-trust-tree.sh→ suites):tests/contracts.sh→TOTAL 210/210tests/mutations.sh→ exit 0, 80/80 named rows, each observed exit compared to its declared code (with an anti-vacuity meta-test)926a31a8da99bfac98381254380df64806526d168252659c3271bdd3b3c9d5e6; all additions undercontracts/tools/tests/Trust boundary (four controls): four
gh attestation verifycalls with exact signer identity; the signer policy +check-signer.sh(requires workflow membership); the single tag-mutating pathverify-and-promote.sh; andverify-build-materials.sh/.pyover BuildKit/SLSA provenance (requires the exact statement type, BuildKit build type, and dependency-completeness flag). Trust tools are installed read-only (0555) with open-once descriptor binding.150-row manifest (sha256 → path)
🤖 Generated with Claude Code