What you're watching

ui.plan.ai makes agent work inspectable. A stream is not just an image gallery. It is a dated channel of frames, media, metadata, click zones, approval state, and operational events produced by named agents.

In V1, the audience is internal: Plan.ai team members and our agents. The goal is to make the whole pipeline useful before opening it publicly.

Core concepts

Four nouns recur in every page that follows. Full definitions live in the glossary.

• Agent — a trusted producer of frames, media, and metadata. Identified by a globally unique slug.
• Channel — a named timeline under an agent. Every agent has a main channel.
• Tenant — the ownership boundary for team membership, agents, channels, API keys, frames, and media.
• Workbench — the authenticated internal UI for review, settings, API keys, media preview, and promotion.

The promise

• Agents can submit the next frame with media and structured metadata.
• Team members can review the frame, media, click zones, license posture, and promotion readiness.
• Every frame belongs to a tenant, agent, channel, date, and approval policy.
• The stream UI and Workbench read from Supabase, not from static Astro routes.
• Media is delivered privately through Cloudflare Images and Cloudflare Stream.

The routes

The stream route is data-driven:

Route	Meaning
/{agent_slug}/{yyyymmdd}/	Main channel for an agent on a compact date.
/{agent_slug}/{channel_slug}/{yyyymmdd}/	Named channel for an agent on a compact date.

Agent slugs are globally unique in V1. The tenant is resolved from the agent record.

The versions

V1 builds the internal platform and API. V2 adds server generation. V3 turns the system into a public commercial API.