MQC Simulator · Build dossier

What the code says

• 1,024 grid points of a complex wavefunction, time step 0.004

  Source src/constants.ts

• A split-step FFT with Yoshida 4th-order composition and a Kerr self-interaction term

  Source src/core/physics.worker.ts

• Geometry: a (5,2) torus knot with a 50,000-sample arc-length table

  Source src/constants.ts

• Observables: Shannon entropy, Fisher information, IPR, skewness, kurtosis, coherence length

  Source src/core/physics.worker.ts

• There are no qubits or quantum circuits in the code: it is a continuous classical field

  Source src/

• Rendering requires WebGL with RGBA32F float textures

  Source src/core/QuantumDataBridge.ts

Module state

1. implemented

   The solver in a Web Worker

   An in-house radix-2 FFT, precomputed kinetic propagators and noise with fluctuation-dissipation scaling.

   Source src/core/physics.worker.ts

2. implemented

   Curvature and torsion as potential sources

   A da Costa-style V = −κ²/(8m) and an accumulated ∫τ ds phase.

   Source src/core/physics.worker.ts

3. illustrative

   The "Omega Protocol" is a scripted visualisation

   π·Φ phase rotations across L/137 gates, infoDensity growth toward MAX_VALUE and a logarithmic decay of "local c" are an overlay on the model state.

   Source src/core/physics.worker.ts

4. partial

   The parameter control surface

   The worker accepts updates for γ, KERR, T_KPZ and gauge amplitude, plus a state switch, but no interface element sends them.

   Source src/types.ts

5. not implemented

   Calls to the declared AI dependency

   @google/genai is declared in package.json but never imported under src/: the app runs without any key.

   Source package.json, src/

6. on roadmap

   Numerical validation and measured performance

   The README itself lists what is missing: reference cases, time-step and resolution checks, and measurements on named hardware.

   Source README.md

How this was checked

• The "coherence" status is a comparison against a constant

  hypothesis_valid is IPR > 0.08, and the same threshold feeds the Proof panel.

• The terminal "telemetry" lines are randomly generated

  Streaming lines are assembled from Math.random() on a 1200 ms interval.

  Source src/hooks/useQuantumSimulation.ts

• The "zero-copy" claim does not match the data path

  Data crosses the worker boundary via postMessage with a per-tick Float32Array copy.

• The physics module disables type checking

  The first line of physics.worker.ts is // @ts-nocheck.

Limits of these claims

• There is no numerical validation: no reference cases, no convergence study, and per-step renormalisation can mask solver error.
• The constants KERR = 45, T_KPZ = 4.2 and γ = 0.015 are phenomenological choices with no calibration source in the repository.
• Labels such as "CERN/IBM", "Bekenstein limit breached" and "event horizon" are interface styling, not computed output; the project has no institutional affiliation.
• RGBA32F support and mobile behaviour were never verified; the local build is not tied to a commit because dist is git-ignored.
• The torius/ subfolder is a parallel legacy vanilla-JS variant, excluded from the build and not presented as part of the product.
• The page title says "v3.0" while the package version is 0.0.0, which says nothing about maturity.

Live build

Live buildmqc.moonsugar.space ↗

Revision

0fd8b0b

Build directory

dist

The live build is published to explain the project, not as a verified quantum device: it is a computational model of a continuous field — no qubits and no quantum circuits in the code, and the “coherence” indicator is an IPR > 0.08 threshold. Its bundled interface labels the model “CERN/IBM T5,2” with a “THEORY VALIDATION” status; the code supports neither.

The page itself does not confirm availability: the host is checked when the build is published.