CLAWSOLATOR / ENGINEERING JOURNAL

Clawsolator Alpha, Planned Beta, Licensing and Framework Roadmap

Alpha today. Beta planned. License under review. A transparent technical roadmap rather than a premature production-readiness promise.

XERXES SI editorial analysis · Alpha-stage product · Updated November 1, 2026

RELEASE TRANSPARENCY

What exists today—and what is planned

Current: XMAN alpha

Source-reviewed agent-management workflows, bounded special requests, rootless Podman integration, approval handling and action journals. Deployment-specific behavior must be tested.

Read more →

Planned: Beta

Beta release is the development objective; publication date is not committed. The code-release license remains under deliberation.

Future: Security Officer

Separate plugin preflight inspection, runtime observation, and potentially its own rootless daemon. Not a current shipping feature.

Read more →

Public availability: The current website and source package are alpha-stage artifacts. A final public source-code release or selected license is not asserted here.

RESEARCH / PRACTICE

Framework-neutral by intention

Clawsolator uses OpenClaw as the current practical foundation, but the governance objective is not to depend permanently on any one framework or plugin ecosystem. Future Hermes integration, OpenShell enforcement, other compatible runtimes, or in-house replacement components are possible directions—not verified shipping integrations. Engineering trade-offs must be evaluated before supporting or replacing an upstream subsystem.

The distinction matters for organizations evaluating technical longevity: the management and approval model should survive changes in the agent runtime when possible, subject to adapter engineering and real compatibility testing.

RESEARCH / PRACTICE

What the name means

Clawsolator = Claw + Isolator. “Claw” acknowledges the current OpenClaw integration; “Isolator” expresses the trust-boundary principle. This is a product identity, not a claim that the system magically blocks every exploit.

Nothing is “unhackable.” The responsible approach is layered controls, measurable limitations, rapid patching, continuous assessment, and recovery. We respect OSSTMM as a security testing methodology; Clawsolator currently claims no OSSTMM certification or other independent certification. ISECOM OSSTMM methodology ↗

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.