Implementation Handoff
Route approved technical work after scope, owners, credentials, and launch criteria are clear.
Implementation Handoff
Use this page after a workspace owner has approved the feature scope, credential owner, and launch path. It is a router, not a standalone developer manual: use it to choose the right implementation surface, then rely on machine-readable contracts and package-owned references for exact details.
Choose An Entry Point
Authentication & Keys
Confirm key type, allowed origin, credential owner, and server boundary.
SDK
Use the TypeScript SDK when app code needs typed workspace reads, writes, or workflows.
API
Use OpenAPI and direct HTTP only when the SDK is not the right fit.
MCP
Connect approved AI clients when the owner has granted workspace scope and credentials.
Webhooks
Receive events after an owner, retry path, and observability plan are assigned.
Handoff Order
- Confirm enabled features in Feature Planning.
- Confirm key ownership, allowed origins, webhook ownership, and AI-agent scope in Integrations & Keys.
- Confirm launch criteria in Launch Readiness.
- Choose the surface below at a routing level.
- Return to Launch Readiness before production exposure.
Surface Selection
| Need | Route to | Keep out of this page |
|---|---|---|
| browser reads or product UI | SDK after Publishable Key and allowed origins are approved | SDK import tables or generated type details |
| privileged server work | server-side SDK or API after Secret Key ownership is assigned | endpoint-by-endpoint reference claims |
| shell-capable coding agent | CLI or package-owned agent setup notes after scope is approved | local automation recipes that bypass owner review |
| hosted or shell-less AI client | MCP after workspace scope and credential boundaries are approved | treating every automation task as MCP by default |
| event processing | webhooks after owner, retry, and observability responsibilities are assigned | provider-specific delivery guarantees not verified here |
Do not implement against a workspace before the workspace owner approves scope, credential ownership, and launch readiness criteria.
Next Actions
- New integration: open Authentication & Keys.
- App or product surface: open SDK or API based on the owner-approved implementation plan.
- Automation or AI handoff: open Integrations & Keys first, then route to CLI/package notes or MCP only when that surface matches the approved client.