Run contract tests
Validate request shape, secret rejection, idempotency and SDK contract vectors before a customer environment is touched.
SIO26 · Developer Center
Turn the plan
into local code.
This workspace reads the non-authorizing Integration Studio plan from this browser session and prepares implementation guidance for local development. It generates no account secret, API credential, delegation, permit, connection or execution right.
01 · Implementation context
// Complete SIO25 Integration Studio first.
Generated code is a local implementation scaffold. Placeholder values remain explicit. SIO26 does not mint tokens, connect customer systems, install dependencies, or claim that a public hosted API is available.
02 · What happens next
Code can describe the request. Authority still has to exist outside the code.
Use shadow first
Where a real workflow is needed for evaluation, preserve the SIO23 read-only shadow boundary rather than jumping directly to execution.
Create authority explicitly
A future real workflow requires tenant-local delegation and policy configuration. Integration code cannot manufacture either.
Keep capability downstream
Permits, JIT credentials and certified execution belong after a current ActionGate decision, not inside the developer quickstart.