VENTUNO
ventuno --primer fast-world

FAST TV platform: a primer for AI labs and agent builders

FAST channels look like simple linear streams. Underneath, they combine media processing, scheduling, metadata, playout, advertising, monitoring, rights rules and operational recovery — which makes them a natural software world for evaluating coding agents.

watch FAST TV live →why it’s an RL environment
// what is fast

The internet-native version of lean-back TV.

FAST is free ad-supported streaming TV. A viewer opens a smart-TV app, a connected-TV platform or a web player and watches always-on channels — no subscription — funded by advertising. It feels like traditional television: channels, schedules, program guides, breaks and continuous playback.

But a working FAST channel is not a video playlist. The stream a viewer sees is the output of a chain of systems that each have to be correct — and stay correct, around the clock.

pipeline → viewer stream
01content library
02channel programming
03schedule + EPG
04playout stream
05ads + measurement
06as-run logs + analytics
// what a fast platform must do
01
content ingestion
Import video, inspect formats, normalize metadata, detect duration, quality, language, rights and technical readiness.
02
channel programming
Group content into shows, blocks, dayparts, themes and collections.
03
schedule generation
Build 24/7 timelines that respect duration, repeats, gaps, fillers, rights windows and programming strategy.
04
EPG generation
Publish machine-readable guide data so platforms know what is airing now and next.
05
playout
Turn a schedule into a continuous stream or stream-like playback experience.
06
ad monetization
Insert ad opportunities, track breaks, support VAST-style ad delivery and record impressions.
07
monitoring & recovery
Detect missing files, invalid schedules, stream gaps, failed jobs and schedule/playout mismatch.
08
as-run & reconciliation
Record what actually aired versus what was planned.
// why it’s harder than it looks

Both a media product and an operations system.

It carries time, state, contracts, failures and business rules — all at once, all the time.

Time-based behavior

A bug may only surface at 2:00 AM, during a rights-window transition, or when a schedule rolls over.

Stateful workflows

A channel moves from draft → validated → published → live → monitored → reconciled.

Cross-service dependencies

Media analysis, scheduler, EPG, playout, ad markers, monitoring and reporting all have to agree.

Real-world failures

Missing files, bad durations, broken metadata, invalid ad breaks, expired rights, repeated content and stale schedules.

Business constraints

A technically valid schedule can still violate programming strategy, sponsor rules, rights or distribution requirements.

// why it’s an rl environment

A living operational system, not a toy bug.

Many coding benchmarks test whether an agent can edit code. FAST World tests whether an agent can understand and repair a living operational system — reasoning across services, time, data, business rules and observable system behavior.

Every task starts from a controlled state and grades on outcomes: is the schedule valid, does the EPG match playout, do the as-run logs reconcile, is the API state correct.

[ see FAST World on the home page ]
rl_capability
fast_world_surface
repository_navigation
Find scheduler, playout, EPG, media and reporting logic
state_reasoning
Understand draft / published / live / as-run states
time_reasoning
Fix bugs across schedules, rollovers and rights windows
cross_service
Align scheduler, EPG, playout and reporting behavior
data_debugging
Trace bad metadata, duration mismatches, missing assets
incident_response
Diagnose stream gaps, missing-file fallback, failed recovery
deterministic_grading
Verify schedule validity, EPG output, as-run logs, API state
// example tasks
missing-file substitution
A scheduled asset is unavailable. Pick a valid fallback, preserve duration constraints and record the substitution.
EPG mismatch
The guide says one program is live, but the playout state reports another.
rights-window violation
A program appears outside its allowed territory or time window.
schedule gap
A 24-hour schedule has a 90-second hole after normalization changes a video's duration.
repeated-content bug
The scheduler violates repeat-avoidance rules inside a daypart block.
as-run reconciliation
The reporting system must distinguish planned events from what actually aired.
stream recovery incident
A simulated playout failure should recover to slate, resume cleanly and produce a traceable incident log.
// synthetic but realistic

Synthetic, grounded in real operations.

FAST World is an independently developed synthetic software world. It needs no customer data, production credentials or transferred platform assets. It is grounded in real media-platform operating patterns, but implemented as a new, deterministic environment built for agent evaluation and training.

synthetic datasynthetic channelssynthetic assetssynthetic schedulesdeterministic failuresprogrammatic verifiersrepeatable agent runs
// see it running

Watch the machinery in action.

The live FAST World TV demo shows the viewer-facing output of channels created through ChannelForge. This primer explains the platform machinery behind that experience — and why that machinery makes such useful long-horizon tasks for coding agents.

watch the live demo →
// sources
[ IAB UK — Free Ad-supported Streaming TV (FAST) ][ Gracenote — FAST channel & content distribution ][ IAB Tech Lab — VAST (video ad serving template) ]

Build agents that can handle the real thing.

Working with foundation-model labs, coding-agent companies, computer-use teams and post-training researchers.

discuss a worldFAST eval