Scheduled · 0 18 * * *

Daily fleet briefing

Generates a short written report and a podcast-format audio episode of what the fleet has been working on in the last 24 hours.

Status

Draft

Trigger

Scheduled · 0 18 * * *

Owner

john

Steps

6

Definition

Steps, top to bottom.

  1. Pull yesterday's audit log

    All agent invocations grouped by agent and team. Aggregate-only — no individual employee names.

    Fetch

  2. Pull workflow run summaries

    Workflow runs that completed, failed, or are in flight. Step-level timing and cost.

    Fetch

  3. Per-team summarizers (parallel)

    Fan out via Queues — one summarizer per team, each writes a 3-bullet digest of its team's AI activity.

    Agent → basal

  4. Compose master briefing

    Stitch the per-team digests into a single executive briefing. Sections: shipped, hot, anomalies, coming next.

    Agent → basal

  5. Render to TTS

    Phase 4: synthesize the briefing as MP3 audio for the podcast feed. Stored in R2.

    Transform

  6. Publish

    Write episode row to D1; static page reads latest. RSS feed regenerates.

    Deliver

Why we run this

The daily fleet briefing is the single most visible Cloudflare Workflow on the platform. It’s the surface that makes the AI fleet’s work legible to leadership and the team, in a form that respects their time — read it in 90 seconds or listen while making coffee.

The privacy discipline is built into the workflow: aggregation happens at the per-team level, individual employee names never appear in the output, and prompt content is never quoted. The briefing reports on the work, not on who did it.

The workflow lives in apps/workflow-runner/ once Phase 3 lands; today it’s an MDX-defined shape we read into the catalog page.

Run history

Mock data

Last six runs.

Durations, outcomes, and costs below are mock data — every number on this table is fabricated for the demo. The real run history will come from the workforce audit log + fleet-api Worker once Blocks 3 and 4 land (see /roadmap). The table renders the same; the source of truth changes.

When Status Duration Triggered by Version Cost
2026-05-10 07:00 Success 14.2s cron v3 $0.084
2026-05-09 07:00 Success 12.8s cron v3 $0.079
2026-05-08 07:00 Success 19.4s cron v3 $0.094
2026-05-07 07:00 Failed 11.7s cron v3 $0.012
2026-05-06 07:00 Success 13.1s cron v2 $0.081
2026-05-05 07:00 Success 16.4s cron v2 $0.090

Designer · Phase 4

Edit, version, A/B promote.

The in-UI designer lets you edit step lists, swap agents, adjust prompts and parameters, save a new version (immutable history), and promote a candidate when it wins on cost, latency, or quality. Wired with Phase 4. Today's edits go through a platform-team PR.

See /roadmap for sequencing.