Layer 8 · Replication Challenge

Reproduce the wwPDB July 15, 2026 Result

You are not asked to trust this result. You are asked to reproduce it, find an error, or trigger the declared falsifier.

The challenge is open and standing.

Here are the files. Here is the scorer. Here is the command. Here is the expected output.

Reproduce it independently, identify a computational error, or trigger one of the four declared falsifiers. If you trigger a falsifier, the verdict changes. That is the protocol.

What was sealed before the terrain opened

Prediction DOI: 10.5281/zenodo.21304301
Sealed: 2026-07-11 (4 days before wwPDB released coordinates)
Terrain opened: 2026-07-15 00:00 UTC
CSV with per-row SHA256 hashes: MH_PRED_V1_02_wwPDB.csv

Verify the SHA256 hashes against the Zenodo-archived CSV to confirm no row was altered after sealing.

The four declared falsifiers

PathwayFalsifier (verbatim, sealed)
PDB-1"No positive core shift or a stable reversed shift."
PDB-2"A closed eligible cage requires an unrelated axis family."
PDB-3"No association between D𝑖 and structural resolution, or a reversed association."
PDB-4"No synonymous-codon stratification or a stable reversed direction."

If your independent run triggers any of these conditions, the verdict for that pathway changes. Submit a documented report to the address below.

The scorer

PDB-4 Full Dataset Scorer

File: PDB4_FullDataset_Analysis.py
Language: Python 3.10+
Dependencies: Standard library only (os, sys, json, math, time, collections, itertools, statistics, urllib). No external packages required for core scorer. gemmi optional for faster CIF parsing.
Source: Layer 4 - Executable Scorer

Run command

python PDB4_FullDataset_Analysis.py

The script queries RCSB live for the July 15, 2026 release, downloads CIF files and CDS sequences, and computes global Kendall tau. Output is written to ../wwPDB_July15_analysis/PDB4_FullDataset_Report.txt.

Permutation control note

The built-in permutation control shuffles B-factors within amino-acid class across all pooled entries (seed 42). It is amino-acid-preserving but not structure-preserving. It does not establish a cluster-robust p-value. A within-entry block permutation can be implemented by modifying lines 517-535 to shuffle within each entry's triple subset.

Expected output - key quantities

MetricExpected valuePathway
PDB-1: core > surface (9ZYS)+0.090 (all 4 thresholds)PDB-1
PDB-1: core > surface (10ZK)+0.022 (all 4 thresholds)PDB-1
PDB-1: direction reversals0 of 12PDB-1
PDB-2: C₂ axes found (9ZYS)49 axes, 6 clusters, best RMSD 7.69 ÅPDB-2
PDB-2: C₃ axes found (9ZYS)16 axes, 1 cluster, best RMSD 8.44 ÅPDB-2
PDB-2: C₅ axes found (9ZYS)3 axes, 1 cluster, best RMSD 9.95 ÅPDB-2
PDB-3: Pearson r(D𝑖, B-factor)+0.0445PDB-3
PDB-3: permutation null r-0.1674PDB-3
PDB-4: Concordant C544,325PDB-4
PDB-4: Discordant D507,577PDB-4
PDB-4: Global Kendall tau+0.034935PDB-4
PDB-4: Permutation control tau+0.025924PDB-4
PDB-4: Total pairs evaluated1,051,902PDB-4

How to trigger a falsifier

PDB-1: Find a July 15, 2026 entry where resolved core Q▵ does not exceed surface Q▵, or where the direction reverses across all tested thresholds.

PDB-2: Find an eligible closed cage from the July 15, 2026 release where axis recovery requires a non-icosahedral family.

PDB-3: Show that D𝑖 has no positive association with B-factor, or that the association is negative.

PDB-4: Show that either (a) no synonymous-codon stratification exists in the pooled dataset, or (b) the global direction consistently reverses (D > C across the full dataset).

If you trigger a falsifier, the verdict changes. Document your methodology and contact us below.

Report a result

To report a successful replication, a identified computational error, or a triggered falsifier:

Institute contact: contact@umtts.org
Ledger record: Full terrain audit
Falsifier adjudication sheet: Layer 6

TRUTH > COMFORT. Always. The record is only as strong as its willingness to be checked.