01 / OpenClaw
Pick the right OpenClaw path.
Start with the Mac mini tutorial unless you need the broad system map or already know the specific note to open.
A cluster route for setup, architecture, scheduling, and execution notes without adding new IA noise.
Use the proven setup path for WhatsApp dispatch, Tailscale recovery, Termius fallback, and tmux continuity.
Start tutorialBroad mapUse the broad architecture map first when the runtime shape is still fuzzy.
Read the teardownSpecific noteJump to scheduling, architecture, or execution when you already know the next question.
View notesStart Here
Choose between the proven tutorial start and the broad map
Use the Mac mini tutorial for setup. Use the source-code teardown for the system map. Pick a narrower note only when you already know the next question.
This is the current proven practical start: a real OpenClaw setup tutorial with WhatsApp dispatch, Tailscale recovery, Termius fallback, and tmux continuity on a real machine.
Best when: you want a working OpenClaw tutorial, the setup order that matters, and recovery options before broader docs
Covers: Mac mini + iPhone + WhatsApp + Tailscale + Termius + tmux setup path
Start the Mac mini tutorialStart here when the runtime is still fuzzy and you need the system map before choosing a narrower path.
Best when: you want the system map before choosing setup, scheduling, architecture, or execution
Covers: the core OpenClaw parts and how they fit together
Read the teardownNext Steps
Open the specific note you need next
If setup or the system map is already clear, jump straight to scheduling, architecture, or execution.
Open heartbeat when the question is recurring checks, cron, or bounded future work. Use the template or comparison only when you need that extra detail.
Use when: recurring checks, cron, or bounded future work are the next problem
Open heartbeatRelated notes
Template
OpenClaw `HEARTBEAT.md` Example
Use this when you already know the job belongs in heartbeat and need the file-level template, quiet-hours rule, and `HEARTBEAT_OK` pattern.
Decision support
OpenClaw Cron vs Heartbeat
Use this when the real question is which scheduling mechanism fits the job without creating noise.
Start with the teardown for the big picture. Use the architecture overview, gateway, or self-modification notes when those questions come next.
Use when: you need the big-picture map before a narrower architecture note
Read the teardownRelated notes
Overview
OpenClaw Architecture Explained
Use this when you want a skimmable component view.
Gateway
OpenClaw Gateway Architecture
Go here when presence, reachability, and channel continuity are the real blocker.
Boundaries
OpenClaw Self-Modification
Open this when the real question is file-backed identity, memory, or self-editing boundaries.
Use the ACP note when setup already works and the next question is how Codex or Claude Code runs under OpenClaw control.
Use when: setup is working and you need the external-harness runtime path
Open ACP executionThe Deeper Layer
The public notes cover the frame, the setup, and the key subsystem boundaries. The Vault carries the deeper systems material behind that public path.