§ Executor · The compounding-content layer
Loopback.
Closes the loop on every week of content. The best work resurfaces, performance compounds, your audience sees the highlights without anyone curating them.
01 What it does
Loopback is the platform that makes every week of content compound. The pieces that performed get pulled back into your audience's view — repackaged for the right format, scheduled for the right window, shipped without anyone curating them by hand.
Content teams ship and forget. Performance signals come back days later, and the work that earned attention sits frozen at its original timestamp. Loopback closes that loop: it resurfaces what worked, so your audience encounters your best material more than once and your team stops paying full editorial cost for every new piece.
Performance pull
A weekly pull from your analytics layer ranks the content that earned attention against your performance criteria — reach, engagement, conversion, dwell.
Recap composition
The top performers get composed into a recap asset — slide format, carousel format, digest format, whatever your audience consumes best on each surface.
Multi-format output
One source recap, many destinations — Instagram carousel, link-in-bio digest, email roundup, newsletter section, internal review. Format is per channel; source is shared.
Scheduled ship
The recap ships on your audience's preferred cadence — weekly digest at the audience peak hour, automatic, no manual queue.
02 How it works
Loopback runs as a weekly durable workflow with five clean phases. By the time you'd open a spreadsheet to start the recap, the recap is already drafted, formatted, scheduled and audited.
Gather. The platform pulls the week's content list from your CMS and joins it with performance signals from your analytics layer.
Rank. Pieces are scored against your performance criteria — reach, engagement, conversion, audience signal — and the top performers selected.
Compose. The selected pieces get composed into a recap with the right narrative arc — opener, picks, throughline, CTA. Voice matches your editorial standard.
Format. The composed recap is rendered into every destination format — carousel slides, digest blocks, newsletter sections, link-in-bio entries.
Ship. The recap hands off to PressRelay, which distributes per-channel with the same recovery as any other piece. Atlas posts the receipt in the morning brief.
03 What it replaces
Loopback collapses the recap function — usually a weekly Friday afternoon scramble involving a spreadsheet, a designer, and a "this should go up Monday" Slack thread — into a single operated layer.
04 Live receipts
Loopback currently operates the recap layer of a live reference deployment — an editorial publishing platform under Umbra Group.
Reference deployment — sustained since 2026-05
- Weekly recap shipped every week, without exception, since deployment. The cadence has not slipped.
- Multi-format output — the same source recap renders to carousel format, link-in-bio digest, and internal review surface.
- Performance-grounded ranking — the recap is not the latest pieces, it's the best-performing pieces against the defined criteria.
- Handoff to PressRelay live — every recap inherits the same per-channel recovery as any other distributed piece.
- Zero designer time per recap — the design system was shipped once during the Sprint; every weekly recap renders against it.
Source — Internal observatory + per-channel audit · 2026-05
05 Pairs with
Loopback sits at the end of the editorial cycle, feeding back into distribution.
PressRelay
The composed recap is delivered to PressRelay, which fans it out to every channel with per-channel adaptation.
Operated by — cockpitAtlas
Weekly recap output and per-channel ship results surface in the Atlas morning brief.
Receives — metadataSchemaForge
Recap previews pull validated metadata so OG cards and channel unfurls are correct on first ship.
References — entitiesHubForge
When recap pieces reference entities, links resolve to canonical hub IDs maintained by HubForge.
06 Deploy in your org
Loopback is deployed during a Lighthouse Sprint that scopes your recap criteria — what counts as "best work" in your performance model, what formats your audience consumes, and on what cadence.
Criteria scoping (Pulso). We define the performance signals that count for ranking, the cadence your audience expects, and the destination formats you ship to today.
Composition tuning (Sprint). The recap design system is built once. Per-format rendering is wired. The handoff to PressRelay is configured. The pull from analytics is authenticated.
Ship (Watch). Platform goes live behind Atlas. The recap ships weekly on cadence with zero designer or operator time per cycle.
07 Pricing line
Loopback is included as an executor in any Lighthouse Sprint that touches your distribution or content compounding workflow. Operating cost is bundled into your Lighthouse Watch tier.
Standalone deployment (Loopback alone) is available from the base Sprint tier. Detailed pricing in the Sprint framework.
08 Engage
See a week of content compound, end to end.
We walk you through the live reference deployment: the weekly pull from analytics, the performance ranking, the recap composition, and the per-channel distribution — all running without operator action.