gm-hop

Args: one JSON object {"node":{"id":"<id>","label":"<Author - Title>","advocate":"<advocate spec>","links":[{"to":"<id>","guards":["<guard>"]}]},"surface":"<path>","session":"<SESSION_ID>","wave":"<wave>","depth":<n>,"rhetoric":""}. links is sorted lexically by to. The payload is the only graph data a hop receives: never load gm-graph.json. rhetoric, max_depth (default 6, the wave's cap) and wave (names .gm/pool/ledger-<wave>.txt) are optional; wave is required for ledger lines. Missing node, surface or session: VERDICT: NOT-APPLICABLE, no writes.

Verbs: gm §1. Code questions: codeinsight first, then codesearch literal rooted at the surface. Read only located paths.

Procedure

The orchestrator writes ledger launch and done lines (gm-orchestrate, Tick), except the hop's final done (step 7).