§ Executor · The distribution layer of your stack
PressRelay.
Multi-channel content distribution with per-channel recovery. Captions tuned per platform, failures isolated to one channel at a time, nothing dropped.
01 What it does
PressRelay is the platform that gets your content to every place it needs to be. Social channels, partner feeds, syndication endpoints, link-in-bio surfaces, internal newsletters — wherever your audience is, your content arrives, formatted right, on schedule, with the failures of one channel isolated from the rest.
Most distribution tooling treats channels as a fan-out: one post, broadcast everywhere, fire and forget. When one channel times out, you find out next quarter from a metrics dashboard. PressRelay treats every channel as its own recoverable transaction — observable end-to-end, isolated from the rest, lands cleanly or surfaces an actionable failure.
Per-channel adaptation
A single piece of content is reshaped per destination — caption tuned to platform norms, format converted (image vs carousel vs short-form video), length adjusted, hashtags localized. One source, many faces.
Per-channel recovery
Every channel runs as an isolated transaction with its own retry envelope. If one channel times out or rate-limits, the others ship as planned and the failed channel re-queues for the next valid window.
Scheduled posting
Cadence is enforced per channel — Instagram at peak, partner feeds at the agreed hour, syndication on contract schedule. The platform doesn't ship until the window is valid.
Health gating
A page that OnPage Doctor flags as unhealthy doesn't get re-distributed. PressRelay defers until the fix lands. You stop amplifying your own broken pages.
02 How it works
PressRelay runs as a durable workflow per piece of content, fanned out to one sub-workflow per channel. Each channel is observable, recoverable and independently retryable.
Pick up. The platform subscribes to ready-to-distribute events from your content system — new publish, scheduled re-share, Loopback recap, manual trigger.
Fan out. The content is split into one sub-workflow per channel. Each carries the source asset plus the channel-specific adaptation instructions.
Adapt. Per channel, the caption is rewritten to platform norms, the media is reformatted, hashtags get localized, the preview gets validated metadata from SchemaForge.
Ship. Each channel posts on its own schedule via its own API. Successes are logged; failures retry with backoff or surface to Atlas for the operator.
Reconcile. A confirmation pass per channel verifies the post landed, captures the published URL, logs engagement signals if available. The audit log is the source of truth.
03 What it replaces
PressRelay collapses the entire distribution function — usually a social-media manager, a scheduler tool, and a Slack channel of error pings — into a single operated layer.
04 Live receipts
PressRelay currently operates the distribution layer of a live reference deployment — an editorial publishing platform under Umbra Group.
Reference deployment — sustained since 2026-05
- Three channels live — Instagram, Facebook, link-in-bio — each with its own adaptation profile and isolated recovery.
- Per-channel recovery proven — when one channel hit a multi-hour outage, the other two shipped clean and the failed channel re-queued and recovered without operator action.
- Caption adaptation per platform — captions are not the same string broadcast everywhere; they're regenerated for each channel's voice and norms.
- Health gating live with OnPage Doctor — pages flagged unhealthy defer re-distribution until the fix ships.
- Zero dropped posts across the reference deployment since the per-channel recovery pattern shipped.
Source — Internal observatory + per-channel audit · 2026-05
05 Pairs with
PressRelay sits at the end of the content pipeline — most other executors feed into it.
Loopback
Loopback assembles the weekly recap; PressRelay ships it across every channel with per-channel adaptation.
Gates — page healthOnPage Doctor
Unhealthy pages defer re-distribution until the repair workflow ships the fix.
Operated by — cockpitAtlas
Per-channel failures, retry chains and reconcile outcomes surface in the Atlas morning brief.
Receives — preview metadataSchemaForge
Distribution previews pull validated structured-data metadata so OG cards and platform unfurls are correct on first try.
06 Deploy in your org
PressRelay is deployed during a Lighthouse Sprint that scopes your channel map — which destinations you ship to, what each one requires, and what "tuned per platform" actually means for your voice.
Channel mapping (Pulso). We catalogue every destination your content reaches today, the adaptation logic per channel, and the schedule expectations. Output is the channel matrix.
Recovery wiring (Sprint). Per-channel sub-workflows are built. Authentication is wired per destination. Adaptation profiles are tuned with your team. Retry policies and rate-limit envelopes are configured.
Ship (Watch). Platform goes live behind Atlas. Failure rate drops to near zero. Dropped posts go to zero. Your distribution function is now operated, not staffed.
07 Pricing line
PressRelay is included as an executor in any Lighthouse Sprint that touches your distribution or content amplification workflow. Operating cost is bundled into your Lighthouse Watch tier and scales with channel count.
Standalone deployment (PressRelay alone) is available from the base Sprint tier. Detailed pricing in the Sprint framework.
08 Engage
See three channels firing with recovery, end to end.
We walk you through the live reference deployment: a fresh publish fanning out to three channels, one channel forced to fail, the other two shipping clean, and the failed channel recovering on the next valid window — all without operator intervention.