RESOURCES / RECORDS
A clearly labelled fictional example of a CANUS delivery record, as a named organisation reads it. No real customer, site or transaction is shown. Field names and values are shown as the API returns them.
HTML brief · Reviewed for public release · CANUS Technologies
Fictional specimen
JSON
{
"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"
}Fictional example. CANUS issues the result. The parties determine acceptance, funding release and billing under their own agreements.
example
true
This record is a format illustration, not a claim of a deployed API contract.
record
CCEC-EXAMPLE-0001
The record identifier inside the CANUS Register.
segment
EXAMPLE-PHASE-01
The part of the delivery this record covers: the phase, batch of equipment or block of capacity defined in the contract.
event
DELIVERY EXAMINATION
The agreed delivery check this record results from.
state
CONSISTENT
The result CANUS issued: the evidence supports the agreed requirements. The alternatives are INCONSISTENT and INSUFFICIENT EVIDENCE.
scope
Agreed delivery requirements
What was checked. The record resolves only the agreed requirements, within the stated scope.
predecessor_record
null
The earlier related record. A first delivery has none. Later deliveries, changes and replacements link to the record they follow.
permitted_use
As specified in the appointment
Who can use the result, and for which decisions, as agreed in the appointment.