docs: the one file of section 11.4 step 3 the release does not carry - #10
Merged
Conversation
Found while implementing the synchronization workflow, and narrowed once spec#87 made the prose contracts travel with the release: `spec/PROVENANCE.md` is now the only file step 3 names that is not a release artefact. Its one sanctioned writer reads four files that are not artefacts either, so a workflow that has verified the release still has to clone `spec` to assemble it -- and no release published so far carries that writer at all, so a synchronization of either one stops with its sums and attestations checked and nothing written. Also records, settled, that "the newest release" is not `releases/latest`: every bundle so far is alpha, every alpha is published as a pre-release, and pre-releases are excluded from that endpoint, which answers 404 today.
euskadi31
force-pushed
the
docs/spec-issues-11-4
branch
from
August 24, 2026 21:42
566b2f8 to
9f5ac5c
Compare
euskadi31
changed the title
euskadi31
enabled auto-merge (squash)
August 24, 2026 21:43
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.
One entry under
## Open, one moved to## Settled upstream. Both found bywriting the section 11.4 workflow, both measured rather than reasoned.
spec/PROVENANCE.mdis the file step 3 cannot get from the release. Sincespec#87 every other file that step names is a release artefact — bundle, corpus,
schemas, and now the prose contracts. That one is not, and neither is anything
needed to build it:
tools/write_provenance.shreadsdocs/spec/provenance/body.md,docs/spec/provenance/<lang>.md,docs/generated/coverage.mdandgo run ./cmd/businessidc inspect, all of whichlive only in the
speccheckout. So an engine that has verified the releasestill has to clone
spec— a second fetch beside the attested one. And thewriter postdates both published tags: run
32779621303
verified
v0.1.1's sums and all four attestation identities on a runner, thenstopped because the commit that release was built from has no provenance writer.
Publishing the assembled file as an attested asset, exactly as the prose
contracts now are, would close it.
Settled: "the newest release" is not
releases/latest. Section 11.4 now saysto list the releases and take the most recent non-draft, which is what this
engine does. Recorded because it changed what the engine does.
Documentation only.