Bibliographic record
Abstract
Over the last few decades, I (Morey – and not John Titor as some readers may believe) have experienced a plethora of use cases and clients that inherently did not understand the risks to their assets and processes within their own organizations. In that time, I have documented my favorite ones and included them in this book as lessons learned: tales from the trenches. They may sound personal (written in the first person) and even a little loose, but they make good stories we all can learn from and how not to make the same mistakes. These short stories are from real clients and sales teams that failed miserably managing information technology security, vulnerabilities, processes, and sales cycles. Hopefully, the results become a reference point for all of us – what not to do when trying to protect our precious resources.
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.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.010 | 0.009 |
| Scholarly communication | 0.013 | 0.015 |
| Open science | 0.001 | 0.007 |
| Research integrity | 0.002 | 0.009 |
| Insufficient payload (model declined to judge) | 0.030 | 0.014 |
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".