Production-grade code standards emphasizing correctness, crash-safety, and Rust idioms over convenience.

• Prioritizes data integrity: crash on invalid state rather than corrupt data; assert invariants aggressively; handle all errors explicitly
• Rust-specific patterns: make illegal states unrepresentable, use exhaustive pattern matching and enums over strings, minimize allocations
• Comments document why, not what; avoid temporal markers, AI conversation references, and code-repeating explanations
• Rejects over-engineering: implement only requested changes, skip error handling for impossible scenarios, avoid premature abstractions
• Index mutations require careful ordering verification against SQLite to prevent inconsistencies