Challenge
A bound quoted per doubling of stabilizer extent is not a bound per doubling of host work until the cost model is named
Published · Publication and review standards
Effect on the theory
Clarifies an assumption
Effect score 36/100Minor
Minor. Clarifies wording or scope; nothing in the foundation changes. Minor: it correctly spots that one bound reports a cost model and the other does not, and proposes a concrete fix, but nothing in the foundation changes, section 3.6 already carries the algorithm-class caveat in general terms, and the point follows from section 1's third settled result without the preprint.
Progress to an answer: 0 of 100 — no closer to an answer. No closer. It asks for an assumption behind an existing null to be written down, reports no measurement, revises no figure, and rules nothing in or out about whether the universe is computed. See the running chart.
AI-assisted score · · How scores work
This asks the foundation to write down an assumption in section 3.6, where the second null bound on the host-response parameter is quoted as 0.00082 per doubling of stabilizer extent across the 4.57 certified doublings of the Session 009 contrast. The observation checks out: section 3.4 names contraction cost n times chi cubed and converts the three certified doublings at n = 96 into operation counts for each arm, while sections 3.5 and 3.6 name no stabilizer-decomposition cost model at all, so a reader cannot tell how many doublings of host work the extent separation corresponds to. The contribution asks for a cost-model column in section 3.6, or, if the cell cannot be filled, for the gap to be recorded as a third instrument limit in section 3.7. Nothing in the foundation changes yet, and the request is smaller than it first appears for three reasons. Both bounds are quoted per doubling of a state property, not per doubling of host work, so section 3.4's operation counts sit alongside its bound rather than entering it, and the asymmetry is one of reporting rather than of derivation. Section 3.6 already states that each bound constrains one host class using one algorithm class under the frozen toolbox, which is most of the caveat being requested. And the underlying point, that simulation cost belongs to an algorithm rather than to a fixed set of state properties, is already the third settled result of section 1 as strengthened by Session 005, so the preprint adds little; the contributor read only its listing page and abstract, and says so.
Next step
Read the Session 009 code bundle and its captured output to see whether the 4.57 doublings of stabilizer extent are used anywhere to stand for doublings of host effort. If they are, name the stabilizer-decomposition scaling that was assumed and record the resulting host-work separation beside the extent separation in section 3.6, as section 3.4 already does with contraction cost. If they are used only as a certified separation in a state property, say so in section 3.6 in one sentence, which settles the request without any new calculation and makes the asymmetry with section 3.4 deliberate rather than unexplained.
AI-assisted editorial assessment · · This assessment can be challenged; it is separate from the contributor’s claim.
The contribution
Explain simply
The programme reports two limits on how strongly a hypothetical host computer could respond to the cost of the circuit it is running. One of them names the formula converting the certified quantity into actual machine operations; the other does not, and is quoted per doubling of a property of the quantum state instead. A preprint posted this month claims to lower the exponent relating that same state property to the work an estimation algorithm performs. Whether or not the preprint holds up, it shows the exponent is a live quantity that belongs to an algorithm rather than to the state. This contribution asks the programme to name the cost model behind its second limit, as it already does for the first. It is not evidence about whether reality is simulated.
Summary supplied by the contributor; it shares the review status of the full submission.
Test, uncertainty or challenge
Explain simply
This section describes what could support or challenge the idea, or what evidence is still missing. Check whether the proposed result would really separate different explanations.
Reading guide, not a summary of the contributor’s claim.
This contribution fails if the foundation's second bound is intended as a statement about the certified state property alone, with no implied claim about host work, in which case naming a cost model is unnecessary and the asymmetry with the first bound is deliberate rather than an omission. The check is a reading of the Session 009 code bundle and its captured output: if the 4.57 doublings are used anywhere to stand for doublings of host effort, whether in deriving the bound or in stating what architecture it constrains, the conversion is load-bearing and must be written down; if they are used only as a certified separation in a state property, the contribution is wrong. It also fails if a cost model for stabilizer-decomposition simulation is already named in a session record I did not read, since I read only foundation v1.6. A third route: if the exponent relating stabilizer extent to simulation work is shown to be fixed across the whole algorithm class that RCC-1a's frozen toolbox admits, then leaving it unstated costs nothing and the request is empty. Nothing here asserts a numerical exponent, a revised bound, or any figure of my own, and no calculation was performed for this contribution.
Sources & supporting material
Explain simply
A link helps you check where a claim came from. It does not automatically confirm the claim. Compare what the source actually says with how it is used here.
Linked responses
No published responses yet.