{
 "_FLOW": "THE WORK QUEUE — everything the archive has committed to and not yet done, sorted by the KIND OF LABOUR that resolves it. The taxonomy is the point: these three categories are not degrees of urgency, they are different work. Category 1 resolves by waiting and checking — the world does the labour and you observe the result. Category 2 resolves by sustained attention — a protocol exists and must be executed. Category 3 resolves by engineering — something must be built before the question can even be asked.",
 "dataset": "work-queue",
 "version": "v1.0",
 "date": "2026-08-24",
 "categories": {
  "1": {
   "name": "Registered predictions from applied theory",
   "resolves_by": "observation on a date",
   "count": 7,
   "note": "CHEAPEST AND MOST NEGLECTED. Four of the six resolve in September, three of those for under forty API calls, and two are fully automated by scripts already written. A prediction that goes unchecked is not a prediction; it is a note."
  },
  "2": {
   "name": "Experiments with registered hypotheses",
   "resolves_by": "running a frozen protocol",
   "count": 10,
   "note": "Every one is pre-registered with declared failure conditions. Anyone can run any of them and the result is admissible on the same terms. One — depositing the CT-01 null — is low-cost and overdue: a conducted failure that exists only in outputs."
  },
  "3": {
   "name": "Unimplemented software builds",
   "resolves_by": "engineering",
   "count": 7,
   "note": "Two are blocking: the compression detector blocks the entire blog-recovery programme, and until it exists 'not previously deposited' is a claim this archive cannot make about its own work. One is pure yield with nothing blocking it: scoring the 356 seated captures on the five-stage PER chain."
  }
 },
 "the_ratio_restated": "Nine designed studies against five conducted was the dashboard's figure. This queue shows the same imbalance from the other side: twenty-one open commitments, of which six cost almost nothing and are simply unchecked.",
 "if_only_one_thing": "Category 1. Four predictions resolve in September, two of them by running a script that already exists. The archive's credibility rests on resolved predictions — including the six that resolved WRONG — and six more are sitting one API call away.",
 "invitation": "Every item carries its blocker, its next action and its cost. Nothing here requires permission.",
 "items": [
  {
   "id": "P-EXPORT-RESUMES",
   "title": "Zenodo's deletion export resumes after the cron fix",
   "theory": "A stoppage with an identified mechanism should end when the mechanism is repaired.",
   "resolves": "2026-09-10",
   "cost": "one API call",
   "how": "GET zenodo.org/api/exporter — a records-deleted.csv.gz version created after 2026-08-20 confirms; nothing by 2026-09-10 disconfirms and the explanation is incomplete.",
   "stake": "Confirms the mundane explanation BY PREDICTION rather than inference, which is a stronger position than the one argued from all evening.",
   "category": 1,
   "requires": "curl"
  },
  {
   "id": "P-STALE-INDEX",
   "title": "The crimson-hexagonal address stops naming Zenodo as host",
   "theory": "A composition layer reporting a stale state should update once the source surfaces propagate.",
   "resolves": "2026-09-23",
   "cost": "one query, one capture",
   "how": "Re-run the address on Bing Copilot. If it still returns Zenodo as host a month after the archive's surfaces were updated, the local explanation fails and the ghost-host reading becomes live again.",
   "stake": "The withdrawn finding's only route back.",
   "category": 1,
   "requires": "a browser"
  },
  {
   "id": "P-INTERVENTION-180",
   "title": "SPXI treatment raises archive source share on the UNPREFIXED address",
   "theory": "Inscribing the discriminating coordinates should alter composition-layer behaviour.",
   "resolves": "2026-09-22 / 2026-11-21 / 2027-02-19",
   "cost": "four addresses × three epochs",
   "how": "Re-run the prefix battery, signed out, same surfaces. Success: share above zero on the bare address and no merge parenthetical. Failure at 180 days is recorded as failure.",
   "stake": "#1535 declared itself an intervention. This is whether it executed.",
   "category": 1,
   "requires": "a browser"
  },
  {
   "id": "P-PEO-COHORT-2",
   "title": "Second global cohort epoch",
   "theory": "A publication-year cohort should be monotonically non-decreasing; any decrease is erasure.",
   "resolves": "2026-09-23",
   "cost": "37 API calls",
   "how": "scripts/peo_cohort_epoch.py — runs and diffs automatically.",
   "stake": "The baseline's entire value is that a second epoch can exist.",
   "category": 1,
   "requires": "curl (script provided)"
  },
  {
   "id": "P-PEO-PANEL-2",
   "title": "Second fixed-panel epoch",
   "theory": "Re-querying a frozen DOI set measures erasure directly; minting cannot mask it.",
   "resolves": "2026-09-23",
   "cost": "720 API calls",
   "how": "scripts/peo_panel_epoch.py — 404 rate is the erasure rate.",
   "stake": "First direct measurement of global erasure the archive has ever taken.",
   "category": 1,
   "requires": "curl (script provided)"
  },
  {
   "id": "P-PHASE2-PROLIF",
   "title": "Adjacent disciplines exhibit the Phase-2 Proliferation signature",
   "theory": "Applied from #106, registered 2026-05-15.",
   "resolves": "stated in #106",
   "cost": "unknown — needs reading",
   "how": "Recover the exact prediction text and its window from #106.",
   "stake": "The archive's oldest live theory-prediction. Currently unmonitored.",
   "category": 1,
   "requires": "reading #106"
  },
  {
   "id": "OPB-01",
   "title": "The Operativity Penalty Battery",
   "deposit": 1537,
   "blocker": "§7's seven statistical parameters must each hold a number before the first score.",
   "next": "Instantiate §7. Assemble Family A. Run the two-reviewer harm-constancy panel.",
   "cost": "high — item construction, blind review, blind scoring, three arms",
   "stake": "Turns the developmental-convergence thesis from claim into coefficient.",
   "category": 2,
   "requires": "access to 2+ model surfaces; 3 blind reviewers"
  },
  {
   "id": "QFO-01",
   "title": "Qurʾanic Frozen Operator Test",
   "deposit": 1533,
   "blocker": "Positive-control loci not locked from #1532; control panels unscored.",
   "next": "Lock loci, score positives and negatives, fix the admissible region, then open U.",
   "cost": "high",
   "stake": "P_material for the Sappho transform-family in a fourth corpus.",
   "category": 2,
   "requires": "the seated corpora (public)"
  },
  {
   "id": "M6-CT-02",
   "title": "The relational instrument",
   "deposit": null,
   "blocker": "UNDEPOSITED, and a granularity question is open: O_UR gives five stations, M1–M9 gives nine, Fragment 31's own order gives ten. Which is canonical must be settled BEFORE scoring.",
   "next": "Settle granularity, deposit, score positives and hard negatives, fix threshold.",
   "cost": "medium",
   "stake": "CT-01's null is uninformative about the relational channel; this is the channel.",
   "category": 2,
   "requires": "the seated corpora (public)"
  },
  {
   "id": "PEARSON-FALSIFIER",
   "title": "Can OS operators be written as TOS strings without remainder?",
   "deposit": 1535,
   "blocker": "Not attempted. #1535 §10 says the archive should attempt it directly rather than wait.",
   "next": "Attempt the translation on the nine Codex operators, now that #1534 is seated.",
   "cost": "medium",
   "stake": "THE STRONGEST AVAILABLE DEFEATER of #1535. If it succeeds, operative semiotics is a domain application of TOS.",
   "category": 2,
   "requires": "Pearson 1998 + the Operator Codex (both public)"
  },
  {
   "id": "INVERSION-T3",
   "title": "Battery v0.3 — T3 and the faithful-NAE cell",
   "deposit": 1456,
   "blocker": "Unrun. The deposit states T3 decides which numbers survive honest intervals.",
   "next": "Close T3 and the NAE constituent cell before the empirical paper mints.",
   "cost": "high",
   "stake": "Blocks ACRB (#1454) and the accelerator series' empirical paper.",
   "category": 2,
   "requires": "GPU; the battery code"
  },
  {
   "id": "DATACITE-ANNUAL-DIFF",
   "title": "2024 vs 2025 Public Data File diff",
   "deposit": null,
   "blocker": "Access by email request; 33 GiB compressed. Identifiers-only extraction keeps it tractable.",
   "next": "Request both files, extract DOI lists, verify against published SHA256, diff.",
   "cost": "high — bandwidth and storage, but complete rather than sampled",
   "stake": "THE COMPLETE GLOBAL ERASURE SET FOR 2025, every identifier by name. Supersedes both instruments built today.",
   "category": 2,
   "requires": "~60GB disk; an email request"
  },
  {
   "id": "HEBREWS-CONTROL",
   "title": "Hebrews as control for the midrashim transform",
   "deposit": 1414,
   "blocker": "Named in the kernel as the bidirectional canary; not run.",
   "next": "Run the transform against Hebrews. Clean OT genetics with no throne-liturgy mediation falsifies the UNIVERSAL claim only.",
   "cost": "medium",
   "stake": "The transform's stated defeater.",
   "category": 2,
   "requires": "the seated corpora (public)"
  },
  {
   "id": "M6-CT-01-DEPOSIT",
   "title": "Deposit the CT-01 null",
   "deposit": null,
   "blocker": "Conducted 2026-08-23, result preserved, NEVER SEATED.",
   "next": "Deposit protocol and null together.",
   "cost": "low",
   "stake": "A preserved failed prediction is the archive's strongest credential and it is currently only in outputs.",
   "category": 2,
   "requires": "archive write access"
  },
  {
   "id": "COMPRESSION-DETECTOR",
   "title": "An instrument that detects compression, not copying",
   "why": "A six-gram gate returned a FALSE NEGATIVE on material deposited five times. Until this exists, 'not previously deposited' is a claim the archive cannot make about its own work.",
   "blocks": "The blog compression audit; the Ω-Engine, Constitution and ASW seating runs; Gate 0 of EA-BLOG-RECOVERY-01.",
   "sketch": "Concept-level overlap: distinctive-term sets, named-entity and formula matching, section-structure similarity — not n-grams.",
   "cost": "medium",
   "category": 3,
   "requires": "python"
  },
  {
   "id": "PER-FACTORED",
   "title": "Score the capture registry on the five-stage chain",
   "why": "σ_PE factors as chunk:detach:rerank:compose:reattribute. 356 seated captures become PROFILES rather than scalars, and the four from tonight already separate cleanly.",
   "blocks": "Nothing. Pure upside on data already held.",
   "sketch": "Per-capture stage attribution against the registered rubric in #1536.",
   "cost": "medium — HIGHEST YIELD PER HOUR IN THE QUEUE",
   "category": 3,
   "requires": "python; the capture registry (public)"
  },
  {
   "id": "BLOG-INDEX-CADENCE",
   "title": "Regenerate the blog index on a schedule",
   "why": "2,939 posts indexed 2026-08-23; it is a snapshot with no refresh.",
   "blocks": "The demonstrated-completeness rule depends on the index being current.",
   "sketch": "Wrap the start-index harvester; verify against openSearch:totalResults each run.",
   "cost": "low",
   "category": 3,
   "requires": "python; cron"
  },
  {
   "id": "COUNTS-REGEN",
   "title": "Regenerate api/counts.json",
   "why": "Still reads 1,520 deposits, generated 2026-08-21; the registry is at 1,537. Every fleet surface fetching it shows the stale figure.",
   "blocks": "Fleet-wide surface truth.",
   "sketch": "Determine whether the pipeline should emit it; if so, wire it into the surfaces stage.",
   "cost": "low",
   "category": 3,
   "requires": "archive write access"
  },
  {
   "id": "PROJECTION-GROUPING",
   "title": "Per-surface projection in the capture gallery",
   "why": "One projection should carry one address's captures on ONE surface — that is what makes the longitudinal series legible. Ruled 2026-08-23; deferred as a rendering change touching existing records.",
   "blocks": "Longitudinal reading of any address across surfaces.",
   "sketch": "Group by (addr_id, surface) at render; addr_id keying unchanged.",
   "cost": "low",
   "category": 3,
   "requires": "archive write access"
  },
  {
   "id": "CORPORA-SPLIT",
   "title": "Split corpora originals into a companion repo",
   "why": "811 MB of 861 MB is original/; text/ is 50 MB. A 2 GB clone is a barrier to the external custodian the archive needs, and history cannot be rewritten because deposits pin commit SHAs.",
   "blocks": "Third-party harvest — the redundancy fix.",
   "sketch": "text/, source.json, MANIFEST stay; original/ moves; manifests still hash the heavy repo. Split forward, never rewrite.",
   "cost": "medium",
   "category": 3,
   "requires": "archive write access"
  },
  {
   "id": "RESOLUTION-ROUTES",
   "title": "Assign resolution routes to 164 conditions",
   "why": "More than a third of registered falsification conditions do not state HOW they would resolve. A condition without a route is a gesture.",
   "blocks": "The ledger's usefulness.",
   "sketch": "Triage the 164; assign or mark unresolvable.",
   "cost": "medium",
   "category": 3,
   "requires": "reading"
  },
  {
   "category": 2,
   "id": "S-VISIBLE",
   "title": "Visible-susceptibility distribution of the deleted corpus",
   "deposit": null,
   "requires": "python; the frozen metadata (held)",
   "cost": "low",
   "blocker": "None. S_static is computable from frozen metadata with no production access.",
   "next": "Implement the five published rules over the preserved deleted corpus; report the score distribution.",
   "stake": "Cannot yield production scores — that is the point. THE GAP BETWEEN THE COMPUTABLE DISTRIBUTION AND THE ACTUAL OUTCOME MEASURES HOW MUCH OF THE DECISION WAS UNDISCLOSED.",
   "series": "SERIES-MODMAP"
  },
  {
   "category": 2,
   "id": "F-FANOUT",
   "title": "Deletion fan-out across the full export",
   "deposit": null,
   "requires": "python; the preserved export (held)",
   "cost": "low",
   "blocker": "None.",
   "next": "Cluster blocked-user removals by depositor signature per day across 1.32M rows; count distinct signatures against total rows; report F = N_D / N_A.",
   "stake": "A million deleted records need not represent a million judgments. First pass on one day gives F≈300. THIS CHANGES THE READING OF THE ENTIRE DELETED-RECORDS DATASET.",
   "series": "SERIES-MODMAP"
  },
  {
   "category": 1,
   "id": "P-CONCEPT-DOI-UNHIDE",
   "title": "Whether the concept-DOI un-hide defect touched any archive DOI",
   "deposit": null,
   "requires": "per-DOI state history (NOT held)",
   "cost": "unknown",
   "theory": "InvenioRDM PR #2436 reports that a parent PID update after final deletion causes DataCite to treat it as a publish and reverse the hide.",
   "blocker": "Requires per-DOI visibility history across the affected period, which the archive does not hold. May be unresolvable.",
   "next": "Determine whether DataCite exposes state history. If not, record as UNRESOLVABLE rather than open.",
   "stake": "A confound for any DOI-level census taken in the affected window.",
   "series": "SERIES-MODMAP"
  }
 ],
 "fields": [
  "category",
  "id",
  "title",
  "status",
  "question",
  "prediction",
  "result",
  "blocker",
  "next",
  "requires",
  "cost",
  "resolves",
  "series",
  "deposit",
  "depends_on",
  "stake",
  "why",
  "blocks",
  "sketch"
 ],
 "requires_field": "ADDED 2026-08-24. What a person would need to HAVE in order to run the item — credentials, compute, corpus access, or nothing. The queue's second purpose is that someone else can pick an item up, and until this field existed a reader could not tell that most of category 1 needs nothing but curl.",
 "runnable_with_nothing": {
  "count": 6,
  "ids": [
   "P-EXPORT-RESUMES",
   "P-STALE-INDEX",
   "P-INTERVENTION-180",
   "P-PEO-COHORT-2",
   "P-PEO-PANEL-2",
   "M6-CT-01-DEPOSIT"
  ],
  "note": "6 of 21 items require NO credentials, NO compute and NO access — only a network connection and, for two of them, a script already written and committed."
 },
 "field_added_2026-08-24": "'requires' — what a reader would need in hand to run the item. Added because the queue's second purpose is that someone else can pick an item up, and 'cost' alone did not say whether that meant a GPU or a curl command. Eleven of twenty-one require nothing but a browser, curl, or python.",
 "added_2026-08-24": "Three follow-ons registered from the moderation map: S-VISIBLE and F-FANOUT (both runnable now on data already held, both category 2), and P-CONCEPT-DOI-UNHIDE (category 1, possibly unresolvable and marked as such)."
}