Content Backlog Protocol

When the content backlog is in focus, do not leave publishable rows quietly half-finished.

The canonical social ship queue is wiki/career/content-backlog.md. If that page is edited, discussed, or materially affected by the session, close by surfacing rows not yet Posted. Source: Operational Heartbeat; Content Backlog

Required Gate

1. Inspect rows not marked Posted.
2. For Ready to post rows, run a social drafting pass.
3. Apply humanizer.
4. Apply kevin-voice for X/LinkedIn or slack-voice for Slack.
5. Report what remains blocked, scheduled, ready, or posted.

Durable Behavior

Update the backlog only when status, copy, channel, source, or next action changes. Do not invent a content plan from a vague signal; route idea capture through the appropriate career/content page first.

Failure Mode

The common failure is producing good copy in chat and leaving the backlog stale. The backlog is the state machine. Update it or explicitly say why no durable update was made.

---

Timeline

• 2026-07-01 | Expanded the content backlog gate into a state-machine closeout for publishable social rows. Source: User request, 2026-07-01
• 2026-05-31 | Content backlog protocol from HEARTBEAT and USER. Source: public wiki expansion, 2026-05-31