RELATIONAL ENCODING → DECODING

RICT Encode–Decode Production Test

Graph → QPC circuit → IBM Heron r2 (ibm_fez) → measure → reconstruct graph. At 12 nodes the graph comes back exactly: every edge, no false edges. Accuracy then tracks the routing burden: 88.5% at 16 nodes, 85.7% at 20, against a chance baseline near 25%.

What This Test Is

The RICT encode–decode test checks whether QPC can encode a relational network (graph) into a quantum circuit, run it on real hardware, and decode the graph from the measurement outcomes. Success here means the full loop works: structure in → structure out.

Goal

Take a random graph A, encode it into phases and entanglement, run the circuit on IBM Heron r2 (ibm_fez), collect shots, then reconstruct an estimated graph A′ from the measured correlations. Compare A′ to A on edge precision, recall and F1, always against an explicit chance baseline.

Why It Matters

The metric is recoverability of the relational structure: the specific graph that went in can be read back out, and told apart from a graph that stayed out. A maximally random output has maximum entropy. Decode F1 against a chance baseline, plus the decoy control, is how this page scores that recovery.

How We Know It Is Real

Three safeguards, all applied here. Every number is quoted against the score random guessing would achieve at the same number of predicted edges. The reconstruction threshold is derived from the measured data alone and never consults the true graph, so nothing is tuned on the answer. And a decoy control runs the identical circuit on a different graph B and scores it against A: a genuine decoder must recover B and fall to chance on A. That is what happens, which rules out the result being an artifact of gate placement or of the hardware's noise.

What is encoding/decoding good for in the real world?

Customers often ask: what does “encode a graph and decode it” have to do with practical tasks? In short: we put a structure (who is connected to whom) into the quantum run, and we read that structure back from the measurement. That same idea applies wherever you need to recover relationships or structure from limited or noisy data.

1. Holography-style reconstruction

In holography, a 3D scene is encoded into an interference pattern (a “flat” recording). When you shine light through it, you recover the full 3D structure. Here we do something similar: the graph (the “scene” of relationships) is encoded into the quantum state; the measurement gives us a kind of interference pattern. Decoding is recovering the relationship structure from that pattern. So the test shows that QPC can, in principle, support tasks where you store rich structural information in a distributed way and reconstruct it later: useful for imaging, compressed sensing, or any setting where the full structure is encoded in a mixed or lower-dimensional signal.

2. Recovering who is connected to whom

Many real problems are about relationships rather than single items: who influences whom, which suppliers feed which factories, which nodes in a network depend on each other. You often don’t see the links directly. You see aggregate or noisy data. Encoding/decoding here means: we put a network of links into the quantum process, run it, and then try to recover that network from the outcomes. The test proves that recovery is possible on real hardware, exactly at small scale and well above chance at larger scale. So it’s relevant for supply chains, social or contact networks, infrastructure dependencies, or any domain where “who is connected to whom” must be inferred from indirect or noisy measurements.

3. Finding hidden structure from correlations

Sometimes you have many signals (sensors, agents, variables) and you want to know which ones are really linked, beyond chance correlation. The quantum run encodes relationship structure; the measurement outcomes give us correlations. Decoding is turning those correlations back into an estimated structure (who is linked to whom). So the test is a proof of concept for tasks where you have to infer structure from correlation data (sensor networks, fault propagation, financial or biological networks) when that structure was encoded inside a quantum or high-dimensional process.

Bottom line: Encoding = putting a relationship graph into the computation. Decoding = reading that graph back from the results. The test shows this works on real quantum hardware. The same idea applies to any real-world task where you need to store or recover who is connected to whom from limited or noisy data.

How It Is Done

Production configuration: random graph at density 0.25, 3 ensemble runs on Fez, 12,288 shots per arm, plus a decoy control arm.

1Graph A
→
2QPC circuit (edges)
→
3ibm_fez (3 runs)
→
4Counts → correlations
→
5Split → A′
Steps

Results below are raw counts. Readout mitigation was computed alongside and left the reconstruction unchanged, since it rescales correlations without reordering them. Operator scripts and CLI flags sit in the NDA reproduction package.

Results

Production runs on IBM Heron r2 (ibm_fez), raw counts, with a decoy control and an explicit chance baseline at every size.

100%
Edge F1 at 12 nodes
12 / 12
Edges found, zero false
88.5 / 85.7%
Edge F1 at 16 / 20 nodes
at chance
Decoy control, all sizes
Metric 12 nodes 16 nodes 20 nodes
Edge F1100.00%88.52%85.71%
Chance baseline F118.18%25.36%27.63%
Edge precision100.00%84.38%84.91%
Edge recall100.00%93.10%86.54%
True edges recovered12 of 1227 of 2945 of 52
Expected by chance2.2 ± 1.27.7 ± 2.114.5 ± 2.8
Significancez = +8.06z = +9.25z = +11.04
p-value< 0.0001 at every size
Couplings → 2-qubit ops after routing12 → 33 (2.8×)29 → 125 (4.3×)52 → 256 (4.9×)
Circuit depth on device42115196
Shots12,2888,19212,288
IBM job IDsd9jpeajjf64c739h6pmg
d9jpeebhdfks73cilt7g
d9jpjugii2cc73ef7et0
d9jpkbibr2fc73e6bvd0
d9jpmd3hdfks73cimang
d9joqfqbr2fc73e6aq50
d9joqlrhdfks73cil370
d9joqr3hdfks73cil3eg
Reading these numbers: at 12 nodes the reconstruction is exact. All 12 edges found, no spurious edge, every one of the 66 possible pairs classified correctly, where random guessing would find about 2 edges. At 20 nodes, 45 of 52 edges are recovered at 85% precision against a chance expectation of 14.5. F1 is always read against its baseline: on a graph of this density, blanket-predicting that every pair is connected scores an F1 in the forties. The chance row sits directly beneath every measurement.
The decoy control: the encoded graph is the recovered graph

The same circuit was run encoding an independent decoy graph B, then scored against the target A. It carries the same gate count, the same routing burden and the same noise environment. Any effect that leaked structure through gate placement rather than through the encoding would track B, not A.

ArmGraph encodedScored againstEdge F1Verdict
Main, 12 nodesA (target)A100.00%z = +8.06 · above chance
Decoy control, 12 nodesB (decoy)A30.30%z = +0.80 · at chance
Decoy, self-scoredB (decoy)B86.49%z = +6.68 · above chance
Main, 16 nodesA (target)A88.52%z = +9.25 · above chance
Decoy control, 16 nodesB (decoy)A29.85%z = +0.37 · at chance
Decoy, self-scoredB (decoy)B82.86%z = +8.34 · above chance
Main, 20 nodesA (target)A85.71%z = +11.04 · above chance
Decoy control, 20 nodesB (decoy)A32.38%z = +0.90 · at chance
Decoy, self-scoredB (decoy)B85.11%z = +11.20 · above chance

At every size the decoder recovers whichever graph was actually encoded and drops to chance against a graph that was not. The recovered structure is therefore the encoded structure.

Reproducibility

Validated offline before any hardware time was spent. Across independently generated graphs in noiseless simulation the method reconstructs the graph exactly, and it continues to do so down to a quarter of the shot budget. The hardware result sits on a method that already reconstructs exactly in simulation.

The reconstruction threshold is derived from the measured correlations alone. That data-only split scores within a point of a hindsight-tuned split, so the published F1 is the measurement’s own cut.

Accuracy tracks the routing multiplier

On this device, Edge F1 follows how many two-qubit operations each coupling costs after routing.

Simulation is exact. Hardware F1 follows routing.

In noiseless simulation this method reconstructs a 20-node graph exactly. On IBM Heron r2 the three sizes line up with the routing multiplier: accuracy falls as that multiplier rises, and nothing else in the setup changes.

NodesCouplings → 2Q opsMultiplierEdge F1
1212 → 332.8×100.00%
1629 → 1254.3×88.52%
2052 → 2564.9×85.71%

Pairs that sit on native lattice edges compile cheaply. Pairs that must be transported pick up extra two-qubit operations. The multiplier, rather than the raw coupling count, governs the published F1: at 12 nodes the encoding uses 33 operations for 12 couplings, and the graph comes back perfectly.

Which error channel the ladder identifies

A calibrated stochastic model (depolarising plus readout error) tracks the hardware for the configuration we run, predicting 88.7% against 85.71% measured. Weaken the encoded signal and the same model predicts 99.0%, while the hardware delivers 84.48%. That mismatch identifies a channel that specifically punishes a weak signal.

That channel is coherent error: small systematic rotations which add structured correlation rather than washing correlation out. Its footprint on this device was measured independently and is strong enough to matter. Configurations that look better in simulation because they use a subtler signal lose first under coherent error. Two such candidates were promoted by simulation; both lost on hardware.

What the 12-node exact run already returns

The measured requirement is native-adjacent couplings. On this same device, at 12 nodes, with a 2.8× multiplier, the method returns the exact graph. Direct connectivity at 20 nodes would remove the 4.9× routing tax. The decoder, shot budget, and qubit count already deliver exact reconstruction when that tax is small.

What This Means for the Whole Test Suite

How the RICT encode–decode test fits with PQST-64, Crash Detection, and PRCBS.

Three main tests

PQST-64 shows high-entropy polycontextural sampling output (64Q, high uniqueness). QPC Crash Detection shows cascade detection on 128Q Torino. PRCBS (RICT, CPRP, PCRT) shows maximum diversity and entropy at 128Q–156Q on Torino and Fez. All three run on real hardware.

Role of RICT Encode–Decode

This test answers: can we get the structure back? It reconstructs a 12-node graph exactly, a 16-node graph at 88.52% and a 20-node graph at 85.71% against chance baselines of 18–28%, with a decoy control at every size confirming that the graph recovered is the graph encoded. QPC relational encoding is decodable on current hardware.

How uniqueness is read

High output diversity (many unique outcomes, high entropy) describes the shot histogram. Recoverable content is scored by decode F1 against a chance baseline, with a decoy control. Uniqueness counts sit beside that decode, as a description of the output.

Summary

The RICT encode–decode test runs on the same stack as the rest of the suite, uses the same relational encoding, and reads the structure back: exactly at 12 nodes, where couplings need little routing, and well above chance at 16 and 20 nodes, identified as the graph that was put in.

Sizes run12, 16 and 20 nodes
Encodingedges
Shotsup to 3 × 4096 per arm
Best resultexact reconstruction
Controldecoy graph, at chance
Outputevidence bundle (NDA)