How this works

Software pulls candidates from feeds we trust. A person decides what ships. Every item links a primary source.

We write what happened in plain language — the claim, then one line of context only if the source said it. If we can’t say why it’s worth a minute without stretching, it stays off the front.

On X as @progressproof — same items, fewer posts.

Refusal list

Hook headlines that hide the fact
Opinion dressed as an event
True-but-dull filler to hit a quota
Silent edits when we’re wrong
Pay-to-feature on the feed or archive

The pipe

trusted sources (RSS, sometimes an X seed) → fail-closed truth check → keep only what’s noteworthy → write the claim straight → show it here with the source and any corrections

Our lane

Deeds: built, found, learned, shipped — especially useful AI and human work. Other outlets cover conflict. We cover constructive events that cleared the gate.

Mistakes

We make them. Fixes live on the story and on Fixes.

Open

Ranking and gates live in code: verify.py, pipeline.py, voice.py, site_export.py.

Pipeline is MIT-licensed with the project. Set brand.repo_url when public.

The letter, and money

The weekly letter is the same units that already shipped on X. Subscribe at Newsletter. Tips, the Method Pack, and briefings: Support. Brands may buy a disclosed note in the letter — never a feed slot.

Today