Human In The Loop Approval

1. Present the Action

Before executing, clearly state:

ACTION REQUIRING APPROVAL:
What: <exactly what will happen>
Where: <which platform/file/system>
Impact: <what changes>
Reversible: Yes / No / Partially

Approve? (yes/no)

2. Wait for Response

• "yes" / "go" / "approved" → proceed
• "no" / "stop" / "wait" → halt and ask what to change
• Silence / no response → do NOT proceed

3. Log the Decision

After approval or rejection, log to OpenClawData/approvals/:

[YYYY-MM-DD HH:MM] ACTION: <what>
DECISION: approved | rejected
REASON: <user's reasoning if provided>

Approval Storage

/Volumes/Expansion/CMO-10million/OpenClawData/approvals/approvals-YYYY-MM.md

One file per month, append entries.

Rules

1. When in doubt, ask — better to over-ask than to act without permission
2. Never assume approval — previous approvals don't carry forward
3. Show what will happen — the user must understand the action before approving
4. Log every decision — approvals and rejections are both valuable records
5. Irreversible actions always require approval — no exceptions
6. Batch approvals are OK — "approve all 5 posts" is valid if user reviews the list