CLAWSOLATOR ALPHABeta release planned · License under considerationRead what is verified

XERXES SI · FRAMEWORK-INDEPENDENT STRATEGY

OpenClaw is the beginning. Governance is the product.

OpenClaw offered a mature ecosystem and useful plugins. Clawsolator is being designed so no single upstream framework, service or plugin can dictate its future.

Software status: Alpha · Beta planned soon · Public license under deliberation

Why start with OpenClaw?

OpenClaw has a working agent framework, connectors, skills and a broad operational vocabulary. Integrating it first can reduce duplicated development. It also exposes well-understood risks around tool permissions, gateway policy, sandbox configuration, skills supply chains and delegated execution. Clawsolator's near-term alpha should be evaluated as an OpenClaw-oriented management layer, not an already validated universal adapter.

Use what works

Reuse mature gateways, frameworks, skills and proven runtimes instead of rebuilding them for appearance's sake.

Keep authority separate

Place sensitive host actions in external, reviewable, bounded workflows. The model requests; an authorized control plane decides.

Preserve the ability to replace

Define adapter contracts, event schemas and audits that allow migration when an upstream project becomes unsuitable.

Planned: other agent frameworks and execution backends

Hermes Agent and other compatible frameworks are candidates for adapters. An OpenShell-backed isolation pathway is another proposed complementary integration. Neither is presented as a shipped, end-to-end verified integration today. Where an upstream component lacks a required security or management capability, XERXES SI may develop its own implementation.

Adapter contract

Agent identity, gateway discovery, lifecycle, permissions and useful tool events.

Independent manager

Approval queues, resource budgets, operator identity, durable requests and recovered states.

Evidence parity

Repeatable test suite and correlated logs before a framework is declared supported.

What success would prove

Run the same approved work against two different harnesses without giving either agent unrestricted host privileges; show auditable decisions, restart recovery, bounded resources and equivalent action results. Publish failures as well as passes. Until these integration tests exist, framework independence is an architecture goal rather than an independently validated guarantee.

Why the name? Clawsolator combines Claw and Isolator: a reminder that useful autonomy should live inside enforceable boundaries, not be excused from them.

CANONICAL TRUST BOUNDARY

Agents request. XMAN decides. Operators authorize exceptional host work.

Each registered agent uses the authenticated requester API through the trusted Gateway bridge. The XMAN management daemon governs policy, resource admission and durable outcomes through its private Unix-socket interface. The operator API is separate; the master coordinates but does not become the operator. The future SysOp and Security Officer daemons would be separate, permissioned services, not current Alpha functionality.