Mirror Architecture converted measured bridge fields into normalized feature vectors that could be encoded and compared outside the original model.
Complete program arc
From measured feature states to a bounded recovery result.
Selection for the Quantinuum Singapore Grand Challenge cohort focused the program on Simon hidden-invariant recovery and AI-for-Quantum work.
Local blinded controls, randomized checks, counts-only GF(2) recovery, and a frozen-policy H2-2E emulator transport receipt define the current support.
Run one separately approved backend gate at a time, compare fixed and adaptive shot policies, and keep every result tied to its actual carrier.
Plain-language method
The quantum computer is the test environment. The measured relation is the object.
The workflow hides the target relation from the controller, collects only the allowed observables, attempts recovery, rejects malformed or leaking controls, and records the complete runtime and result chain. That makes the test auditable instead of decorative.
Current evidence
What the program supports today.
Simon hidden-invariant recovery
The program defines a hidden relation, exposes bounded observations, and tests whether the relation can be recovered without giving the answer to the controller.
Blind and randomized checks
Local validation uses frozen inputs, randomized larger cases, malformed controls, and leakage checks before a transport result can be accepted.
Aqora / Nexus H2-2E emulator
A frozen policy completed a bounded private blinded run through the Quantinuum H2-2E emulator route exposed through Aqora/Nexus.
Receipt before claim
Runtime, package, policy, and result hashes keep the recovery result attached to the exact software, carrier, and control set that produced it.
Evidence boundary
Current support: controlled recovery and bounded emulator transport.
The public record supports Quantinuum SG Grand Challenge 2026 cohort participation, blinded recovery work, counts-only GF(2) recovery, and bounded H2-2E emulator transport. It does not establish physical-QPU execution, quantum advantage, a contest result, a production deployment, or a general Quantinuum partnership.
Preserve the frozen policy and controls, execute one approved backend comparison, and publish only the support level carried by that backend's receipt.