F.12:9.1 - SaaS uptime

• Promise content: availability ≥ 99.9% for the named service scope in June.
• Delivery Work population: the in-scope service-delivery occurrences during June, connected to the promise through the applicable A.2.3 relations.
• Evidence: synthetic-probe observations, with regions and outage-detection coverage stated. If their measurement model directly concerns the promised availability characteristic, no proxy is added; otherwise the distinct probe-to-user indicator relation needs a defining or testing pattern.
• Evaluation: a System performs evaluation Work; the exact application binds observed good time and total in-scope time and returns a value on the declared result scale.
• Status or summary: map the result to RequirementStatus=Satisfied or RequirementStatus=Violated only when that F.10 rule applies. If the evidence basis is inadequate, use EvidenceStatus=Inconclusive and RequirementStatus=Pending, or the exact locally declared result. Plainly: met, not met, or cannot judge.