cascadelisted

# Cascade — Three-Level Propagation When something changes, three things happen: 1. The change matures within itself (internal) 2. The change propagates where it must (external) 3. During propagation, new possibilities emerge (emergent) ## Level 1 — Internal Cascade Before propagating, the change must mature. **Questions to ask:** - Is this a semi-duplicate of something else? → Unify or distinguish - Does it make something obsolete? → Update or remove the old - Does it open new possibilities? → Note as emergent, don't implement yet - Is a tool maturing into an entity? → Evaluate if full automation is warranted - Do existing skills/hooks need updating? → Update descriptions, triggers, evals - Is the system's self-description still correct? → Update instruction files ## Level 2 — External Cascade (binding) The change must arrive where it needs to. These are mandatory. ``` Function/skill/hook created or modified ├─ In the seed? → neutral version, zero specific references ├─ On the site? → spec to the responsible node ├─ Config files? → update references ├─ Other nodes? → message via collaboration channel ├─ Shared rules? → if applicable to all nodes ├─ Local memory? → update memory files └─ Settings? → if it's a hook, verify registration ``` **Corrections:** ``` Correction received ├─ Executable rule (when X → do Y) ├─ Local memory → update ├─ Seed kernel? → if universal ├─ Other nodes? → if cross-node └─ /auto-learn → activate ``` ## Level 3 — E