Why verified?
Every 605Buzz article carries a signed cassette receipt — a small cryptographic envelope containing the article's text, the sources it cites, the AI pipeline version that drafted it, the human byline that approved it, and the timestamp of publication. (We call the envelope a "cassette" because it plays back the exact bytes that were signed at publish time — a snapshot you can rewind and verify, not a live-editable page.) The signature is Ed25519, minted by the runtime that produced the article, anchored to a per-tenant key held in the operator's tenant-scoped keychain.
What verified means, exactly
- The text was signed at publish time. Any change to the article after publication that isn't a signed correction breaks the signature. Readers, subscribers, and the Wayback Machine can all detect tampering by re-running the verify.
- The sources cited are attributable. Every article lists its Pluck source IDs in the cassette payload. You can walk from the article to the raw ingest to the original institutional source without our servers as a middleman.
- The AI pipeline is versioned. Articles drafted by a specific pipeline version carry that version in the frontmatter. If we swap a model or change a prompt template, downstream consumers know the article was produced by a different pipeline than the one they audited yesterday.
- The approval is stamped. A human byline reviewed and approved every article before it published. Whose byline, when the approval fired, and — for elevated-risk content — what evidence the approval carried (cool-off window clear, retype-confirm, or second-factor) are all on the cassette.
How to verify yourself
The receipt page at broadcast.run/r/<token> for each article runs a client-side Ed25519 verify against the tenant's published public key. If it says green, the article is byte-identical to what the runtime signed. If it says red, don't trust it.
The full receipt page + verification tooling ships alongside the first vertical launch (business intel is targeted as the first vertical; specific timing is aspirational).
Why this matters
In an era where LLM outputs get A/B'd behind the scenes, tweets get deleted after retweet, and screenshot-vs-truth wars become a distribution event: an outlet whose every claim is signed, timestamped, and third-party-verifiable is a different kind of source than one whose content vanishes when it becomes inconvenient. That's the bar 605Buzz holds itself to.