Integration with the plane is an artifact contract, not an SDK contract. You provide four inputs; the plane runs everything else. Each input is validated on ingest against the acceptance criteria below — an input that cannot pass validation never reaches execution, which is the entire point of putting the gates at the boundary.
Division of labor
| You provide | The plane runs |
|---|---|
| SOP definitions — JSON DAG artifacts | The execution engine and its full pipeline |
| Cedar policies — compliance and access rules | The Policy Gateway and runtime evaluation |
| MCP tool definitions — schemas and endpoints | The MCP sandbox orchestrator |
| LLM configuration — model selection and credentials | The reasoning path, verification, and evidence |
| The staging environment and its network posture | Everything above, inside your perimeter |
Acceptance criteria
| Input | Validated against | On failure |
|---|---|---|
| SOP | Structural rules — unique step ids, resolvable dependencies, acyclic graph, reachability — in the SOP reference ingest table | Rejected at ingest |
| SOP verification posture | Every step's verification block exists and satisfies the zero-case rule | Flagged at ingest — authoring warning |
| Cedar policy | Policy structure and resolvable references | Rejected at ingest |
| MCP tool definition | Tool schema well-formedness | Rejected at registration |
| LLM configuration | Credential validity at first use | Surfaced at the first REASONING step |
What you never provide
| Not yours | Because |
|---|---|
| Retry, escalation, and regeneration logic | Budgets are engine behavior, declared in the SOP |
| Rollback procedures | Saga compensations are engine behavior |
| Audit trail assembly | The Evidence Ledger is written by the run itself |
| Sandbox lifecycle management | The orchestrator provisions and destroys per call |
| Verifier prompts beyond the SOP's own | Verification contracts live in the SOP |
The right-hand column is the platform's value stated as a division of labor: the machinery that makes execution governable is not something you assemble, configure, or maintain — it is what the plane does with your artifacts.
Onboarding sequence
| Stage | What happens |
|---|---|
| 1 | Workflow mapping — your procedures become SOP candidates |
| 2 | Artifact ingest — SOPs, policies, tool definitions, validated per the criteria above |
| 3 | Staging pilot — the plane runs your real workflows in your environment |
| 4 | Handoff — the validated baseline becomes the production deployment unit |
The staging pilot itself is specified in the deployment model.