django-domain-delivery

Safe Django migrations require reversible operations or explicit waivers for irreversible decisions, including documented deploy order and rollback paths. This workflow gates completion on scoped verification commands, query/transaction evidence, and a repair-or-deferral loop on failures.

Transaction.atomic in DRF viewsets requires query and rollback evidence to verify side-effect safety. You constrain viewsets to request orchestration while maintaining transaction boundaries, ensuring persistence shape changes roll back cleanly when permission or API contract tests fail.

Testing Django permission and API contract changes requires scoped verification commands and permission tests gated on query evidence. You run a repair loop on failures, ensuring serializers validate API contracts and viewsets enforce auth boundaries before delivery.

Yes, this workflow applies to async Django tasks by requiring idempotent, retry-bounded task design with failure evidence. You maintain observability using existing logging, metrics, and tracing patterns while constraining tasks to async side-effect boundaries.

Django ORM query changes break serializer contracts when persistence shape and API boundaries overlap. You prevent this by keeping models and managers focused on persistence shape, serializers on API contracts, and viewsets on request orchestration with scoped verification.