Repository navigation
Conversation
Upload image, draw image and free image join the spec: their bytes, their decoding, the image table beside the mask table in the retained state, the validation rules (ids below 2^16 in their own space, sides 1 to 2^14, live pixel bytes at most 2^28, a draw naming a live image with its source inside it) and the list's byte limit growing by 2^28. The contract extends theorem_validated_bounds to image bytes and source rectangles. Spec and contracts only (CLAUDE.md rule 3): exec.rs, lemmas.rs, examples.rs and independent.rs do not yet cover the new items, so Verus does not pass at this commit; the next commit has the implementation and proofs. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
….10) The decoder reads tags 7 to 9, the encoder writes them, and the validator keeps a table of images beside its masks, all proven against the previous commit's spec: Verus 100 verified, 0 errors with independent.rs set aside (it still has to learn the new items; the next commits do that, and mutations). Examples evaluate the new bytes and each new rule both ways on the spec. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…(6.10) Tags 7 to 9 in the second form (a fold over maps by id, a reading by position), and the equivalence with the spec extended: i_read is decode, and i_check is validate over masks and images, on every list. Verus: 131 verified, 0 errors. Unlike 5.17a's definitions this extension was not written blind: the session that extended the spec wrote it, from item 6.10's paragraph, and the file's header says so. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…items (6.10) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…them until 6.12 Conformance: a second decoder and validator for tags 7 to 9, random lists, hand-built cases per rule, the encoder's pixel check, the draw bytes, and a list past 5.17a's limit that reads as an upload. clazel-gpu refuses a list that holds an image item, with a comment pointing at 6.12. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
130 mutations (79 of 5.17a's, 11 of them re-anchored for the new spec text, and 51 new, one or more per new rule), all killed by a theorem with a certificate: 130 killed, 0 incidental, 0 survived. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…t near 0.04 s natively (6.10) With the Miri branches forced on, natively: differential_random_lists 0.039 s, differential_hostile_bytes 0.041 s, the rest under 0.001 s. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Member
Author
|
Interim result of
The proof evidence I do have comes from separate runs: Verus 131 verified, 0 errors, and 130 of 130 mutations killed with certificates ( |
atiernan
had a problem deploying
to
full-verification
November 17, 2026 14:22 — with
GitHub Actions
Error
… and changed-crate CI) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> # Conflicts: # crates/clazel-displaylist/README.md
atiernan
had a problem deploying
to
full-verification
November 19, 2026 23:57 — with
GitHub Actions
Error
…ri (6.10) CI took 457 s for 40 random lists and 482 s for 200 hostile byte strings under Miri, over the 300 s limit for one test. Under Miri they now run 8 and 40, about 95 s each at the rate CI measured. The normal test job is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
atiernan
requested a deployment
to
full-verification
November 20, 2026 01:39 — with
GitHub Actions
Waiting
This branch is waiting to be deployed
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
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.
Phase 6 item 6.10, in
clazel-displaylist(tier 2 crate; the tier is unchanged).What it adds
MAX_LIST_BYTESgrows from 2^27 to 2^27 + 2^28.Masksis now{table, images}).theorem_validated_boundsnow also covers image bytes, andimage_sources_inside.Commits
The spec and contracts come first, alone, in 8aef016 (rule 3). Verus doesn't pass at that commit. Then come the proofs, the independent transcription, examples and docs, tests, mutations, the Miri sizing and the status row.
Evidence so far (local)
expectwas relabelled.cargo xtask checkpasses.cargo xtask verify --changed: it was still running locally when this PR was opened, queued behind other proof jobs. The result goes in a comment.Caveats
MAX_LIST_BYTES(384 MiB) is now aboveclazel-gpu's socket limitLIST_MAX(256 MiB). Lists between the two sizes are refused, never misread. Item 6.12 must settle this with its second-channel decision, along with theGPU_LIMITcomment incrates/clazel/tests/hostile_graphics.rs.in_rangehas no stateless bound on how far a draw's source rectangle extends; that is a rule of the walk (image_sources_inside). Guaranteeing that every live image's sides are at most 2^14 would need one more invariant, which isn't added.clazel-gpurefuses image items: the builder returnsError::Refusedand the reference returnsNone.🤖 Generated with Claude Code