ops-socials

# /ops-socials — public social channels router Load `ops-rules` before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If `AskUserQuestion` / `Workflow` are missing, follow Rule 10 in `ops-rules` (Hermes: numbered options / two-turn Telegram card; `delegate_task`). Three reading/posting surfaces, **multiple publishing identities**. Don't cross the streams — between surfaces _or_ between identities. ## Resolve the IDENTITY before anything else (READ FIRST) This router serves two **strictly separated** classes of identity. Posting to the wrong one is the cardinal failure mode of this skill. 1. **Personal / founder identity** — the owner's own artist / entrepreneur brand. Publishes via **Typefully** (`$SOCIAL_SET_ID`, the global Typefully default). This identity is registered at `$PREFS_PATH/preferences.json` → `marketing.social_identities.personal.*`. 2. **Project brands** — each marketing project (e.g. a product) is its own brand with its own channels. Each is registered at `marketing.projects.<project>.social` with a `social.engine`. **Resolution algorithm — run at the start of every flow:** ``` intent is owner autopilot status (`my-project`, "show me the autopilot status", `/ops-socials my-project`, owner-autopilot read-out)? ├─ YES → skip project/personal identity resolution; run the Owner autopilot status recipe below (read-only). `my-project` here is NOT a project name. └─ NO → continue intent mentions / implies a named proje...