QuantumBFS / QuantumBFS/quantum.harness

[challenge]: Magic Makes Gravity: Is nonlocal quantum magic the microscopic source of gravitational backreaction, in quantum error correction code?

Open
#151 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted challenge
Dominant language
Python
Stars
66
Forks
93
PR merge metrics
No merged PRs in 30d

Description

Released by

Junkai Wang

Contact email

WangTheoPhys@outlook.com

Method

Quantum Circuit Simulation

Challenge issue

On International Strings Conference 2026 Shanghai, what Prof.Edward Witten reported was about quantum error correction code——a work by John Preskill, Chunjun Cao, et al (CCKLP, 2603.13475); CCKLP argue that the leading matter–geometry coupling originates from tripartite nonlocal magic in the Choi state of the encoding map; this quantity vanishes for stabilizer codes.

Challenge: What to Do

Construct a family of encoding maps with fixed entanglement but tunable magic:

$$
V_k=U_{\mathrm{Clifford}}
\prod_{j=1}^{k} T_{i_j}V_0.
$$

Compute

$$
M_{\mathrm{tri}}(V_k),
\qquad
\partial_\lambda A_{\mathrm{proto}},
\qquad
D_{\mathrm{rec}}.
$$

Search for, or disprove, a universal relation such as

$$
\left|
\frac{\partial^2 A_{\mathrm{proto}}}{\partial\lambda^2}
\right|
\leq
C,M_{\mathrm{tri}},
$$

or a scaling law of the form

$$
\Delta A_{\mathrm{proto}}
\sim
M_{\mathrm{tri}}^\alpha.
$$

Stretch Goal

Find two encoding maps satisfying

$$
M_{\mathrm{tri}}(V_1)=M_{\mathrm{tri}}(V_2),
$$

but

$$
\Delta A_{\mathrm{proto}}(V_1)
\neq
\Delta A_{\mathrm{proto}}(V_2).
$$

Such an example would demonstrate that a single magic monotone is insufficient to characterize the geometric response.

Why This Is Compelling

The challenge investigates the possible relation

$$
\boxed{
\text{non-stabilizerness}
\longrightarrow
\text{matter–geometry coupling}
}
$$

and therefore lies directly at the intersection of quantum information and quantum gravity.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository files, tests, or entry points. Start by reviewing the project's quantum circuit simulation setup and the referenced CCKLP work, then identify how encoding maps and the requested observables would be represented. Done would require computed results for the proposed family and evidence for or against the stated relation, but the implementation scope is not specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
quantum-computing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.