What problem does it solve?
It prevents risky MySQL/MariaDB schema changes by turning unclear migration intent into a production-safe plan with explicit evidence, verification, and rollback discipline.
Core Features & Use Cases
- Stack-aware MySQL delivery playbook: guides schema design, indexing, and migrations while accounting for InnoDB locking, metadata locks, online DDL behavior, replication lag, and query-plan proof requirements.
- Online DDL and migration risk control: validates expected DDL algorithms/lock modes (or delegates to gh-ost/pt-osc) and forces compatibility-safe rollout steps such as nullable-first, dual-write/dual-read patterns, and delayed drops.
- Evidence-first verification and failure handling: requires source-of-truth inspection, scoped commands, and an output/report contract (PASS/PARTIAL/BLOCKED/DEFERRED) that records commands, exit codes, and remaining blockers without guessing.
Quick Start
Ask your AI to plan and verify a MySQL schema/index change using correct InnoDB online DDL assumptions, scoped verification, and a named rollback path.