I frame a task, its context and acceptance criteria before allocating execution. Studio prepares a reviewable mission package, not an unrestricted command.
ACP StudioA task. Clear roles. A verified result.
I design a local orchestration environment around mission scope, agent roles, tools, context and verification. Studio prototypes and tests are documented; real execution remains bounded and experimental.
Explore the case study ↓The concept separates planning, implementation and verification roles. Harnesses and tools are selected within an explicit scope rather than given universal permission.
The model shows a context packet and distinct tools: specification, code workspace and test bench. It exposes no private configuration or provider identity.
State, integrity and acceptance checks keep a reported success separate from a verified result. Human approval remains a decision boundary.
Local Studio interfaces, state machines and synthetic tests are documented. Real pilots have narrow scopes and unresolved limits; this is not a generally autonomous multi-agent service.
The result and the next step.
A documented local architecture with state machines, interfaces and synthetic test evidence. Pilot limitations are retained; the scene does not imply a fully autonomous service.