// Enforce reproducible testing, automated verification, and evidence-driven sign-off before merging any change.
Model the end-to-end system, constraints, and failure modes before touching code; use whenever a change spans multiple layers or unclear requirements.
Decompose work into safe, observable increments with feature flags, rollbacks, and communication baked in.
Design every change with traceability, diagnostics, and fast incident triage in mind across mobile, web, and web3 stacks.
Guard latency, memory, battery, bandwidth, and gas/compute budgets by measuring before and after every change.
Deliver changes with clear communication, reviewer-ready context, and follow-up accountability.
Apply proactive threat modeling, least-privilege design, and safety guardrails before delivering any code or infrastructure change.
| name | eng-rigorous-validation |
| description | Enforce reproducible testing, automated verification, and evidence-driven sign-off before merging any change. |