react-domain-delivery

Manage React state transitions by converting tasks into bounded UI state-machine changes with named visible states, explicit state ownership, and a named rollback path. This prevents unbounded edits and ensures disciplined component delivery with clear proof.

Implement loading, error, and empty states by explicitly modeling them within a UI state-machine architecture. This approach avoids derived-state misuse via effects and ensures async error handling flows are properly bounded and verifiable during React component delivery.

Verify React Testing Library coverage and accessibility behavior by requiring scoped commands, focused tests, and recording verification receipts. This evidence-first approach ensures accessibility checks and state transitions are provably correct within existing project conventions.

Defer React changes when required runtime constraints, approvals, or project conventions are missing. Safe deferral ensures that state management, async data integration, and accessibility behavior are not implemented without the necessary source-of-truth inspection and boundary ownership.

Yes, this discipline works for reviewing existing async data integration, forms, and hooks by applying source-of-truth inspection and scoped verification evidence. It explicitly models UI states and requires a named rollback path to ensure safe, bounded modifications.