WHAT WE CHECK
Inside a CANUS programme, CANUS checks each delivery against the requirements the parties have agreed, fixed before delivery. These are the categories those agreed requirements usually cover. How we check is proprietary; the requirements are the parties' own.
The categories
The amount of capacity the order promises at the delivery point, at the agreed configuration. The parties write the requirement; CANUS checks whether the delivery meets it.
Evidence class
THE PARTIES' ORDER DOCUMENTS
Checked against
THE AGREED DELIVERY REQUIREMENTS
Reported as
CONSISTENT / INCONSISTENT / INSUFFICIENT EVIDENCE
What the delivered capacity must be: the equipment classes, quantities and arrangement written into the order, checked as agreed requirements rather than assumed from anyone's records.
Evidence class
AGREED CONFIGURATION REQUIREMENTS
Checked against
THE AGREED DELIVERY REQUIREMENTS
Reported as
CONSISTENT / INCONSISTENT / INSUFFICIENT EVIDENCE
The power, cooling and network conditions the parties set as delivery requirements. These are contractual requirements the parties agree, not measurements CANUS publishes.
Evidence class
AGREED DELIVERY CONDITIONS
Checked against
THE AGREED DELIVERY REQUIREMENTS
Reported as
CONSISTENT / INCONSISTENT / INSUFFICIENT EVIDENCE
The agreed delivery dates and the conditions attached to them, so every party works from the same record of what was due and what arrived.
Evidence class
THE AGREED SCHEDULE
Checked against
THE AGREED DELIVERY REQUIREMENTS
Reported as
CONSISTENT / INCONSISTENT / INSUFFICIENT EVIDENCE
Planning, connection and commissioning approvals the parties supply into the scope. CANUS records them as connected requirements; the relevant authorities keep every approval decision.
Evidence class
APPROVALS SUPPLIED BY THE PARTIES
Checked against
THE AGREED DELIVERY REQUIREMENTS
Reported as
RECORDED AS CONNECTED REQUIREMENTS
Every signed result states its limitations and any agreed requirement that remains unresolved. CANUS never reports more than the evidence supports, and never fills a gap by inference.
Evidence class
THE SIGNED RESULTS
Checked against
THE AGREED DELIVERY REQUIREMENTS
Reported as
STATED LIMITS + UNRESOLVED REQUIREMENTS
SHARED INFRASTRUCTURE
Large AI campuses grow in stages, and every stage stands on approvals owned by others. CANUS records those approvals as part of the agreed scope; it never decides them. The network and other relevant authorities keep all power approvals.
Evidence class
Checked against
Reported as
Evidence class
Checked against
Reported as
Evidence class
Checked against
Reported as
Evidence class
Checked against
Reported as
Evidence class
Checked against
Reported as
One stage's result says nothing about another stage, and nothing about any neighbouring customer's service.
Every category is checked against the requirements the parties agreed before equipment was ordered, and reported in the same three words.