The content rule now lives on the platform (what blocks a post, what sends it back to Drafts, scores and thresholds, what changes per network), and the agent reads it on every pass instead of remembering it. A reviewer token takes the posts in Review that have no verdict on their current content, judges them network by network, leaves a note the author reads, and its OK schedules the post at its time. The server has the last word: it recalculates the verdict from the scores, never sends on an OK from the same token that created the post, only lets an owner, admin or a member ticked "Their OK publishes" on the Team page release a post, refuses anything under 15 minutes away, and drops an OK the moment the post is edited. Skill 1.6.0 and MCP 1.1.0 carry the job and the prompt that sets it up.