OpenClaw
Outer shell, operator-facing access point, monitoring surface, and workflow discipline layer.
The working pattern for verification, incident handling, and use-case execution through the operator shell.
Outer shell, operator-facing access point, monitoring surface, and workflow discipline layer.
Internal routing and compression layer where applicable.
Deterministic authority: solver-backed, benchmark-backed, script-backed correctness.
Working rule: OpenClaw makes Project Phoenix accessible; Project Phoenix makes OpenClaw outputs trustworthy.
| Step | Command | Purpose |
|---|---|---|
| 1 | openclaw --profile ollama-local gateway run --port 19001 --force | Bring up the live gateway in a separate terminal. |
| 2 | scripts/check_openclaw_hardening.sh | Verify endpoints, thresholds, screenshots, and incidents from one gate. |
| 3 | scripts/check_openclaw_hardening.sh --record | Record a milestone or audit run when needed. |
| 4 | scripts/check_openclaw_hardening.sh --skip-live | Artifact-only validation when the gateway is intentionally offline. |
Record the issue with screenshots or trace artifacts and create an incident packet with strict required fields.
Fix the actual problem in code or configuration while keeping the incident folder as the operator unit of work.
Write the resolution, validate the folder, and confirm the index stays internally consistent.
Resolved examples already exist in the current incident index, including the original gateway outage and the run-trace static-data bug.
Sandboxed localhost checks do not always see the live gateway even when the foreground gateway is healthy. The reliable path is documented and operational: run the full hardening gate from the live shell environment when needed.