Repository navigation
Freeze W3 Phase 1 amendment for published Checkwash 0.6.0 - #48
Merged
Merged
Conversation
taipei49314
marked this pull request as ready for review
October 5, 2026 17:45
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.
Bind the existing six-case W3 design to published Checkwash0.6.0 with a complete,
standard preregistration/v1 manifest. Preserve original cases, classes, twins,
fixtures, profiles, collector and installation inputs; preserve the0.5.0
manifest/catalog/snapshots as historical lineage. There is no runtime overlay
or relaxed trusted pin. The new frozen lineage contract identifies prior
exploration and the engine's published repairs without inventing case outcomes.
The new manifest is campaigns/checkwash-wave-3/manifest-v0.6.0.json, rawSHA256
e7beb853fbdbc3ffdbf426b4508f68aeea019b69a312fa0d3eb2a233d6f1f32b.
It points to the0.6.0 catalog/index/source snapshots and actual current package
bytes. Catalog attributes keep the new catalog's raw Git bytes stable.
The source re-pin is merged PR47 (b7786b2); this branch is based on that actual master commit.
Nelson's exact instruction,2026-10-06 Asia/Taipei:
This amendment is results-free. Its actual source approval/merge provenance
must be recorded independently; the previous Phase1 approval cannot approve
changed bytes. The final W3 startup decision remains human-review gated:
final_start=null, no FormalLifecycle/ticket/anchor, formal cases or formal POST.
Validation: source-only review and exact input identities; local product/parser/
tests NOT_RUN under POLICY work-machine-local. A new synthetic-authority unit
contract audits the shipped manifest's complete closed roots and original six
classes/twins through prepare_run, without running any arm or establishing
real approval/adoption. PR CI run37348560110/1 passed all three jobs at exact head5c7f20a: 1269 unit/policy/integration tests, both catalog gates and measure. Exact-source HOST50 qualification and actual independent approval/adoption remain pending.