CANUS

INDEPENDENCE & ACCOUNTABILITY

Independence and accountability.

Independent delivery checks sit at the core of the CANUS programme. This page explains how they are governed: CANUS checks contracted AI capacity deliveries against the requirements the parties have agreed, and gives the named organisations signed results they can use. How we check is proprietary. The result, its limits and our accountability for it are not.

What we check

PRINCIPLES

Governed the same way.Every time.

  1. 01

    Your systems are not on trial

    Operator systems are built to run and report on the facility. The parties should not have to rely on those reports alone to learn what was delivered.
  2. 02

    The delivery is an agreed event

    Commissioning asks whether the facility works. CANUS answers the different question the parties agreed to ask: whether the contracted delivery took place as agreed.
  3. 03

    The standard comes from the agreement

    The requirements are fixed from the parties' own agreement before delivery. CANUS designs the check, never the standard.
  4. 04

    The result is one of three

    CONSISTENT, INCONSISTENT or INSUFFICIENT EVIDENCE. CANUS never reports more than the evidence supports.

YOUR RIGHTS TO THE EVIDENCE

A direct duty to answer.

Under the CANUS appointment, each organisation named to use the result can ask us to explain the evidence for its agreed use, without the payer's permission or first proving an error. We must respond, correct the record where needed, and identify unresolved questions or further work. The history is preserved.

The company paying for the programme cannot veto a named organisation's right to question our evidence.

RESPONSIBILITIES

Our part.Their part.

CANUS

  • 01How the check is carried out, how evidence is kept, the agreed scope and the signed result: CANUS answers for these under the appointment.

THE PARTIES

  • 01Grid connection and power approvals, site construction and readiness, cooling and network delivery, and commercial obligations. CANUS has no authority over any of them.
  • SCOPE DISCIPLINE
  • SIGNED RECORD
  • DOCUMENTED LIMITS

IF THE REQUIRED CHECK CANNOT BE ARRANGED FOR THE AGREED SCOPE, THE OUTCOME IS INSUFFICIENT EVIDENCE, NOT A SOFTER RESULT.

THE RESULT

Three outcomes.Nothing in between.

The result is signed and preserved either way. The parties apply it under their own agreements.

Consistent

The evidence supports the agreed requirements within the stated scope.

Inconsistent

The evidence conflicts with one or more agreed requirements.

Insufficient evidence

The evidence is insufficient to decide one or more requirements.

QUESTIONS AND CORRECTIONS

Any named organisation can question the result.

An organisation named to use the result can ask CANUS to reopen it on new evidence or a claimed error. CANUS reviews from the preserved record and issues a correction or a considered refusal, with reasons.

The original result is never edited in place. A correction enters the Register as a linked record, connected to the result it corrects. The full history remains available to every named organisation.

WHAT TO ASK

Questions to put to canus.

CANUS will answer each of these in writing before the order is signed.

  1. 01

    What exactly will you check, and which requirements will it resolve?

  2. 02

    What can stop a delivery being checked in its agreed window?

  3. 03

    What does a named organisation's right to question cover, and what does it cost?

  4. 04

    What does INSUFFICIENT EVIDENCE mean for our contract, and how is it resolved?

  5. 05

    Which obligations remain ours when others use the result?

Run it on a real delivery.

Start with a founding place: your first phase, checked independently against the requirements your customer agreed.

See an example