Requirements model

Start with what must be true.

An operational requirement describes an outcome to evaluate. It does not prescribe an internal host, cluster, vendor, or implementation.

What to provide

• Business criticality, customer impact, and growth horizon.
• Availability, latency, throughput, and degradation expectations.
• Ordinary, burst, seasonal, and launch traffic.
• Data classification, durability, retention, backup, RPO, and RTO.
• Security, audit, contractual, and regulatory constraints.
• Geography, residency, and regional continuity needs.
• Target and maximum cost, plus acceptable tradeoffs.
• Change windows, approvals, escalation, and support needs.
• Repository revision, runtime, dependencies, state, and integrations.

How results are reported

Each requirement evaluates to met, at-risk, unmet, unknown, or not-applicable. Unknown is never treated as met, and a hard constraint is never silently weakened to reach a cost target.