How should core System Design Principles be prioritized in distributed systems?

I am looking for a definitive architectural rationale on how to prioritize and rank the following five system design principles from most critical to least critical: A) Scalability B) Reliability & Fault Tolerance C) Maintainability D) Consistency E) Availability While I understand that constraints depend heavily on the business domain (e.g., finance vs. high-volume social media), what is the industry-standard consensus for ranking these from a foundational software lifecycle perspective? If you had to drag-and-drop these from MOST to LEAST important, what would your order look like, and what are the primary trade-offs driving your top and bottom choices?