Bibliographic record
Abstract
Epilogue, or the squirrel who got away?So, has Monstrous Moonshine been explained?According to most of the fathers of the subject, it hasn't.They consider VOAs in general, and V in particular, to be too complicated to be God-given.The progress, though impressive, has broadened not lessened the fundamental mystery, they would argue.For what it's worth, I don't completely agree.Explaining away a mystery is a little like grasping a bar of soap in a bathtub, or quenching a child's curiosity.Only extreme measures like pulling the plug, or growing up, ever really work.True progress means displacing the mystery, usually from the particular to the general.Why is the sky blue?Because of how light scatters in gases.Why are Hauptmoduls attached to each g ∈ M? Because of V .Mystery exists wherever we can ask 'why' -like beauty, it's in the beholder's eye.Understanding doesn't put an end to questions, it spices them.There's always a horizon, no matter how high you climb, beyond which everything is still hidden.However, have we really isolated the key conjunction of properties needed for Moonshine to arise?Can we derive the Monster from Monstrous Moonshine?In Section 7.2.4 we make the case for a more direct, topological explanation for Moonshine involving compatible actions of the Virasoro algebra and the braid group B 3 .In any case, we need a second independent proof of Monstrous Moonshine.Moonshine is now 'leaving the nest'.We are entering a consolidation phase, tidying up, generalising, simplifying, clarifying, working out more examples, climbing a few metres higher.Important and interesting discoveries will be made in the next few years, and yes, there still is mystery, but no longer does a Moonshiner feel like an illicit distiller: Moonshine is now a day-job!
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.006 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.003 | 0.004 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.355 | 0.137 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".