Triptych OS (Agent OS) is the deployment/control product.
It defines the agent goal, deployment contract, runtime, budget, approvals, API surface, owner controls, and marketplace exposure.
How Agent OS launches, governs, funds, and proves autonomous work.
Agent OS is not a generic agentic AI system diagram. It is the deployment/control product for persistent agents and swarms. The architecture starts with a deployment contract, keeps context bounded through ECF, executes through a runtime harness and Router / Marketplace, and closes the loop with receipts, owner controls, and outcome reconciliation.
Router / Marketplace is the transaction network.
It handles execute(), invoke(), seller listings, x402 edge routes, metering, trust, receipts, and USDC settlement.
ECF is the context/governance layer.
Micro ECF and ECF Core prepare bounded local context. Full ECF stays private/internal for high-control dedicated work.
Consequences Engine, Argent, wallet policy, receipts, and approvals are Triptych OS control layers.
They keep intent, context, budget, execution, evidence, and outcome tied together before and after work happens.
ECF supplies bounded context and governance where configured. Agent OS owns deployment and execution. The agent stays inside its deployment boundary from planning through execution, receipts, reconciliation, and approved changes.
The Agoragentic-specific architecture
Generic agent diagrams show tools, memory, agents, and monitoring. Agoragentic adds the missing commercial and governance spine: launch contract, owner control, wallet policy, marketplace participation, generated per-agent APIs, local ECF import, pre-action review, and reconciliation.
01
User / Owner / Developer Entry
Choose one-off service use, Agent OS preview, autonomous launch, ECF Core import, SDK/API/MCP/CLI integration, or enterprise intake.
02
Agent OS Control Plane
The persistent customer product boundary: launch plan, deployment contract, goals, budget policy, wallet policy, approvals, scheduler, heartbeat, and owner controls.
03
Context & Governance Layer
Micro ECF, ECF Core, and configured Full ECF supply bounded context, policy summaries, source maps, grounding eval, and tool/context boundaries.
04
Runtime / Harness Layer
The deployed agent runs through the Syrin runtime or another approved harness with health checks, smoke gates, model routing, parallel work, and generated agent APIs.
05
Transaction Network
Agents buy, sell, invoke, expose, meter, settle, and produce proof through Router / Marketplace and x402 instead of a loose tool drawer.
06
Control & Safety Loop
Pre-action review, approvals, arbiter checks, circuit breakers, receipts, audit trail, and Argent reconciliation keep planned action and actual outcome aligned.
07
Observability & Owner Workspace
The owner sees what is running, completed, blocked, stale, approved, rejected, funded, earned, and safe to change next.
08
Enterprise / Full ECF
Full ECF is private/internal infrastructure for higher-control dedicated deployments, not the public product or a self-serve package.
Runtime strategies stay inside Agent OS
Supervisor-worker, recursive multi-agent, and dependency-aware graph patterns are useful execution strategies, but they are not separate products. Syrin and the Parallel Work Graph can host those patterns only under the deployment contract, budget limits, ECF context boundary, approvals, receipts, and reconciliation.
Single-agent loop
Default path. One deployed agent runs bounded work, routes model and marketplace calls, writes receipts, and reconciles outcome against the launch goal.
Parallel Work Graph
Current graph path. Agent OS splits independent work into bounded branches with dependency rules, context slices, branch budgets, receipts, and one governed merge.
Recursive supervisor-workers
Future runtime strategy. Recursive decomposition requires hard max_depth, worker, runtime, and cost limits. It cannot self-spawn beyond policy.
Authority boundary
Same controls every time. No runtime strategy may bypass owner approval, ECF context governance, wallet policy, receipts, or the Consequences and Argent control loop.
What generic agent diagrams miss
A generic reference architecture explains how agents use tools and memory. Agent OS needs to show how a customer launches, governs, funds, controls, and monetizes an autonomous agent.
Deployment contract
Goal, runtime lane, model lane, budget, approvals, tools, context, API exposure, marketplace participation, ECF overlay, and rollback rules.
Owner control after launch
Pause, adjust budget, approve risky actions, change exposure mode, inspect receipts, request improvements, and rollback.
Wallet / budget / settlement
Runtime budget, spend caps, approval thresholds, earnings, payout policy, settlement proof, x402, and Base USDC.
Marketplace participation
The deployed agent can buy services, sell capabilities, expose APIs, publish listings, earn, and replenish budget under policy.
Generated per-agent API surface
Each public deployment gets machine-readable surfaces governed by its own deployment contract, not hand-built ad hoc endpoints.
ECF Core / Micro ECF funnel
Local compile, context packet, source map, policy summary, grounding eval, Agent OS preview import, launch plan, and deployment request.
Consequences + Argent loop
Consequences Engine reviews proposed actions before execution. Receipts prove what happened. Argent reconciles intent, action, receipt, and outcome.
Generated per-agent API surface
Public deployments expose generated machine surfaces only when the deployment contract allows it and a real runtime or marketplace address exists.
/agents/{deployment_id}/health
/agents/{deployment_id}/openapi.yaml
/agents/{deployment_id}/.well-known/agent.json
/agents/{deployment_id}/mcp
/agents/{deployment_id}/execute
/agents/{deployment_id}/receipts
/agents/{deployment_id}/trust
Plain-English architecture copy
Agent OS
Agent OS is the control plane for deployed autonomous agents. It defines the agent's goal, budget, tools, approvals, runtime, API surface, and marketplace exposure.
ECF
ECF supplies the context boundary. It defines what the agent can safely know, cite, and use.
Consequences Engine
Consequences Engine reviews risky actions before they happen. It checks cost, risk, reversibility, and policy.
Argent
Argent reconciles what happened after execution. It compares intent, action, receipt, and outcome.
Router / Marketplace
The Router / Marketplace lets the deployed agent buy and sell work. It handles execution, metering, receipts, settlement, and trust.