m01-ownership

Rust ownership and lifetime error diagnosis through design-first questioning. Layer 1: Language Mechanics Who should own this data, and for how long? Before fixing ownership errors, understand the data's role: Before fixing an ownership error, ask: What is this data's domain role? Is the ownership design intentional? Fix symptom or redesign? When errors persist, trace to design layer: From design decisions to implementation: - Covers seven critical error codes (E0382, E0597, E0506, E0507, E0515, E0716, E0106) with root-cause questions rather than quick fixes - Guides developers to ask "who should own this data?" before applying syntax solutions, distinguishing between symptom fixes and design restructuring - Provides decision trees for choosing between move semantics, borrowing, cloning, and smart pointers (Arc, Rc, Cow) based on data role and sharing requirements - Includes escalation paths to related skills (resource management, mutability, domain modeling) when errors persist beyond a third attempt - Is it shared or exclusive? - Is it short-lived or long-lived? - Is it transformed or just read?