Admin follow-up contextPlayground
You navigated here via the admin Week 8 readiness summary. Continue the targeted onboarding, billing, verification, or go-live review for this workspace, capture the outcome on that surface, then return to the filtered admin readiness view. This is navigation-only context and does not change identity, impersonate a member, or automate remediation.
Audit export continuity
Reuse the same Latest export receipt from /settings so the filename, filters, and SHA-256 stay chained from settings through verification, go-live, and back into this admin handoff. This manual evidence relay is navigation-only; open the receipt, carry the proof in the workspace surfaces, and then return here to complete the queue or readiness loop.
Current workspace: default · Requested from admin: default · Week 8 focus: Credentials
Treat this as the manual admin → workspace surface → admin loop: follow the requested surface, capture evidence or outcome notes there, then use the return link below to restore the admin context and keep the focus state aligned.
Returning keeps the same admin filter state in place so the operator can continue the governance review without rerunning the drill-down manually.
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.
Request
Ready for first demo run
Admin readiness follow-up
You arrived from the Week 8 readiness lane. This page does not automate remediation; it only helps you produce a real run, inspect the response, and gather evidence before returning to readiness review.
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
Use a narrow request that proves this workspace can queue a governed run. Keep `input.kind` as `user_instruction`, preserve `POST /api/v1/runs`, and avoid broad payload changes until the first response succeeds.
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 healthy follow-up returns `run_id`, `trace_id`, `status`, and `workflow_status`. Use those ids as concrete readiness evidence, then continue into verification or return to the admin review lane.
Supported endpoints
POST /api/v1/runs
GET /api/v1/runs/{run_id}
GET /api/v1/runs/{run_id}/graph