Workspace Guardian

> Enforce workspace discipline — consistent structure, naming, memory lifecycle, and safety boundaries.

Quick Reference

workspace/
├── projects/   YYYYNNNN_name     — source code only
├── knowledge/  topics|articles|research|assets — knowledge files only
├── output/     wechat|docs|slides|preview — final deliverables
├── memory/     YYYY-MM-DD.md → archive/ (14d+) — never deleted
├── logs/       run-time logs
├── .temp/      temporary files — delete after use
└── slides/     presentations

Core Rules (6 Tenets)

1. System Files Stay Outside

No workspace files in OpenClaw's own directories (~/.openclaw/ except workspace/, ~/.openclaw/canvas/, etc.).

2. Workspace Is the Only Writable Zone

All AI-generated files → workspace/ subtree only. Never write to Desktop/, Downloads/, ~/, or system paths.

3. Scattered Files → Immediate Redirect

Any file not in its designated directory → move to correct location, not delete.

4. One Config Backup Only

Configuration or .json-based projects keep one archived/expired backup, not piles of timestamps.

5. Temp Files → Never Overnight

.temp/ files: delete after task completion. >7 days stale → cleanup on next session start.

6. Skills Source Separation

ClawHub-installed skills in skills/. User-built local skills also in skills/. No double installation.

File Routing Rules

Naming Standards

Authorization Levels

Red Lines

• No private data leaks
• No destructive commands without explicit confirmation
• No external sends without authorization
• No safety settings modification

Scripts

• scripts/workspace-cleanup.py — Scan and clean temp/stale files
• scripts/validate-workspace.py — Validate workspace structure against these rules

References

• references/naming-conventions.md — Detailed naming rules
• references/memory-tiering.md — Memory lifecycle management
• references/safety-boundaries.md — Detailed safety rules