AI-generated conjecture · below the evidence/publication boundary
← All conjectures · Logistics & operations
Grain-dole queueing
Status is derived only from the shepherd-authored triage/prediction data above -- community submissions and claims are a separate overlay and can never change it (see the participation panel below).
Claim (verbatim)
Grain-dole queueing. Rome's grain dole served on the order of 200,000 registered citizens each month, administered through the Porticus Minucia Frumentaria, a purpose-built hall whose distributions ran through 45 numbered bays — recipients were assigned a specific bay and day. That is, structurally, a multi-server queueing system of the kind Erlang's formulas analyse: given an arrival stream and a per-bay service rate, queueing theory dictates how many servers are needed before waiting times explode. The conjecture is that the Porticus Minucia's architecture implements a solution to exactly this problem: 45 bays multiplied by a plausible per-transaction service rate, spread over the attested distribution schedule, should match 200,000 monthly recipients with minimal waiting — sitting near the efficient region of the queueing trade-off rather than far inside or outside it. Roman administrators found by iteration what Erlang later proved.
Prediction clause (verbatim)
Run the arithmetic against the architecture: using the attested 45 bays, a defensible range of per-recipient service times from comparative evidence, and the documented distribution calendar, compute throughput and expected queue behaviour under a multi-server queueing model for 200,000 monthly recipients. Primary clause: for mid-range service times, implied capacity utilisation falls between 0.6 and 0.95 — sufficient to serve all recipients within the schedule with bounded waits — rather than implying gross over- or under-provision (utilisation below 0.4 or above 1). The verdict follows the primary clause.
Kill-dataset (verbatim)
the arithmetic against the architecture.
Nobody has run this test. The kill-data is named above. If you can run it — or you know the paper that already settles it — claim the kill or submit the prior scholarship. Kills and prior scholarship are credited here, by name, as they come in.
On Inferpedia
This conjecture has been linked to the following subject pages on Inferpedia — an encyclopedia of the missing, now in limited preview.
Provenance
Run: Imported conversation (verbatim harvest) · model: claude-fable-5
Origin: operator conversation with Claude Fable 5 at max effort, conducted 2026-07-03, relayed verbatim by the operator into the shepherd session on 2026-07-04. No ModelRun exists for the original generation (it happened outside the pipeline); this transcript file is the canonical capture. Transcript path: docs/generated/conjecture_harvest_fablemax_20260703.md. Model (operator-attested, not pipeline-recorded): claude-fable-5. Novelty disclaimer (verbatim, load-bearing -- rule 4): "Same caveat as before, doubled: at 100 items across all of archaeology and history, some of these will have cousins in the literature I can't check. What I can guarantee is the format — each links two things not normally linked, and each names the dataset or measurement that would kill it."
Novelty / leakage triage
no prior formulation located (search dated 2026-07-05)
The Porticus Minucia's archaeology/topography and the annona's tessera-token distribution logistics (~200,000 monthly recipients) are described historically, but no queueing-style capacity calculation (bay count x service rate vs recipient load) was located. No prior formulation located (search dated 2026-07-05) — a dossier blank-join item, and one of the cheapest conjectures in the harvest to resolve (the arithmetic needs no new data).
- 'The porticus bears all the grain: an update of the area of the Porticus Minuciae (Rome)' — The architectural evidence
- Cura annonae overview — Recipient counts + token system
Predictions
No prediction registered yet.
Weigh in
No community feedback yet.
New here? Create an account first
Create an account or sign in and your feedback is tied to you — you can track it, get replies, and claim this conjecture so others know you’re working on it. Prefer not to? Just leave your take below as a guest — only the name you type is shown.
Add your take
Posted immediately (spam is removed). Community feedback is never an adjudicated verdict and never changes this conjecture's triage label or status above.