rails-domain-delivery

Ensure production-safe Rails delivery by keeping persistence inside ActiveRecord boundaries and generating explicit rollback plans for migrations. This requires recording scoped command outputs and query proofs as evidence rather than relying on prose.

Keep authorization and persistence inside framework-native Rails boundaries by mapping behavior to ActiveRecord models, controllers, Hotwire contracts, and service objects. This prevents hidden cross-domain side effects in lifecycle hooks and limits callback scope creep.

Structure a focused Rails slice by confining request and response boundaries to Hotwire or API contracts. Use service, form, and query objects to isolate logic, and verify the delivery slice with scoped commands before deployment.

Rollback planning for ActiveRecord transactions and jobs is supported by requiring explicit rollback paths for deploy-sensitive changes. It caps confidence when proofs are missing and outputs a completion status with next actions when blocked.

Avoid automated Rails refactors across multiple domain boundaries when they blur ownership of persistence, authorization, and lifecycle safety. Guardrails block out-of-scope refactors to prevent risky AI-assisted edits that are hard to verify and roll back.

You can verify ActiveRecord migrations by running scoped commands and preserving query or migration proofs as evidence. This satisfies verification requirements for a narrow production slice without demanding an extensive standalone test suite.