Proof / The system behind Satoshi Gazette

One working example.
Inside Satoshi Gazette.

Satoshi Gazette is a MaydaLabs-owned Bitcoin publication with independent editorial standards. This is a look at its software and editorial workflows, not a client result or a requirement for your business to work the same way.

Figures as of 2 September 2026.

The numbers

34

pieces published — stories, wires, briefings, data desk

100%

of publications passed a human approval before going out

44

editorial control cases tracked through the pipeline

454

automated tests on the operating system behind it

11

treasury-desk entities, each verified against a regulatory filing or audited report

0

external actions ever taken without an approval — by design

The pipeline, honestly split

Seven stages. The machine does the volume; a human owns every consequence.

  1. Intake machine
    Feeds, newsletters, and submitted signals are fetched, normalized, and de-duplicated automatically.
  2. Triage machine + rules
    Deterministic scope and duplicate gates decide what becomes an editorial candidate.
  3. Drafting AI
    Candidates are drafted by AI, grounded in the publication's charter and the collected sources.
  4. Evidence rules + human
    Every claim is linked to a source with a role — primary, supporting, background, counterpoint — or it cannot publish as fact.
  5. Approval human
    Nothing publishes without an explicit, recorded human approval. No approval means no external action.
  6. Publish machine
    Approved pieces are inserted idempotently; the live site is the source of truth.
  7. Reconcile machine
    Distribution is verified against public URLs — a post counts as posted only when the public record proves it.

Try the gate

The machine drafted this. It can't do the next part.

A local demo — nothing is sent anywhere. Notice the one claim without a source: it's marked, and it stays marked.

Draft · machineDRAFT

Corporate treasury desk: two new filings this week

Claims in this draft

  • Company A disclosed additional BTC purchases in an 8-K filing.sec.gov/…/8-K
  • Company B's quarterly report lists BTC holdings at cost basis.sec.gov/…/10-Q
  • Analysts expect further purchases next quarter.unverified — will not publish as fact
Waiting for a human. The AI has no publish authority.

Ledger

No external action recorded.

In production the ledger entry carries the approver, the timestamp, the piece id, and — after reconcile — the public URL.

The two rules that make it trustworthy

Source-linked or unverified

If a claim has no source URL, it is marked unverified and does not publish as fact. This is enforced by the pipeline, not by good intentions.

No approval, no external action

The AI can draft, sort, and prepare. It cannot send, publish, or spend. Ever. The approval surface makes review take minutes — but the click is always human.

What can carry over to your project

Source tracking, connected tools and human review can also be useful outside publishing. We start with your actual process, then scope the software or automation it needs. This example demonstrates implementation, not a promise of the same results.

Satoshi Gazette is a MaydaLabs-owned publication with independent editorial standards; its coverage is never for sale, including to our clients.

Want this on one of your workflows?