Emerging Edge Media — Agentic Workflow Dashboard

A book, end to end

Two tracks, one rule: whichever track publishes the book, Marketing & Promotion runs the promotion. The Self-Publishing Unit hands over the finished book + launch package; querying hands over the deal. Sales and list response flow back to Books as the signal for the next title.

Reach → leads → revenue

Social reach is raw material, not the goal. Promotion & Sales aim it at the funnel; the funnel converts it to leads; List Health & Growth keeps those leads engaged and buyable; Community nurtures them up the ascension journey toward programs and coaching.

The show feeds everything

One anchor episode a week becomes drafts for every channel, and its transcript joins the searchable library — the same library the support drafter and session prep answer from. Outreach compounds the audience from both directions: Derek as guest, and guests on his show.

Advice & oversight loop

Decisions flow down the same path work flows up: units report status changes, the Agentic COO rolls them up, the Coach advises from the full picture (grounded in Sage's knowledge of Derek), and Derek's call returns as sequenced work — not a loose intention.

1 · Events, not streams

Each agent emits one small event per state change, carrying task_id · run_id · agent · status plus a one-line summary and a blocker note when there is one. Silence means “still doing what the last event said” — which costs nothing.

2 · One small status table

Every event appends one row to a single run table. This dashboard reads only the latest status per task from that table — it never polls the agents themselves. One run_id joins the trace, the cost, the approval decision and the quality score; anything that can't join by run_id is a silo, not a dashboard.

3 · Coordinator rollups

Workers report to a coordinator (Muse, per unit), and the coordinator writes one summary line per workstream — the line you see on each card above. Twenty workers become one readable line. You open the drill-down only when a line needs your eyes.

4 · Heartbeat catches the silent failures

A scheduled check every ~15 minutes flags any run still marked “running” past its expected window — the failures that never send a “failed” event. Blocked + stale runs roll into a daily digest. Output lands as ready for review; only a human acceptance moves it to accepted — attempted, reviewed and accepted are three different states.

Knows you & remembers

• Standing memory: your rules, people, projects, locked decisions — applied without re-briefing
• Morning brief, inbox watch, calendar — the day's picture in one place
• Self-check discipline: every number pulled fresh from the source before it's reported to you

Runs operations

• Email, calendar, Drive/Docs/Sheets, ClickUp, Slack — read, draft, send, file, track
• Batch campaigns (like the query wave) under standing authorization, with per-item QA
• Long lanes — downloads, transcription, indexing — kept moving with stall detection

Researches & verifies

• Deep web research with sources, like the report behind this page
• Live verification of people, companies, prices, windows — stale labels re-checked, never trusted
• Best-practice first: how pros actually do it, before improvising

Builds pages & apps (Spaces)

• Pages — hosted, can be published to a public link: the Master Manual, the daily brief site, this dashboard
• Apps — pages with their own database that remember what you enter: trackers, planners, logs; they stay private to you
• Documents too: Word, PDF, decks, spreadsheets you keep editing

Builds from your real stuff

• Your Drive, Gmail, Calendar, Sheets, ClickUp, Teaching Library, workbooks
• Searchable systems over your own corpus — the Asset Management System is the template
• Nothing invented: dashboards show your actual agents and their actual state

The honest limits

• No native phone apps; pages don't work offline
• A static page can't save typed input — that's what the app kind is for; an app can't be published publicly
• Live data needs a live source — this board refreshes on status events and snapshots, not magic
• Deleting an artifact is permanent — Muse always checks with you first

The five surfaces (what grows on the run table)

• Launch gates — success rate, unresolved failures, eval pass rate, approval backlog → decide whether to scale a workflow
• Run explorer — searchable runs by workflow, version, model, state → debug a failed or expensive run
• Trace detail — nested model / retrieval / tool / approval spans → find the exact failing step
• Cost attribution — cost by workflow, model, prompt version, outcome → change routing, limits, prompts
• Approval queue — pending / approved / rejected / expired / escalated → the “Waiting on Derek” section above, live

Authority ladder — autonomy is earned per workflow

• L0 Read & answer · L1 Draft & recommend · L2 Reversible actions, logged
• L3 Prepare consequential actions for human approval · L4 Unattended inside narrow limits, with monitoring and stopping rules
• Begin read-only; promote a workflow only after it passes real cases repeatedly
• An agent trusted to draft a brief has not earned the right to touch the CRM — authority is per workflow, not per agent
• Every agent gets a written charter (outcome, scope, sources, tools, evidence rules, definition of done, escalation, owner, review date) and a line in the agent register: no register entry, no credentials