feat: OpenClaw as governed execution runtime in ShellForge

[jpleva91]

Summary

Position ShellForge as the governed OpenClaw runtime — "OpenClaw + AgentGuard governance + Octi Pulpo coordination." This is the stack the enterprise market is asking for per the "Scaling OpenClaw for Enterprise" article.

Architecture

shellforge run openclaw "task"
  └── OpenClaw (execution: browser, shell, files, 100+ skills)
       └── AgentGuard Kernel (semantic governance on every action)
            └── Octi Pulpo (coordination: memory, routing, signals)

Two runtime paths:

• shellforge run openclaw — lightweight, just OpenClaw + AgentGuard
• shellforge run nemoclaw — adds NVIDIA OpenShell sandbox + Nemotron local models

Why this matters now

The article "Scaling OpenClaw for Enterprise" names the exact gap ShellForge fills:

• OpenClaw has no governance → ShellForge adds AgentGuard
• NemoClaw has sandbox-only governance → ShellForge adds semantic governance
• 250K OpenClaw users need guardrails → ShellForge is the onramp

Related

• shellforge#80 (OpenClaw/NemoClaw runtime integration)
• octi-pulpo#5 (browser driver)
• agentguard#CLAW10 (CLAW-10 scorecard)