social-publishing-weapon

The publishing rulebook for social-publishing-guardian. It encodes how to get finished social content into connected accounts SAFELY (as drafts a human reviews and publishes), the live-verified GoHighLevel / LeadConnector Social Planner API contract, the Zernio runbook (REST + MCP), the alternative-provider landscape, and the provider-agnostic invariants (publish gate, idempotency, read-back verification). The GHL runbook was verified live against a real client account on 2026-06-29 (location z1iSilSVX6vJSU01d92u) and corroborated against current public docs by loremaster (see research/research-summary.md).

The one rule that gates everything

DRAFTS ONLY. NEVER auto-publish. The most polished post is a liability if it goes live without the client's sign-off. Create every post as a DRAFT. The human schedules or publishes each draft in the platform UI.

The unsafe behavior is the DEFAULT on every provider studied:

• GHL status:"scheduled" AUTO-PUBLISHES at its scheduleDate. The approver/userId field does NOT route a post to a held approval queue (research/ghl-social-planner/2026-06-29-ghl-create-post-api.md).
• Zernio MCP DEFAULTS to scheduled, 60 minutes out, unless you pass is_draft=true (research/zernio/2026-06-29-zernio-mcp-server-default-scheduled-footgun.md).
• Even tiered approval CHAINS end in auto-publish; the only truly safe state is a draft a human manually promotes (research/publish-gate/2026-06-29-approval-gate-automation-risk.md).

The Guardian's whole value is forcing the draft state explicitly, every time. See guides/01-publish-gate.md.

Critical directives (the guardrails)

These come from the Command Brief's SUBAGENT CRITICAL DIRECTIVES, deepened by research. Full treatment in guides/00-principles.md.