integration-protocollisted

# Integration Protocol — 7 steps to wire the pre-existing > The default failure mode when asked to integrate is to build a new layer on top. > This protocol prevents that: observe first, recognize the invariant already present, name it, map, build minimum. ## When this applies Trigger prompts: - "connect X" - "integrate Y into Z" - "unify the various W" - "orchestrate" - Intuition: "too many disconnected pieces, need a coordinator" Does NOT apply to: - Single implementation tasks (just do it) - Local refactor (no cross-system connection) - Quick fix (the protocol is overhead) --- ## The 7 phases ### 1. OBSERVE the existing landscape Before building anything, read: - All relevant directories (recursive `ls` on skills/, hooks/, memory/, kernels/) - All index files (CLAUDE.md, README, MEMORY.md, hooks.json, settings) - The header/description of every candidate skill/hook/agent Test: if after observation I cannot name ~20 specific elements of the domain, I have not observed enough. Construction will presuppose. ### 2. RECOGNIZE the shared invariant pattern During reading, look for the structure that recurs. Test: if two or more elements have similar structure (N steps, N modes, N gates), they are probably specializations of the same neutral pattern. Example: 6 steps in cec + 6 modes in autologica + 4 gates in a method = there is a shared invariant. ### 3. NAME the neutral form as first-class Do not add a "new skill" on top of the existing. Name the neutral form that wa