Tweet Today

Produce at least three distinct single-post options grounded in real evidence. Use blog for an essay and standup for a team update.

1. Find receipts

Use the nearest source: current conversation, user draft, supplied daily summary, or structured receipt from another workflow. A receipt is a shipped change, fixed bug, observed detail, tested tool, decision, mistake, screenshot, or changed opinion.

If the source lacks a subject, stance, or concrete proof, ask only for the missing piece. Request permission before inspecting notes or Git.

Complete when the evidence supports three genuinely different signals rather than three phrasings of one claim.

2. Run the public-safety gate

Remove or generalize credentials, private URLs and repository names, customer data, unreleased metrics, internal architecture, config values, copied logs, and private backlinks. Keep receipt IDs and vault links as private workflow metadata.

For code, retain only the minimal public-safe lines and replace sensitive values with unmistakable placeholders.

Complete when every retained fact is publishable and traceable to the source.