02 / Follow the boundaries
Every layer has a job. And a limit. 01 A place for the idea Implemented source 02 Know who is asking Activation gated 03 Agree on the spending Activation gated 04 Give the agent a clear job Activation gated 05 Keep actions within reach, not beyond it Implemented source 06 Keep the thread when a call breaks Activation gated
workspace
Next.js · React · portable memory Edit five context files and carry your brief between tools. Device recovery is optional, plaintext and browser-local.
Source: app/platform/studio.tsx
Explore this layer ↗ A prompt describes the job. It never grants identity, spending authority or tool permissions.
03 / Take the next step
Your build plan: shape a project. Download architecture .md ↓ This selection stays in the current tab. Download the plan to keep it. Curator
Build in this order 01 · Prove the foundation Run the existing identity, budget, ownership and recovery tests. Review migrations and expiry operations before activation.
02 · Validate one real run Use a designated pilot account and an approved rate card. Verify provider usage, settlement and lost-response recovery end to end.
03 · Add capabilities deliberately Measure brief quality against a reviewed evaluation set before expanding access.
04 · Open a managed pilot Require tenant-isolation evidence, support and deletion procedures, payment-backed grants and observable spend limits before wider access.
What must be true before launch A gated request cannot call a model before admission. An interrupted request retains its run reference and cannot silently retry. Use verified tenant identity, not tenant IDs supplied by the model. Reserve and claim a bounded budget before inference; reconcile uncertain usage. Recovery reads do not create a new model attempt. Do not store prompts, memory or generated content in operational telemetry. A map, not a launch announcement. The workbench is a deterministic planner: no model calls, account connections or infrastructure changes. “Implemented” describes source in this branch, not a live verification. Cloud inference remains activation-gated. Research and delivery roles are proposed extensions, not hosted services.
Inspect the developer interfaces ↗