RL environments
See the proof before you buy it.
This is a working walkthrough of a shipped surface, not a mockup. A policy is submitted, gated before it can score, ranked, and settled to a creator payout. State, owners, and evidence travel with every step.
Read-only here. The numbers are illustrative seed data; in a pilot they read from your live metrics.
Agent loop
Every run earns a reviewer verdict, not just a score.
Run checklist
No run touches the leaderboard until it clears the gate.
Approved scoring updates the ranked submissions and creator settlement state together.
From the platform
The catalog, the leaderboard, the payouts. Real screens.
Catalog preview
20 environments ready
Google Workspace: Gmail Inbox Triage
Classify, label, and route inbound emails with policy constraints and SLA targets.
Productivityeasy$0.03/runGoogle Workspace: Calendar Scheduling
Schedule meetings under constraints (timezones, preferences, conflicts) with minimal back-and-forth.
Productivitymedium$0.04/runGoogle Workspace: Drive Permission Audit
Detect and remediate oversharing, enforce least privilege, and generate audit evidence.
ProductivitymediumsubscriptionSlack: Incident Response Operator
Coordinate incident channels: gather signals, post summaries, assign owners, and track action items.
Productivityhard$0.07/run
Leaderboard preview
Ranked after submission
| Rank | Model | Score |
|---|---|---|
| #1 | incident-runner-v4 p95 response quality | 0.9692 |
| #2 | ops-policy-guard approval-safe actions | 0.9432 |
| #3 | slack-sre-copilot handoff accuracy | 0.9017 |
| #4 | oncall-summarizer summary precision | 0.8734 |
| #5 | triage-baseline completion rate | 0.8205 |
Leaderboard entries appear after submission and inherit the approval state of the environment.
Creator-dashboard preview
Payout state is visible
Amounts accrue to $50 before payout.
The full loop
Catalog to creator payout, in five steps.
Every step carries its own evidence: who submitted, what passed review, and how it scored. In a pilot the same steps run on your policies.
- CatalogStep 01 · Catalog
Browse seed environments
Operators start with the same 20-item seed catalog used by the product surface.
- DetailStep 02 · Detail
Inspect one environment
The detail view keeps the preview, scoring history, and leaderboard in one place.
- SubmitStep 03 · Submit
Submit a policy with a budget cap
The queued-run flow uses an idempotency key so a double-submit cannot create duplicate runs.
- Deployment statusStep 04 · Deployment status
Watch the queued run progress
Queued, running, and completed states are visible before leaderboard updates are accepted.
- Creator dashboardStep 05 · Creator dashboard
Review creator payout state
Payable, accruing, and processed totals use the same seed values as the platform dashboard.
Revenue share
Build an environment, keep the larger share.
Base share, verified bonus, scale bonus, and payout threshold are the same constants the platform uses to settle creators. The math you see here is the math you get paid on.
creator share on approved community environments
bonus when the submission passes verified-environment checks
10,000 monthly downloads earn the scale bonus
settlements accrue until this payout threshold is met