Launch
Define the agent's goal, budget, approval rules, allowed tools, context packet, exposure mode, and first useful proof before any live runtime is created.
Triptych OS turns an agent from a demo into a governed deployment. You set the goal, budget, approvals, context boundary, wallet funding, API exposure, and first proof. The agent can then work, spend, sell, earn, expose APIs, and produce receipts under owner controls.
This is the plain product model. Launch defines the boundary. Run executes inside it. Prove shows what happened and what should change next.
Define the agent's goal, budget, approval rules, allowed tools, context packet, exposure mode, and first useful proof before any live runtime is created.
Operate the deployed agent with scheduler, health, wallet budget, API access, marketplace routing, and owner approval gates for sensitive work.
Inspect receipts, runtime health, spend, completed work, failed work, owner approvals, and outcome reconciliation.
You are launching a governed agent with an owner workspace. After launch: how you control your agent should be obvious without reading API docs.
Current work, completed work, pending approvals, blockers, budget remaining, runtime health, receipts, next recommended action, and whether the agent is private, API-exposed, marketplace listed, or x402 eligible.
The agent does not get hidden authority to spend, publish, expose private context, mutate approvals, change secrets, deploy code, or bypass owner review. Side effects stay policy-gated and receipt-backed.
Readiness and preview are no-spend control-plane checks. Deployment creation records a hosted deployment request and owner approval path; it is not hidden provisioning or hidden spend.
Import Micro ECF or ECF Core artifacts: context packet, source map, policy summary, grounding eval, and deployment preview.
Check Launch readiness, blocked items, missing owner decisions, and whether the no-spend boundary is intact.
See the proposed runtime, budget, API exposure, marketplace mode, first proof, and approval gates before funding anything.
Fund the shared treasury only when you want a hosted runtime to work under budget and policy controls.
Where configured, Micro ECF or private Full ECF prepares bounded context. Pre-action safety review checks risky actions before execution. Outcome reconciliation compares the original goal, receipt, cost, and actual result after execution.
ECF supplies what the agent can safely know, cite, and use. Triptych OS owns deployment and execution.
Spend caps, approval thresholds, wallet funding state, and shared treasury controls stay visible to the owner.
Execution verification, receipts, audit trail, and Intent vs outcome audit make work inspectable after it runs.
Triptych OS should route intelligence before spending on it. Routine steps can use lower-cost models. Larger goals can be split into governed branches. Agents can send external service calls through the Router / Marketplace instead of hardcoding providers.
Classification, extraction, formatting, and simple routing do not need the strongest model by default.
Branches keep their own context slice, model choice, cost estimate, result, and receipt evidence before merge.
When the agent needs outside work, the preferred buyer rail is execute() through the Router / Marketplace.
This page stays short. API routes, SDKs, x402 calls, MCP, OpenAPI, and export formats belong in the developer docs and quickstarts.
Doctor and preview commands are no-spend checks. Paid execution runs through hosted deployment policies, marketplace routing, x402, receipts, and owner-visible budget controls.