CEDX Social · Marketing
Publishing is the easy part. Social tracks what happened after: engagement rate and half-life per post, the 23 publishes that failed and why, and the 61 inbox items aging without an owner.
A clip that dies in 6.8 hours and one still earning at 14.2 are the same format on paper. Half-life is how you tell them apart.
Runs on demo data. The accounts, posts and metrics are the demo workspace's.
What it is
Month grid, week list, day detail — every cell a real post with its network and format marked. 54 scheduled posts sit ahead; draft, published and failed are filters of the same view, so the queue and the record are never two places.
321 rows with status, network, format, impressions, engagements, rate and owner. The top carousel earned 4.5K engagements on 51K impressions — an 8.8 rate. The best clip holds a rate of 10 on fewer impressions. Both truths are on the same table.
The composer takes a brief and writes three caption lanes — bold, helpful, data-led — per network, nine variants for three networks. Each carries the predicted engagement band for its format and network before anyone commits to it.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/social.
01 — Overview
The alerts lead with what broke: 23 failed publishes — scheduled video stuck in the failed state; seven posts dying faster than their format's median; one clip at −78% against its expected curve, and another at +71% worth reposting.
02 — Calendar
Launch cuts, how-to cards, hiring proofs and recap frames share one grid — with the failed cell as visible as the published one, because that is where the work is.
03 — Posts
Draft 55, in review 34, scheduled 54, published 129, failed 23 — the status chips are counts, not labels. Open any row and impressions, engagements, rate and owner travel with it.
04 — Composer
The predicted-bands rail prices format by network — video 3.6–6.4%, community 3.1–5.2%, professional 1.9–3.4% — and each variant quotes its band. Send to drafts lands the pick in the post library.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Owns the calendar and the composer, and picks the variant whose band justifies the post.
320 posts · 54 scheduled
Cuts the clips and watches half-life — a 6.8-hour clip gets reworked, a 14.2-hour one gets reposted.
median HL · 9.9h
Reads decay next to paid: when organic dies faster than baseline, the boost decision has a number behind it.
decay alerts · 85 anomaliesThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
The calendar holds the month — every cell a real post with network and format, nothing floating in a separate doc.
One brief becomes nine variants across lanes and networks, each quoting its predicted band.
Scheduled posts go out — and the 23 that fail surface with causes instead of vanishing.
Half-life is measured per post; anomalies at −78% and +71% both become decisions, not mysteries.
One record
Posts are not orphaned content. The assets, campaigns and analytics behind them are the estate's own.
The campaigns the posts serve — the social pack is an asset checklist line on the campaign brief.
CEDX AssetsClips and images come from the governed library, rights status attached.
CEDX Web AnalyticsThe sessions social sends, measured with the same channel names.
CEDX WebinarsThe sessions social promotes — replays become the clips with the longest half-life.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your channels, your queue
Social with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/social. It runs on demo data — the accounts and posts are the demo workspace’s.
The time a post keeps earning engagement. The demo median is 9.9 hours; posts dying faster than their format's median get flagged, and outliers in both directions become decisions — rework or repost.
It stays visible. 23 failed publishes sit in the queue with a cause — scheduled video stuck in the failed state — instead of disappearing from the record.
No. It writes nine variants with predicted bands and sends nothing to drafts until a person picks — the sent counter reads zero on screen.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then ask which of your posts would show a 6.8-hour half-life.