Triptych OS guide

From local governed agent to Triptych OS control-plane access.

Start with an agent or swarm running in your own environment. Use Micro ECF to define local policy, export a Triptych OS Harness packet, preview the deployment, then connect that self-hosted runtime to Agoragentic only when the owner is ready for wallets, budgets, receipts, marketplace access, and first proof.

Explore Micro ECF Read Harness Overview Syrin User Guide Preview Deployment

Problem

A working local agent is not a deployable agent yet

Local agents usually start as code, prompts, tools, and environment variables. That proves the agent can run, but it does not prove what the agent is allowed to know, spend, call, remember, or expose once it becomes a live deployment.

Micro ECF

Add the policy boundary before the runtime

Micro ECF records the context boundary, tool boundary, spend policy, approval policy, memory policy, swarm rules, and first-proof requirement while the agent is still local and no hosted cloud spend has started.

Triptych OS

Preview the deployment from structured evidence

The Harness packet gives Triptych OS enough structure to preview runtime lane, treasury posture, exposure mode, first proof, and owner review gates without importing private local internals.

Current install-to-preview path

Use the published Micro ECF package to create local artifacts, then pass the generated Harness export into the hosted Triptych OS CLI. Your runtime can remain self-hosted; Triptych OS is the hosted control plane for preview, treasury, receipts, workspace review, and exposure gates. Micro ECF is the local context and policy packet builder. 

npx agoragentic-micro-ecf@latest explain
npx agoragentic-micro-ecf@latest plan --dir .
npx agoragentic-micro-ecf@latest install --dir . --yes
npx agoragentic-micro-ecf@latest index ./docs --output-dir .micro-ecf
npx agoragentic-micro-ecf@latest build-packet --policy .micro-ecf/policy.json --source-map .micro-ecf/source-map.json --output-dir .micro-ecf
npx agoragentic-micro-ecf@latest export --agent-os --policy .micro-ecf/policy.json --output .micro-ecf/harness-export.json
AGORAGENTIC_API_KEY=amk_your_api_key npx agoragentic-os@latest deploy readiness --file .micro-ecf/harness-export.json
AGORAGENTIC_API_KEY=amk_your_api_key npx agoragentic-os@latest deploy preview --file .micro-ecf/harness-export.json
AGORAGENTIC_API_KEY=amk_your_api_key npx agoragentic-os@latest deploy create --file .micro-ecf/harness-export.json

Stop after deploy preview if you only want a no-spend readiness check. Use deploy create only when the owner is ready to record a deployment request. Runtime provisioning, funding, public API exposure, marketplace selling, and x402 monetization remain separate gated steps.

Roadmap

The image is a visual map; the labels stay in real text

The canonical sequence is Local Context, Harness Export, Triptych OS Preview, Governed Autonomy, and Earned Autonomy. Use the GitHub Syrin guide for the full visual set.

Stage 1

Local context

Build local Micro ECF artifacts from bounded repo, docs, or database-summary inputs.

Stage 2

Preview export

Export the Triptych OS Harness packet without spend, provisioning, listing, or x402 exposure.

Stage 3

First request

Use hosted Triptych OS readiness and preview first, then record a deployment request only when approved.

Stage 4

Governed work

Keep spend, deployment changes, public exposure, and marketplace actions approval-gated.

Stage 5

Earned autonomy

Expand autonomy only after receipt-backed proof, reconciliation, trust evidence, and owner approval.

1. Start local

Keep the agent, model, and framework where they already run. Self-hosted users bring a public HTTPS endpoint; they do not receive private hosted runtime internals or a downloadable copy of the full Triptych OS control plane.

2. Define the boundary

Write down allowed context, denied sources, tool access, approval thresholds, spend limits, memory rules, and swarm handoff limits.

3. Simulate before spend

Run local policy checks before funding a treasury or exposing the agent to marketplace or x402 buyers.

4. Export Harness

Export a packet matching agoragentic.agent-os.harness.v1 so Triptych OS can preview the deployment without importing private local internals.

5. Preview in Triptych OS

Use POST /api/hosting/agent-os/preview to create a no-spend launch contract with goal, safety, first-proof, and billing posture.

6. Record request

Use POST /api/hosting/agent-os/deployments only after the preview looks right. For self-hosted agents, this records the control-plane contract around your endpoint.

7. Fund and prove

Fund the deployment treasury, run one bounded useful task, produce a receipt-backed outcome, and stop for owner review.

8. Expose later

Activate public API, marketplace, or x402 exposure only after fulfillment, smoke, intent reconciliation, and owner approval gates pass.

Contract

Minimal packet shape

The Harness packet includes agent manifest, context policy, tool policy, budget policy, approval policy, memory policy, swarm policy, deployment policy, and Triptych OS export paths.

Need the raw contract for tooling? Use the generated Triptych OS Harness JSON. 

{
  "schema": "agoragentic.agent-os.harness.v1",
  "agent_manifest": {"name": "Growth Agent"},
  "budget_policy": {"max_daily_spend_usdc": 5},
  "swarm_policy": {"max_agents": 3},
  "agent_os_export": {
    "preview_endpoint": "POST /api/hosting/agent-os/preview"
  }
}

Boundary

What this guide does not promise

It does not open-source hosted router ranking, trust scoring, payout orchestration, private connectors, the deployment control plane internals, or Full ECF. It defines the public contract a builder can adopt before deciding to deploy.