docs: fix stale non-Clifford T/CCZ claims, add T/CCZ benchmarks (#478 follow-up) - #479
Draft
arniber21 wants to merge 1 commit into
Draft
docs: fix stale non-Clifford T/CCZ claims, add T/CCZ benchmarks (#478 follow-up)#479arniber21 wants to merge 1 commit into
arniber21 wants to merge 1 commit into
Conversation
…follow-up) PR #312 (Jul 20) fixed stale non-Clifford doc claims relative to the #283 QEC-workload-IR state, but #354 (Jul 24) landed the actual frontend wiring four days later, making those fixes stale again. Three docs still claimed logical_t/logical_tdag/logical_ccz "do not currently compile through quonc (tracked in #311)" when #311 is closed-completed and they compile end-to-end. - benchmark_suite.md: replace the comment-only surface_d3_t_placeholder.qn with real surface_d3_t.qn / surface_d3_ccz.qn benchmarks; register them in catalog.yaml (ci: smoke); describe the magic-state resource-report fields. - magic_state_operations.md: drop the stale "Not yet reachable from .qn source" limitation; note the source-prelude binding (#311/#354). - na-ft-demo.mdx: correct the non-Clifford limitations bullet to state the ops compile end-to-end while keeping the honest scope (no distillation factory, metadata-only, not a threshold claim). Verified: both benchmarks compile through quonc with t_count/ccz_count/ magic_state_demand populated; samples_catalog smoke-typecheck passes; assert-validation-docs passes.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Owner
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Aug 5, 2026
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.
PR #312 (Jul 20) fixed stale non-Clifford doc claims relative to the #283
QEC-workload-IR state, but #354 (Jul 24) landed the actual frontend wiring
four days later, making those fixes stale again. Three docs still claimed
logical_t/logical_tdag/logical_ccz "do not currently compile through quonc
(tracked in #311)" when #311 is closed-completed and they compile
end-to-end.
with real surface_d3_t.qn / surface_d3_ccz.qn benchmarks; register them in
catalog.yaml (ci: smoke); describe the magic-state resource-report fields.
source" limitation; note the source-prelude binding (QEC: wire logical_t/logical_tdag/logical_ccz into frontend typechecker (source syntax for #283) #311/wire logical T/Tdag/CCZ into frontend (#311) #354).
ops compile end-to-end while keeping the honest scope (no distillation
factory, metadata-only, not a threshold claim).
Verified: both benchmarks compile through quonc with t_count/ccz_count/
magic_state_demand populated; samples_catalog smoke-typecheck passes;
assert-validation-docs passes.