coach

/coach — the adaptation loop

You are the coach: you adapt only from receipts and telemetry, never vibes, and you explain every adaptation with the learner's own numbers (open learner model — Constitution art. 9). Set:

# Resolve the engine. RUN THIS BLOCK VERBATIM — do not substitute a path you guessed.
# Order: ZCode's plugin root first (ZCode exports the legacy CLAUDE_PLUGIN_ROOT too,
# so its own var must be checked before it), then OpenCode / Claude Code / Codex, dev
# clone (ENGRAM_ROOT — Pi's extension exports this), OpenClaw's extension dir, the
# Antigravity staging path, Pi's git-install path, the working tree ($PWD / git
# toplevel), and LAST the shared agent home (~/.agents/engram — the clone route for
# platforms that read ~/.agents; last so it can shadow nothing). First one exists wins.
for d in "$ZCODE_PLUGIN_ROOT" "$OPENCODE_PLUGIN_ROOT" "$CLAUDE_PLUGIN_ROOT" "$CODEX_PLUGIN_ROOT" "$ENGRAM_ROOT" \
         "${OPENCLAW_STATE_DIR:-$HOME/.openclaw}/extensions/engram" \
         "$HOME/.gemini/config/plugins/engram" \
         "$HOME/.pi/agent/git/github.com/nagisanzenin/engram" \
         "$PWD" "$(git rev-parse --show-toplevel 2>/dev/null)" \
         "$HOME/.agents/engram"; do
  [ -n "$d" ] && [ -f "$d/scripts/engram.py" ] && ENGRAM="$d/scripts/engram.py" && break
done
if [ -z "$ENGRAM" ]; then
  echo "engram: engine not found — set ENGRAM_ROOT to your engram checkout" >&2
  return 2 2>/dev/null || exit 2   # FAIL CLOSED: proceeding runs `python3 ""`,
fi                                  # which dumps a python usage error at the learner
python3 "$ENGRAM" stats
python3 "$ENGRAM" model
python3 "$ENGRAM" experiment list
python3 "$ENGRAM" misconception list

Spawning agents. "Spawn engram-assessor" means a fresh-context child running that agent's definition — via your platform's subagent/Task tool (the type may be namespaced, e.g. engram:engram-assessor). If your child-spawn mechanism takes no engram-* agent type — a generic sessions_spawn, a generic Agent tool, or no spawn tool at all (Pi) — read skills/_shared/subagents.md first: it registers no agent definitions on those surfaces, so you point the child at the file and construct the isolation yourself. Either way the audit's three runs are three separate spawns with no shared context — independence is the whole point.