Research Annex

Quantum Research Annex

Resource estimation, simulation-first reasoning, and evidence-preserving software intervention.

This annex is a research and interpretation layer. It does not claim quantum advantage, does not run production quantum workloads, does not imply affiliation with Google, and does not modify CodeWorld's core simulation-first repository governance thesis.

Overview

A separated interpretation layer

Six surfaces define the annex. Each is additive and advisory — none alter CodeWorld's repository-as-world core.

Research Annex

A clean, separated interpretation layer. The repository-as-world thesis remains primary; quantum tooling is studied, not embedded.

External Tool Map

Cirq, qsim, Qualtran, OpenFermion, and TensorFlow Quantum are external open-source references — not bundled application code.

Resource Consequence Ledger

Quantum-style resource accounting mapped onto software intervention governance: files, dependencies, tests, predictions, evidence.

Local Experiment Layer

A lightweight local lab produces JSON evidence. Heavy simulation stays off the production runtime entirely.

No Quantum Advantage Claimed

No advantage, no production quantum compute, no scientific claims. Discipline borrowed, claims withheld.

Evidence Export Only

The web app may display exported JSON evidence. It never executes quantum simulation.

Rationale

Why quantum, and why an annex

Disciplined resource accounting strengthens simulation-first software governance — without product or performance claims.

Why quantum appears in CodeWorld

Quantum resource estimation is one of the few disciplines that demands fully explicit accounting of cost before execution. CodeWorld borrows that posture for software interventions.

Why this is a research annex

It is intentionally separated from the core. The annex strengthens the thesis without converting CodeWorld into a quantum product or runtime.

Why no quantum advantage is claimed

No advantage, speedup, or production capability is asserted. The value is interpretive: a discipline of consequence accounting, not a performance claim.

Why external repos are references

External quantum repositories are studied locally and cited by URL. They are not vendored, imported, redistributed, or committed into CodeWorld source.

How resource thinking maps to engineering

Explicit resource estimation becomes intervention accounting: which files, dependency zones, and test surfaces a change consumes, with predicted versus actual outcomes.

Repository-as-world stays primary

The simulation-first repository governance architecture is unchanged. The annex is additive, advisory, and reversible.

External Tool Map

References, not bundled code

External open-source projects studied for their resource-estimation and simulation discipline. None are imported into the app.

Cirq

reference

Analog for explicit construction of an intervention plan from primitive operations before any execution — circuits as composable, inspectable change graphs.

Studied externally. Not imported into the web app. Optional local research dependency only.

https://github.com/quantumlib/Cirq

qsim

reference

Analog for scaling simulation-before-write reasoning when intervention consequence spaces grow large — predicting outcomes before committing.

Heavy simulation is local-only. Never executed inside the Vercel web runtime.

https://github.com/quantumlib/qsim

Qualtran

reference

Strongest conceptual fit. Maps directly to CodeWorld's structured intervention accounting — the Resource Consequence Ledger inherits its discipline of explicit, decomposable resource estimation.

Conceptual inspiration for software resource accounting. No quantum claims are made.

https://github.com/quantumlib/qualtran

OpenFermion

future

Future scientific branch only. Reserved for later research into domain-specific consequence modeling. Not part of Q1.

Future scientific branch. Not used in the web app or Q1 lab scaffold.

https://github.com/quantumlib/OpenFermion

TensorFlow Quantum

future

Future hybrid research branch only. Must not be added to the web app runtime.

Future hybrid branch. Explicitly excluded from the application runtime.

https://github.com/tensorflow/quantum

Resource Consequence Ledger

Intervention accounting for repositories

Inspired by explicit resource accounting, applied to software repositories as technical worlds — a natural extension of CodeWorld Observatory, not quantum marketing.

FieldMeaning
files affectedScope of the change surface.
dependency zones touchedCoupled regions that may propagate effects.
test surfaces predicted to failPre-execution failure hypotheses.
intervention hypothesisThe proposed change and its intent.
predicted outcomeExpected result before any write.
actual outcomeObserved result after evaluation.
evidence hash or timestampTamper-evident provenance.
uncertainty levelExplicit confidence bound.
human approval statePending, approved, or rejected.
rollback postureReversibility and recovery stance.
simulation statusWhether simulation preceded the write.

Local Experiment Layer

Exported evidence artifact

A lightweight local lab generates a Resource Consequence Ledger JSON artifact. The production app displays this exported evidence — it never runs heavy quantum simulation.

Generate the evidence artifact locally:

python quantum-lab/experiments/resource_consequence_placeholder.py

Output: quantum-lab/results/sample_result.json

Evidence ArtifactExported JSON Result

Resource Consequence Ledger — interpretation placeholder

run · qx-run-1782746311

Human Approval Statepending
Sourcequantum-lab/experiments/resource_consequence_placeholder.py
Simulation Statussimulated-before-write
Timestamp2026-06-29 15:18:31Z

Predicted Resources

Files6
Dep Zones2
Test Fails1

Observed Result

Files6
Dep Zones2
Test Fails0

Optional quantum tools detected: none

Uncertainty

high — placeholder data, not a scientific measurement

Assumptions

  • Resource accounting discipline (Qualtran-inspired) maps onto software interventions.
  • No quantum hardware or simulator is required for this placeholder.

Limitations

  • No real quantum simulation performed.
  • No quantum advantage claimed.
  • Not affiliated with Google.
No Production Quantum Workload

Exported JSON evidence only — not live quantum compute. This artifact is produced by a local research script. No Python runs and no quantum library is invoked during web rendering.

How this evidence flows

  1. 1A local research script produces an exported JSON artifact.
  2. 2CodeWorld reads the exported artifact as evidence.
  3. 3The web app displays the evidence.
  4. 4Human review remains the authority layer.
  5. 5No live quantum simulation runs in the Vercel request path.

This page displays exported local research evidence only. It does not run Python, does not invoke quantum libraries, and does not perform live quantum simulation during web rendering.