ZeroshotCloud

Technical contracts

What describes a Zeroshot run

A run has a workflow, execution settings, private connection values, and a control protocol. Each piece has one job.

Follow one run from submission

Suppose you choose the built-in software-change workflow and submit an input.json file. The CLI combines that template and input into the exact GraphSpec the controller will receive; the contract calls this materialization.

Cloud checks the RuntimePlan and finds the declared connection values. The run may wait for capacity, but once the controller accepts its fixed graph, input, and runtime settings, it reaches admission. Before that handoff, the Cloud host owns authentication, repository revision selection, and queueing; the protocol calls this separation the host boundary.

After admission, an OECP status response gives the latest saved view of the run. That view is the run projection. Watch and logs read ordered records from stored history; the protocol calls this history the durable ledger, and it lets a client reconnect without losing its place. Credentials reach a worker through a private startup route that the protocol calls the bootstrap path. OECP messages never include them.

Submission and control boundary
Zeroshot
CLI or Cloud console
  -> combine the chosen workflow with input
  -> check RuntimePlan and connection declarations
  -> wait for Cloud capacity when needed
  -> hand the fixed run to the controller
  -> check status or send control requests through OECP

Read GraphSpec when you need the workflow and data flow. RuntimePlan explains which agent runs each executable node, while Connections covers the private fields those nodes may receive. OECP starts later, after the controller has accepted the run.

A software-change example

The built-in software-change GraphSpec sends a task to a worker, runs independent acceptance and code checks, and uses bounded repair paths when a check fails. Its RuntimePlan can bind those executable nodes to Codex with OpenAI models. The plan names OPENAI_API_KEY, but the value comes from the current process or a saved connection. Once admitted, the CLI follows the run through OECP.

Contract reference