One gate every post walks through

pendpost is agent-first: an AI agent drafts your posts, sizes them, and schedules them over MCP. Which is exactly why the engine has one rule that never bends. Nothing publishes until it clears a single pre-flight checkpoint, and an agent cannot approve its own post.

What the checkpoint is

Every post from every source hits the same gate. An agent can draft it. A schedule can pick its slot. None of that reaches a platform until a human approves it. The hand that wrote the post is never the hand that waves it through.

Why one gate and not ten

Early on the checks were scattered: one before scheduling, one at publish, one for media. Scattered checks drift. One grows a bug, a post could slip past, and you would find out once it was already live.

So we collapsed them into one fence. The same verdict runs whether the post came from you typing, an agent drafting over MCP, or a retry firing after a failure. There is a force override for the rare case you truly want to skip a check, and it gets logged.

What this buys you

You read the queue on your own time. You fix the two captions that need fixing. You approve the rest. The agent does the volume; you keep the judgment. Nothing goes out behind your back, because the only door out of pendpost is the one you hold.

MIT, local-first, agent-first. github.com/pendpost/pendpost