Repository navigation
DRAFT-HOLD: v0.3.0 verify-a-release and new-chain NIST/SLSA pages (TO-VERIFY). Do not merge before v0.3.0 is live - #165
Draft
fosterstack-admin wants to merge 8 commits into
Draft
fosterstack-admin wants to merge 8 commits into
fosterstack-admin wants to merge 8 commits into
Conversation
… NIST/SLSA page, every claim TO-VERIFY; do not merge before v0.3.0 is live
Deploying www with
|
| Latest commit: |
c3482fe
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://7169f21e.www-4rw.pages.dev |
| Branch Preview URL: | https://www-v030-drafts-hold.www-4rw.pages.dev |
… TO-VERIFY); do not merge before v0.3.0 is live
…page, every row TO-VERIFY; do not merge before v0.3.0 is live
This was referenced Oct 11, 2026
…ign wording before the owner has signed (draft kept in the outbox)
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.
Held draft, never to be merged until the advisor says v0.3.0 is live. Three pages for the new release, every v0.3.0 claim marked [TO-VERIFY], noindex while a draft: /verify-a-release/ (ratified rule 78 shape: one page, 500 words, 10 commands, cosign/gh/jq only, both images; rule 80 wording), /how-our-pipeline-maps-to-nist-and-slsa/ for the new chain (designed against, never certified or compliant; nothing about SLSA Level 3 until the Build-stage tamper test passes), and a new developer-first /whats-new-fosterstack-cache-v0-3-0/ (what to check before you upgrade: Linux only, no -debug image, the 431 header rule, what stays the same, how the release is built, upgrading), listed in sitemap, llms.txt and the home list so the site-rot check passes. The what's-new facts come from the owner's answers (Oct 9: no macOS archives, no -debug image) and the cache lane's notes for the next release; everything not yet ratified or shipped is TO-VERIFY. Replaces the older held outline in #41.
Update (batch 12 b): the NIST/SLSA draft page also has a CISA Secure by Design section, seven rows, every product cell and every status cell [TO-VERIFY], built only from the internal gap map (cache lane, Oct 10); no pledge wording, no CISA mark, no endorsement, attestation or compliance claim; 'We do not claim to meet any of these goals until each row has been checked against the v0.3.0 release.' The pledge line waits until the owner has signed. Still draft, noindex, never merge before v0.3.0 is live and every row is met or justified.