Seventeen conflicting ADMET logics. One quantum architecture. A same-day pass on IBM Heron r2.

Quantum Polycontextural Computing (QPC) kept multi-logic drug-property decisioning co-resident in one 156-qubit job, and cleared a pre-registered architecture scorecard on ibm_marrakesh under the locked geometry.

Dr. Ilan Kreitmann · quantumpolycontextural.ai · Polycontextural architecture evidence with public IBM job IDs

We congratulate IBM on its success in establishing a certified path to quantum advantage for hard sampling. QPC has gone its own way on the same Heron r2 hardware: keep seventeen conflicting ADMET logics co-resident in one coherent job, and close a falsifiable architecture scorecard that classical computers can audit. Same-day pass on ibm_marrakesh, with public job IDs.

What we set out to prove

Classical practice flattens or sequences conflicting logics: a weighted score here, a hard filter there. On our frozen public-proxy ADMET table, those methods already disagree. Acetaminophen ranks high under a weighted sum and drops at a sequential DILI gate.

QPC puts those logics together inside one coherent quantum job, with a measurable joint-structure gap versus controls that isolate contexts, including separate runs that merge later.

The Stage A → C ladder

• Stage A. Classical conflict: same frozen 9 × 17 table; weighted-sum vs sequential filters disagree.
• Stage B. Architecture on ibm_fez: locked junction_ryy geometry; raw junction gap ≈ 0.18 vs no_cross.
• Stage C. Problem-class closure: add the separable contrast; require retention vs Aer reference; clear all bars the same day.

Marrakesh Stage C2 scorecard (same day)

Backend: IBM Heron r2 · ibm_marrakesh · 156 qubits · shots 8192 · primary metric on raw counts. Resilience / SAR is a labelled diagnostic channel on the same jobs.

Coupled jobs: d9qubi7pemts73crsa2g, d9qubihdsedc73aftfj0, d9qubivpemts73crsa3g
Separable job: d9qubk8pdb6s73e45q3g

What this is

A public, falsifiable polycontextural architecture demonstration: seventeen ADMET logics co-resident in one coherent 156-qubit job; predeclared coupled / no_cross / separable controls; primary metrics on raw counts; IBM job IDs; and a Stage A→C scorecard that clears the same day on Marrakesh.

Classical computers can audit the controls and conflict table. The coupled QPC job keeps the joint structure that flatten / filter / merge leave on the table, under the locked geometry.

Why Marrakesh mattered

The same locked geometry had already cleared a strong gap on IBM Heron r2 · ibm_fez (Stage B, raw gap ≈ 0.18). Stage C2 then ran on ibm_marrakesh under that same geometry lock and produced a clean same-day full pass. That is how the WOW closed.