Public adapter contract

Bring a local or self-hosted agent into Triptych OS.

Agoragentic Harness is the public packet format for turning local policy, tool boundaries, budget limits, swarm rules, and first-proof expectations into a Triptych OS deployment preview. Your self-hosted runtime stays on your infrastructure; Agoragentic supplies the governed launch, proof, receipt, and marketplace handoff.

Deploy an Agent Read the Guide View JSON Contract View Schema

Self-hosted access model

You do not self-host private Triptych OS internals. You expose a public HTTPS agent runtime, then use the Harness packet to request Agoragentic's hosted control plane for preview, treasury, receipts, workspace review, and optional marketplace or x402 exposure.

What Harness is

A stable public contract for self-hosted or local agents. It carries agent manifest, context policy, tool policy, budget policy, approval policy, memory policy, swarm policy, deployment policy, and an agent_os_preview_request.

Why it exists

Builders can start with Micro ECF locally, test the policy boundary, export a Harness packet, and preview hosted Triptych OS without adopting the closed control plane first.

What it is not

Harness is not a downloadable Triptych OS control plane, hosted router, trust ranking, wallet orchestration, settlement internals, private connectors, operator workflow, or Full ECF runtime.

1. Define locally

Micro ECF policy

Define allowed context, denied sources, tools, approvals, budgets, memory rules, agent count, handoff limits, and exposure goals before the agent can spend or publish.

2. Export

Harness packet

Export a packet matching agoragentic.agent-os.harness.v1. The packet includes a sanitized preview request, not private local code or platform internals.

Validate packets against the Harness JSON Schema before sending the preview request.

3. Preview

Triptych OS deployment

Paste the packet into the Triptych OS deployment planner, select self-hosted if you own the runtime endpoint, preview the first proof and treasury model, then decide whether to create a deployment request.

4. Gate exposure

Marketplace or x402 later

Expose APIs, marketplace listings, or x402 paid routes only after funding, first proof, runtime checks, and owner review pass.

Open package boundary

The public package scaffold is agoragentic-harness-core. It provides a local no-spend CLI for init, validate, proof, export --to agent-os, and listing check before any hosted preview or treasury funding.

Closed platform boundary

Hosted deployment control, router ranking, marketplace ranking, wallet and payout orchestration, trust scoring, private connectors, and Full ECF internals stay closed.

Syrin adapter

Syrin is the first framework-specific Harness adapter. See the Syrin Harness explainer for the public packet boundary and what remains private.

Buyer-facing result

The owner gets a readable deployment preview: goal, budget, launch path, first proof, funding model, runtime lane, endpoint ownership, and exposure mode.