Ops Lab Playbook: Planner Studio
Last updated: 2026-03-08
1. Purpose and when to use this
Use Planner Studio to discover opportunities, review generated proposals, and approve actions for execution.
2. User roles and auth modes
JWT creator: discovery and proposal listing.JWT operator: proposal approval actions.
3. Prerequisites checklist
- Primer completed: Onboarding and API Primer
HANDLEexists and includes proposal history or enabled discovery.JWT_TOKENfrom creator/operator identity.
4. UI onboarding flow
- Open
https://app.10x.in/creator/planner. - Run discovery for target categories.
- Review proposal list and status.
- Approve a proposal as operator.
5. API workflow map
PL-01:POST /v2/handles/{handle}/agent/discover(JWT creator)PL-02:GET /v2/handles/{handle}/agent/proposals(JWT creator)PL-03:POST /v2/handles/{handle}/agent/proposals/{proposalId}/approve(JWT operator)
6. cURL examples
Set module variables:
export PROPOSAL_ID="proposal-1"
PL-01 Discover opportunities
curl -sS -X POST "${API_BASE}/v2/handles/${HANDLE}/agent/discover" \
-H "authorization: Bearer ${JWT_TOKEN}" \
-H 'content-type: application/json' \
-d '{"include":["catalog","coverage","backlog"]}'
PL-02 List proposals
curl -sS "${API_BASE}/v2/handles/${HANDLE}/agent/proposals" \
-H "authorization: Bearer ${JWT_TOKEN}"
PL-03 Approve proposal
curl -sS -X POST "${API_BASE}/v2/handles/${HANDLE}/agent/proposals/${PROPOSAL_ID}/approve" \
-H "authorization: Bearer ${JWT_TOKEN}" \
-H 'content-type: application/json' \
-d '{"note":"approve via creator suite"}'
7. Expected success outputs and verification checks
- Discovery returns coverage and catalog hints.
- Proposal list contains deterministic rows for handle.
- Approval response confirms status transition to approved.
8. Failure modes and remediation
403 insufficient_roleon approval:- Remediation: use operator-level JWT.
- Empty proposal list after discovery:
- Remediation: rerun discover with broader include filters.
401JWT issues:- Remediation: refresh login token and retry.
9. Async behavior notes
Planner actions are synchronous request/response paths (SYNC) in the scenario contract.