ripwire-handoff

# Handoff with ripwire > Nearest neighbours: > • You need to UNDERSTAND the subsystem yourself first (not brief someone else) → **ripwire-orient**. > • You need ONE symbol's full contract, not a whole-subsystem brief → **ripwire-navigate** (`--expand`). > • The recipient needs an architecture/layering read specifically → **ripwire-layers**. Trigger: you're handing a subsystem to another agent or developer and want to give them a fast, accurate brief — not a wall of source code. `<dir>` = repo root. `SUBSYSTEM` = the area in plain words (e.g. "ingest pipeline", "graph ranking", "MCP server loop"). 1. **Task-relevant symbols** — `ripwire <dir> --for="SUBSYSTEM" --top-k=20` Output: `<sigs>` ranked by relevance. The top 10 are the symbols the recipient most needs to know. Note their file paths, complexity (`cx=`), and reuse count (`in=`). 2. **Expand the key symbols** — `ripwire <dir> --expand=SYM1,SYM2,SYM3` (Pick the top 3 by rank from step 1.) Output: full bodies + callee signatures. This is the actual contract — paste it into the handoff verbatim rather than paraphrasing. **Bodies are redacted by default** — high-confidence credentials (API keys, tokens, connection strings) are masked before you see them, so pasting this straight into a handoff doc is safe as-is; pass `--no-redact` only if you deliberately need the verbatim secret (e.g. auditing the credential-handling code itself). 3. **Design rationale** — `ripwire <dir> --recall="SUBSYSTEM"` ...