System Map
What Manowar Owns
The Execution Unit Is An Agent
Manowar’s core distinction is structural: a subagent is not a raw model call wrapped in a bigger prompt.task, delegate, and swarm_delegate target a registered Compose agent by agentWallet. The runtime checks the registry, loads the agent card, resolves the card model, applies that agent’s memory and tool scope, and executes it as its own participant.
Raw model calls still exist, but they live behind models_call. That split matters. A model call spends tokens on a provider model. An agent call invokes an addressable agent asset with identity, creator, card metadata, tools, memory scope, reputation surface, and payment boundaries.
The contract layer makes the same boundary economic. AgentFactory agents carry creator-set license prices and license supply. Manowar workflows nest agents, compute workflow price from nested agent prices, and distribute creator payment proportionally when the workflow is minted. Lease contracts split usage fees between workflow creators and leasers during lease periods, and royalty contracts add EIP-2981-style royalty calculation for secondary-market flows.
So the important claim is not “multi-agent orchestration.” Many systems have that. Manowar is global agent-to-agent execution where the callable unit is a deployed, stateful, ownable agent. That is the substrate for agent-as-an-asset: when another agent or workflow includes or invokes your agent, the system can attribute the work to your agent instead of hiding it inside an anonymous prompt chain.
Positioning
Different agent frameworks put the control plane in different places:
The clean comparison is architectural. LangGraph is a graph runtime. OpenAI Agents SDK is a lightweight code SDK. ADK is an app framework. OpenClaw is a local gateway. Manowar is the Compose runtime for paid, registered, memory-backed agents that can call each other globally.