Delivery records · The CANUS Register
In a decentralised buildout the funding, the site, the power, the equipment and the installation are separate businesses under separate contracts. The CANUS Register is our system for signed delivery records, changes and corrections. Each record states what was checked, against which requirements, what the evidence supports, who may use the result and how it relates to earlier deliveries or changes. Each party decides under its own agreement.
Example delivery record
Fictional example. The result, what was checked, who may use it and what came before. The example API response carries the same content.
CANUS · THE REGISTER
FICTIONAL EXAMPLE
CANUS-EX-001
DELIVERY CHECK
Result
Consistent · SignedWho can use the result
Reads the signed result against the agreed delivery requirements. The parties' contract determines sign-off and billing.
{
"example": true,
"record": "CCEC-EXAMPLE-0001",
"segment": "EXAMPLE-PHASE-01",
"event": "DELIVERY EXAMINATION",
"state": "CONSISTENT",
"scope": "Agreed delivery requirements",
"predecessor_record": null,
"permitted_use": "As specified in the appointment"
}CANUS signs the result. The parties apply their own agreements.
What the record changes
The parties keep their own contracts. Where those contracts use CANUS evidence, the provisions are agreed between the parties. What changes is that the same signed result is available to everyone entitled to use it.
Problems the programme addresses
With the Record
That is how independent businesses build one project without taking each other's word for it.
The delivery record
Cloud operator, customer, lender, insurer, data-centre and installation partners read the same signed result, each under its own contract. Three possible results. We issue all three.
Consistent
The evidence supports the agreed requirements.
Inconsistent
The evidence conflicts with one or more requirements. An adverse result is complete, preserved and never edited away.
Insufficient evidence
The evidence is insufficient to decide. The open questions are named.
The customer's contract decides what a result means for sign-off. The lender's agreement decides what it means for funding. Billing follows the parties' own terms. CANUS signs the result.
Delivery and change history
A second customer, a later phase, an upgrade, a change of capacity source or a correction each earns its own record, and the Register links it to what came before. Each result keeps its scope, states whether it still applies, names who may use it, and is linked to any change, question or correction rather than written over. CANUS controls none of the parties' systems and is authoritative only for its signed result and its history.
01 · First delivery
CANUS-EX-001
Consistent · Signed
The agreed first phase is checked and the record issues.
02 · Expansion
CANUS-EX-002
Consistent · Signed
A new phase is checked for its own scope; the Register links it to the original.
03 · Capacity source change
CANUS-EX-003
Consistent · Signed
An agreed alternative data centre or cloud operator delivers the capacity. Valid earlier evidence is kept where the parties agree to use it; site, power and installation for the new capacity source are checked again.
04 · Correction
CANUS-EX-004
Insufficient evidence · Signed
A later material change leaves an open question. Preserved, not edited away.
Organisations entitled to use the result read the same signed record under their own policy.The Register is authoritative only for CANUS's signed result and its delivery and change history.
When the capacity source changes
The original result stays on record. A proposed alternative capacity source is checked for its own scope and receives its own result. The Register keeps the two connected, showing which earlier evidence still applies and which organisations have agreed to use it. A change of capacity source does not rewrite what happened before.
A previous result is not an automatic pass for a new arrangement. Transfer rights, acceptance and financing decisions remain with the parties.
HOW THE RESULT IS READ
Every interface serves the same signed result. Every named organisation reads the one issued record, within its agreed use.
Cloud operator
The signed result and delivery record of its own deliveries.
Compute buyer
The issued result against the contracted requirements, with the delivery and change history.
Lender
Signed delivery evidence its own systems and credit process can use directly.
Three founding places. The CANUS fee for the first agreed trial delivery check is waived; any third-party costs are agreed before work starts. Ongoing programme services are separately scoped and priced.
We do not supply, own, operate or finance what we check. Funding decisions stay with the lender.