Shipping in public.
What changed in Margo, newest first. Written the way the department reports: what shipped, why it matters, no adjectives doing the work.
The operating manual + Ask Margo
Every gate, ladder, and ritual is now documented inside the product itself — and Ask Margo answers questions about your own department from that manual. Why was this held? What does the send gate check? Ask, get the real answer, keep moving.
Public demo workspace
The demo at /demo is now a live, read-only workspace running on real data — today's rituals, the actual approval queue, this morning's brief. No staged screenshots; if the demo human falls behind, you'll see the queue back up.
E2E golden path + org deletion
The full journey — signup, onboarding, first day on the clock — is now covered end-to-end in CI, so the front door can't quietly break. And organization deletion is complete and verified: when you ask for your data gone, it goes.
LLM cost ceilings + activation emails
Every workspace now has hard ceilings on model spend, enforced per role per day — the department budgets its own thinking. New workspaces also get a proper activation sequence instead of a login link and silence.
Four-source truth pipeline + inference ledger
Revenue truth now reconciles four sources — platform claims, analytics, the store, and the bank of record — into one number the whole department reports against. Every inference Margo draws is written to a ledger you can audit.
The ingestion seam + first-day onboarding
Import your history and Margo starts working before a single platform is connected — the ingestion seam feeds the same pipelines live connections do. First-day onboarding now walks a new brand from empty workspace to a running clock.
Decisions propagate: QA-gated publishing, voice learning
Your approvals now teach the department. Edit a draft and the voice guide updates; reject one and the reason becomes precedent. Publishing sits behind the QA gates everywhere — there is no side door to the feed.
Per-org settings, notifications, the daily digest
Workspaces now carry their own settings — channels, thresholds, notification rules — and a daily digest lands each morning with what happened, what's waiting, and what needs a decision from a human.
The department engine: six roles on the clock
The core engine shipped: six roles running scheduled rituals against a shared calendar. Strategy briefs, social drafts, email checks, design queues, paid reconciliation, the analytics brief — on time, every day, without being asked.
The department surfaces: approvals, queues, gates
The surfaces where you meet the department: the approval queue, the request queues, and the gates that hold work until it's complete. From the first commit, nothing ships without a human's yes.
Earlier work predates the public log.