Every claim on this website should be traceable to evidence for the purchased scope. This page records that evidence as it stands, including remaining validation requirements, because a buyer deserves the same truthfulness before the order as after it.
Each capability has a named delivery owner. A capability is described as available only when its purchased workflow and its financial connection have passed release checks on a deployed build and a synthetic operating cycle has been traced end to end. Automated checks alone are not treated as sufficient, and an edition never inherits availability from another edition or from a catalogue entry.
The statements below identify what must be verified for the purchased scope. A scope review provides the current evidence and the remaining validation requirements.
We will not provision an account from an enquiry, invent customer proof, promise a delivery date that is not backed by named available hours, or describe a limited first cycle as the whole product. If support exceeds the agreed allowance or a representative acceptance test fails, new sales of the affected scope pause until it is resolved.
A scope review is a working conversation about your last hard operating cycle. It ends with one recommendation, one engine and a dated payment calendar, or with an honest no.