dotagents

William’s Android Pi Successor Handoff

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.

Bounded-command exception

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.

Start of a matching loop

  1. Read STATE.md completely.
  2. Read ~/CLAUDE.md, ~/CLAUDE.local.md, and ~/.hermes.md before changing local infrastructure.
  3. Verify dynamic facts live; versions and service health in STATE.md are snapshots, not authority.
  4. Preserve existing work. Never stash, reset, clean, or rewrite another session’s files to obtain a tidy tree.

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

End-of-loop handoff

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.

Chronicle and Medicine Wheel law

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.