---
name: multi-channel-social-publishing
description: Adapts one approved piece of content to each target channel's format and schedules it, enforcing per-day limits and holding everything for pre-publish approval. Use when the user asks to schedule a post, publish across channels, or plan a content calendar.
metadata:
  version: "1.1.1"
---

# multi-channel-social-publishing

> **Client-neutral reusable package.** No client names, tenant or workspace identifiers, account or
> resource IDs, customer records, credentials, or internal paths. All examples are synthetic.

| | |
|---|---|
| Live catalog name | Multi-Channel Social Publishing |
| Live category | Social & Publishing |
| Catalog entry | 15 |
| Internal capability ID | `CAP-CC-02` |
| Provider | Social publishing services |
| Availability | Candidate; validate in the active Workspace |
| Deliverable type | `limited_pilot_package` |
| Validation status | Candidate; local package validation only |
| Version | 1.1.0 |


## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant
bindings for the required inputs below; this public package supplies no client facts or authority.
Consume `ask-ollie-authority-core` for authority, `outloop-access-fallback` for recovery and
resource verification, `email-lifecycle-core` for recipients, approvals and stored-copy delivery
verification, and the bootstrapper Runtime Contract for ownership, scheduling and completion.
These owners govern execution; this Skill does not implement a competing runtime.

Select the relevant expertise below for the requested outcome. Runtime governs combining Skills,
partial use and completing missing steps with other authorized capabilities. This Skill's domain
scope does not limit the Operator's wider authorized task. Preserve domain safety restrictions.
Verify findings against source evidence and read back any resulting artifact or authorized change.

## Business outcome

One approved asset reaches every channel in that channel's native format, on schedule, without anything going out unreviewed.

## Operating modes

Read · Analyze · Draft · Publish with approval

## Prerequisites — what must be true before this runs

- Workspace Context (brand, communication rules)
- An approved publishing grant per channel
- Per-channel validation completed

## Required inputs

| Input | Source |
|---|---|
| Connected channels and their handles | Workspace configuration |
| Per-channel format and length rules | Configuration |
| Publishing windows and per-day caps | Configuration |
| Approved media — real supplied assets only | Required |
| Named approver | Configuration |

## Boundary — state this to every client, verbatim

> Every channel is validated individually before first use. This is not a universal publishing bus.

A channel that works in one workspace proves nothing about another, and a provider that publishes text reliably may
fail on video. Validate per channel, per account, per media type.

## Caps are enforced across every workflow, not per workflow

A per-day publishing cap must hold across everything that can publish to that channel. Two workflows each honouring
a cap of one produce two posts. Enforce the cap on the channel, not inside the workflow, and queue the excess.

## Real supplied media only

Publish only assets the client supplied or approved. Never publish generated imagery as though it were real captured
material.

## Action classification

| Action class | This workflow |
|---|---|
| Read | Connected channel inventory, scheduled queue, post status, published history |
| Analyze | Per-channel adaptation, format and length validation, cap and window enforcement, duplicate detection |
| Draft | A per-channel variant with its media and scheduled time |
| Publish with approval | Schedules approved variants only, then reads back the scheduled state |
| Destructive | None. Never deletes a published post |

## Approval and delivery

The Operator applies Authority Core and the active Workspace approval policy to any requested
mutation. Email Lifecycle owns recipient classification, sending and stored-copy verification.
The action table defines this capability's domain scope; it grants no permission by itself.

## Expected output

A per-channel variant set with scheduled times, a cap-and-window compliance summary, and a read-back of each scheduled item.

## Synthetic placeholders used in this package

These are illustrative only. Real values come from the client's own workspace configuration and are
never written back into this package.

| Placeholder | Meaning |
|---|---|
| `CHANNEL_PLACEHOLDER` | Connected channel |
| `WINDOW_PLACEHOLDER` | Publishing window |
| `APPROVER_PLACEHOLDER` | Named approver |