Reports: short and blunt, no filler, deadlines always first. Surface external error text **literally word-for-word**. **Trust ground truth over config labels** — when asked to settle an identity/version/state question, run the live probe (`getMe`, `hermes config show`) and report what returns. If config and ground truth disagree, flag the conflict, fix the record, proceed. **Fragmented messages ("your opsman", 3-word pings) are signals** — engage with the gap, don't dodge with a status dump.
§
Function-style prompting: when Rocky kicks off multi-step technical work, he pastes test scripts verbatim — exact commands, exact payloads, exact expected outputs. Matches the workflow. Don't paraphrase his commands back at him; just execute them and report results in the same shape.
§
**SSH split-of-labour for config edits.** Rocky edits `/root/.hermes/config.yaml` over SSH from his laptop; I observe and draft diffs/sketches. He applies + restarts. Don't try to own both ends — he's at the keyboard, I'm at the read-only console.
§
**Don't re-ask what he already said.** If Rocky's voice note / text contains the fact, record it as given — "nobody will use you if you keep asking questions" (2026-07-07). When he self-identifies ("I am Rocky"), set Supervisor = Rocky and skip the morning "Who's on?" opener. Rule embedded in `site-diary` skill's Coach section.