Prompt, invoke, inspect
Use a Monaco-backed request editor to create a real run for the selected workspace and inspect the structured control-plane response.
Plan-limit checkpoint
Before you create a fresh run, confirm that the current workspace plan still has room for the demo or operator flow you are about to exercise. This keeps the run path aligned with Week 6 usage metering and Week 7 billing review.
Conservative gating is still manual here: use Usage to inspect current pressure, then use Settings if the workspace needs a plan or billing follow-up before more traffic is sent through the control plane.
Onboarding first demo
This Playground session is part of the onboarding path—submit the first `POST /api/v1/runs` request, capture the `run_id`/`trace_id`, then confirm the signal in usage and record evidence in verification.
The evidence lane is manual: run in Playground, verify the usage trace, then attach evidence links.
Request
Ready for first demo run
Onboarding first demo
This workspace was sent here to create the first real run. Keep the payload simple, confirm the run queues successfully, then carry the returned ids into verification or API key follow-up.
Preflight reminder
Before you invoke a run, reconfirm key scope, plan boundary, usage pressure, and any manual billing review that keeps delivery approved. This check is still a human step; there is no automated block in place yet.
First-run tip
Keep `input.kind` as `user_instruction` for onboarding. You can adjust `entry_agent_id`, labels, and context metadata, but the request must still match `POST /api/v1/runs`.
Onboarding handoff
Use this surface to create or confirm the first successful demo run, then capture evidence.
Current blockers
Baseline bootstrap is not complete yet.
Service account is still missing.
API key is still missing.
First-demo recovery
Recover from failed/demo-in-progress states and keep evidence flowing.
No demo run yet. Submit the payload above and keep this lane ready for instant verification handoff.
Audit export continuity
After the first demo run, reopen the Latest export receipt from /settings?intent=upgrade so the filename, filters, and SHA-256 stay chained through verification and go-live notes before you return to the admin or alerts lane.
Navigation-only manual relay: these actions preserve workspace context but do not automatically attach the audit export or resolve rollout steps for you.
Response
What to look for
A successful first-run response returns `run_id`, `trace_id`, `status`, and `workflow_status`. Use those ids for logs, replay, and verification follow-up.
Supported endpoints
POST /api/v1/runs
GET /api/v1/runs/{run_id}
GET /api/v1/runs/{run_id}/graph