Docker sandbox runtime and Open Knowledge Format memory base

Why

EmiClaw requires an isolated, non-privileged execution environment to operate safely without risking root access or unconstrained filesystem operations on the studio VPS.

Problem

An unconstrained host agent could accidentally mutate host configurations, overwrite system dependencies, or persist credentials insecurely in environment variables.

Approach

Constructed a hardened Docker container sandbox (nanoclaw-agent-v2) running as an unprivileged node user, and organized working memory using the Open Knowledge Format (OKF 0.1).

Implementation

• Built isolated Docker container with strict directory bind mounts.
• Structured working knowledge base under /home/deploy/nanoclaw/groups/emiclaw/memory/.
• Configured credentials in opencode.json with restricted filesystem permissions (chmod 600).
• Configured host service via systemd user daemon (nanoclaw.service).

Verification

• Verified container starts with unprivileged UID.
• Confirmed memory usage calibrated at ~1.5 GiB used with 2.5 GiB free headroom on 4 GB VPS.

Result

EmiClaw operates in an isolated sandbox with structured long-term memory.