OpenClaw First-Run Memory Setup 20260815 - Release Notes
What It Does
OpenClaw First-Run Memory Setup helps teams check whether a first-run memory plan is ready before it becomes operational. It reviews redacted notes for storage layers, provider boundaries, retention rules, health checks, rollback evidence, and review ownership, then returns a clear PASS, REVIEW, BLOCKED, or ERROR result.
The workflow is advisory, read-only, and deterministic. It gives implementation teams evidence they can preserve for review without touching private values, live systems, or configuration.
Use Cases
- Operators setting up OpenClaw memory for the first time who need a structured readiness check.
- Agent teams documenting working, session, and durable memory boundaries before rollout.
- Reviewers who need reproducible evidence for rollback, health checks, and ownership.
Requirements
- Python 3 with standard-library modules only.
- Redacted notes supplied via
--textor one explicit local notes file. - No API keys required.
- OpenClaw workspace capable of running local skill scripts.
Example Usage
python3 scripts/first_run_memory_setup.py --text "memory purpose documented; working memory path set; session memory path set; durable memory path set; retention rule agreed; promotion rule agreed; provider boundary documented; redaction check complete; health check recorded; restore point exists; rollback plan assigned; review owner named" --json
Expected output: JSON containing verdict: "PASS", matched evidence signals, and mutated_files: []. Incomplete evidence returns REVIEW; multiple risk phrases or very low evidence scores return BLOCKED.
Price
$4.99