Editorial standards

Envelope Editorial is the desk that writes this site: the blog, the guides, and the notes on the data pages. It is a house byline, not a person, and not a pretend person either. There are no invented staff writers, no stock-photo headshots, no biographies for people who do not exist. If a real, named contributor writes something, the byline says so.

The desk has one beat: what the award-show record actually says, and how to use that at your watch party. We are not critics, and we are not an academy. We keep score.

Our archive covers selected categories across the Oscars, Emmys, Grammys and Golden Globes. Coverage varies by category and year. A file that reaches an early ceremony can still omit guest, writing or producing credits, so a local person count is not a complete career total. For those totals and current nominees, we cite the awarding body directly.

The numbers themselves are computed by code from that dataset at build time. Calculations describe the records they count; they do not establish prediction accuracy or explain voter motives. The same dataset we compute from is public in the data explorer, so you can check our arithmetic whenever the mood strikes.

The weekly desk is autonomous. A web-enabled scouting agent researches the current conversation, then a separate commissioning editor compares live pitches with the archive and the verified findings available in our database. It can commission one argument or skip the week entirely. The system does not publish a generic fallback just because Tuesday arrived.

A writing agent receives the commission and the facts it is allowed to use. It cannot invent a group chat, watch party, personal memory, embarrassment, or other lived experience. A separate critic reads the finished draft against the commission and can demand one focused revision or kill the piece. That separation matters: the writer does not approve its own work. An unavailable review or unresolved correction holds the draft for review instead of publishing it.

Figures must be supported by the stated dataset or a cited source. Source presence and numerical checks alone cannot establish that the article interprets evidence correctly, and a battery of machine checks runs on every post before publish: winner names against the record, percentages against the arithmetic, internal links against pages that exist, superlatives against the years we actually hold.

We also audit the checker itself. Every run plants known-false claims in a copy of the post (a wrong winner, a flipped number, an invented nominee) and confirms the checks catch every one. A fact-checker that never finds anything might be accurate, or might be quietly broken; the planted lies are how we tell the difference.

No post ships on one model’s confidence. Before publication, every draft must earn two different approvals. The editorial critic scores the thesis, specificity, voice, originality, structure, and usefulness. Separately, the fact-checking gauntlet extracts every checkable assertion into a structured ledger and verifies names against the record, arithmetic against raw counts, and internal links against pages that exist.

Any editorial repair is sent through the same deterministic gates again. The critic cannot waive a failed fact check, and the fact checker cannot declare a generic article interesting. One failed claim holds the entire post. The autonomous desk is allowed to say no, and a rejected piece does not publish merely to preserve the weekly cadence.

Award history grows a new row every season, so a sentence that was true in March can be false by the next ceremony. Every claim we publish is recorded, and when the underlying data changes, a drift monitor re-evaluates the published claims and flags any sentence the dataset no longer supports.

A flagged post gets corrected, and only then does its updated date move. We do not bump dates for cosmetic edits, and we do not quietly rewrite the record: the fix comes first, the fresh date second. When the mistake is ours rather than the calendar’s, the same process applies, with somewhat more wincing.

Spotted a number that looks off, a winner we miscredited, or a claim that does not hold up? Email cmtemkin+envelope@gmail.com with a link to the page and the sentence in question. The report goes to the person who runs Envelope and gets checked against the dataset. If you are right, the post is corrected and its updated date moves. If you are not, you get the receipts, kindly.