This skill belongs to agent work on William’s Android machine, relationally named Ilex. Its purpose is small: let the next agent begin from witnessed reality instead of rediscovering the device or trusting stale assumptions.
A routine shell or Git command with explicit scope and a clear postcondition is not a matching loop. Do not read STATE.md, survey unrelated repositories, or create a successor entry for it. Follow ~/CLAUDE.local.md literal-command mode: preserve the named work, report a blocker plainly, and stop rather than escalating into an improvised recovery procedure.
STATE.md completely.~/CLAUDE.md, ~/CLAUDE.local.md, and ~/.hermes.md before changing local infrastructure.STATE.md are snapshots, not authority.Useful live checks:
~/bin/gmusic-service-mode.sh status
~/bin/ensure-miadi-workbench.sh status
git -C ~/repos/jgwill/medicine-wheel status --short --branch
curl -fsS http://127.0.0.1:8040/api/health
curl -fsS http://127.0.0.1:8031/api/health
Update STATE.md with one dated entry containing only what changes the successor’s decisions:
Do not store credentials, tokens, private addresses, device serials, transcript content unrelated to the work, or giant command dumps.
/data/data/com.termux/files/srv/miadi/episodes/miadi-chronicle/http://127.0.0.1:8040http://127.0.0.1:8031AGENTS.md: work on main, fetch/reconcile first, preserve dirty concurrent work, and never force-push..mw-registration.json receipt agrees.land, tenant=human, service=knowledge; never invent a new NodeType.@medicine-wheel/infra, but preserve Android métis. Ilex uses Termux and tmux watchdogs, not systemd; never hide that difference merely to satisfy a schema.When a loop belongs to an existing episode, leave its success/failure and provenance inside that episode and push the Chronicle when explicitly requested. Append to an existing agent work log rather than replacing earlier testimony.