verify(oci): record the field-found evidence gap; defer P06 to v1.131 - #325
Merged
Conversation
FV-FALCON-OCI-001 claimed distribution was "validated end-to-end" on v1.127/ v1.128. That evidence was NOT sufficient, and jess proved it in the field: falcon-rate:1.129.0 shipped as a raw core module. My check confirmed the OCI config mediaType — which reads "component" regardless of the payload — so it verified the WRAPPER, not the BYTES. Record it honestly rather than quietly re-verifying: the gap, its root cause (no_std dropped `cabi_realloc`, wit-bindgen-rt only provides it when std is linked; the build failure was then swallowed by `|| true`), and the four strengthenings that close it (#323, #324) — cabi_realloc exported, build failures abort, an 8-byte HEADER assert on every component (verified to REJECT the published 1.129.0 artifact), and by-name artifact selection. This is the release-planning loop working as intended: a field regression re-opens the requirement's verification rather than being patched silently. Also defers SWREQ-FALCON-MATHF32-P06 (Cody-Waite argument reduction) from v1.130 to v1.131 — an explicit, logged scope move, not a silent slip. It is the multi-week proof of the four and is not ready; v1.130 is a fix release that republishes falcon-rate as a real component. rivet validate: PASS. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvusAXYbHLyv3uTzfBcMbG
avrabe
enabled auto-merge (squash)
July 30, 2026 03:47
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.
The honest correction
FV-FALCON-OCI-001claimed distribution was "validated end-to-end" on v1.127/v1.128. That evidence was not sufficient, and jess proved it in the field:falcon-rate:1.129.0shipped as a raw core module. My check confirmed the OCIconfig.mediaType— which reads "component" regardless of the payload — so it verified the wrapper, not the bytes.Rather than quietly re-verify, the artifact now records:
no_stddroppedcabi_realloc(wit-bindgen-rt supplies it only when std is linked,#[cfg(not(target_env = "p2"))]), andbuild-components.shswallowed the resulting failure with|| true,cabi_reallocexported, build failures abort the bundle, an 8-byte header assert on every component (verified to reject the published 1.129.0 artifact), and by-name artifact selection.This is the release-planning loop working as designed — a field regression re-opens the requirement's verification instead of being patched silently.
Scope move (explicit, not a silent slip)
SWREQ-FALCON-MATHF32-P06(Cody-Waite argument reduction) moves v1.130 → v1.131. It's the hardest of the four proofs and isn't ready; v1.130 is a fix release whose job is republishingfalcon-rateas a real component — which jess is blocked on, and which the held wasm.directory registration depends on.rivet validate: PASS. Code-free.🤖 Generated with Claude Code