Resources

Conformance

Run your work against the vectors to see whether it conforms, and at which level.

Approved by the Board for implementation · 20 November 2026

Status

Every specification here is a draft (version below 1.0). Build to them and comment on them, knowing they may change. No licence is granted yet.

In short

Each specification publishes test vectors in one shared format. Run your work against them to see whether it conforms, and at which level. Only CTU metering has published vectors so far; the first vectors for the other five are proposed for their next versions.

One vector formatid · spec · level · case · input · expect · sinceContinuityInvariant3 proposedProof format4 proposedLedger entryformat3 proposedCTU metering8 publishedAudit2 proposedStagedrollout3 proposedA builder’s report of which vectors their work passes is their own statement; it becomes a CRIS statement only after an audit.
Conformance across the library: one vector format for all six.

The vector format

FieldMeaning
idUnique within the specification, for example PF-3
specThe specification slug
levelThe conformance level it belongs to
caseOne plain sentence
inputThe illustrative input (invented values)
expectThe expected output, or the expected rejection
sinceThe version that added it

The vectors

SpecificationIdLevelCaseExpectedSince
continuity-invariantCI-11A change that keeps both halves of the Invariantpassesproposed for 0.2
continuity-invariantCI-21A change that loses correspondence in any domainfailsproposed for 0.2
continuity-invariantCI-31A change that drifts from purpose beyond tolerancefailsproposed for 0.2
proof-formatPF-11A pass with no lossesacceptedproposed for 0.2
proof-formatPF-21A staged verdict without conditionsrejectedproposed for 0.2
proof-formatPF-31A pass with a loss in one domainrejectedproposed for 0.2
proof-formatPF-41A corrected proofrefers to the old oneproposed for 0.2
ledger-entryLE-11An entry without a link to the previous onerejectedproposed for 0.2
ledger-entryLE-21A correctionpoints back to the entry it correctsproposed for 0.2
ledger-entryLE-31An entry with personal datarejectedproposed for 0.2
audit-methodAM-11A sample recorded after work startedrejectedproposed for 0.2
audit-methodAM-21A re-run that does not matchproduces a findingproposed for 0.2
staged-rolloutSR-11A move forward without a tested rollbackrefusedproposed for 0.2
staged-rolloutSR-21A failure at a stagemoves back one stageproposed for 0.2
staged-rolloutSR-31Live without an external auditrefusedproposed for 0.2
ctu-meteringCT-V11A passing cycle on one deviceOne record; all fields present0.2.0
ctu-meteringCT-V21A cycle rejected at the gateOne record; outcome reject; energy counted0.2.0
ctu-meteringCT-V31A cycle that fails before the gateOne record; outcome failed; energy counted0.2.0
ctu-meteringCT-V42Two cycles sharing a nodeTwo records; allocations sum to the node meter0.2.0
ctu-meteringCT-V52Missing meter readings for part of a cycleRecord marked unverified; no silent estimate0.2.0
ctu-meteringCT-V62A correction for a calibration errorA new record pointing back; the original unchanged0.2.0
ctu-meteringCT-V71No CTU definition yetConversion: none; CTU empty; raw values present0.2.0
ctu-meteringCT-V81A record with a personal name in itRejected0.2.0

All inputs are illustrative. No implementation has been tested against these vectors yet.

Implementation reports

You may publish which vectors your work passes, at which level and for which version. Such a report is your own statement. It becomes a statement by CRIS only after an audit under the audit method.

Back to the specifications

Owner: Systems EngineeringNext review: 2027-05-11