the receipts

EDITORIAL POLICY.

MilesBuzz is a fast, tactical news channel on miles, points, cards, and status. Here is exactly how a drop gets made and what our bylines are.

Where the signal comes from

Every drop starts from a real reader question asked in a public frequent flyer forum around the web — things enthusiasts are actively puzzling over that day. Our editors watch a rotating shortlist of sources; when a question is timely, tactical, and answerable, it enters the queue.

How a drop is drafted

Drafting is model-assisted. A large language model produces the first pass in the locked voice of the assigned host — Wire, Plastic, Altitude, or Glitch — using a persona prompt maintained by MilesBuzz. Every persona has a defined beat, a set of sources it tracks, and a house style. A drop that doesn't fit the beat gets reassigned or killed.

Human review before publish

A MilesBuzz editor reviews every draft before it goes live: fact-check on program rules and cited numbers, sanity-check on "the play," and voice-check against the host's baseline. Drops we can't verify get held, cut, or reframed with an explicit uncertainty note.

What our bylines are

The Buzz hosts are editorial personas, not natural persons. Each host has a locked voice, a defined beat, and a consistent point of view — like a column, not a masked reporter. We say this plainly on every host page and in the JSON-LD served to search and AI engines. If you see a byline on MilesBuzz, it is a persona operated by MilesBuzz.

Corrections

When we get something wrong — a chart mispriced, a partner missed, a fare rule miscalled — we amend the drop in place with a visible correction note and log it publicly, by date, on /corrections. We do not silently edit. Substantive changes always earn a line on the log.

What we don't do

• We don't invent quotes or attribute claims to real named people.
• We don't publish drops on programs or partners no host on the roster actually tracks.
• We don't take payment to move a story, a card, or a program in the ranking.
• We don't dress AI personas as real humans in bios, schema, or share previews.

Contact

Correction requests, source tips, and questions about a specific drop go to [email protected]. Include the drop URL and what needs to change.