A Build is not quoted until the control surface is visible.
The Proof decides whether a production engagement is justified. The Build only follows when the workflow, source material, acceptance criteria, operating duties and review points are clear enough to quote honestly.
-
Acceptance criteria
Every Build starts with the job it must perform, the material it must read, the limits it must respect, and the evidence needed to accept or reject the result.
-
Data handling and hosting
Hosting is agreed before production use: your environment, or private Australian hosting where selected. The system does not train on your data.
-
Human review points
The system assembles and proposes. Named people decide. Review points are specified before any output is relied on.
-
Monitoring and support
Operation, monitoring and quarterly review are included in the quoted Build price. The running of the system is part of the number, not a second negotiation.
-
Continuity
The operating model names what is maintained, what is logged, what is reviewed, and how the system is handed over or wound down if the engagement ends.
-
Conflict boundary
Where a Board Session leads to a Proof or Build, the recommendation must be explainable in writing. If the evidence does not support a production build, the Build is not quoted.