Resources

CTU metering method

What is metered, at which boundary, in what record, how it is checked and how it is reported.

Approved by the Board for implementation · 20 November 2026

DraftVersion 0.2.0Drafted 12 November 2026Owner: Systems Engineering (role being recruited; interim owner to be named, Q4)Licence: [to be confirmed]Side of the line: published

A draft (0.x): read it, build to it and comment on it; it may change without notice. Drawn from the CTU book and the Sovereign Stack page. Changelog · Comment on this specification

Relies on: Correspondence proof format, Ledger entry format · Relied on by: Audit method

This is a draft (0.x). It may change without notice, and no deployment is metered to it yet. Every number on this page is an example, not a measurement.

1 Purpose

Every CRIS system reports the compute and energy it uses in Compute Thermodynamic Units (CTU), so that gains in capability can be weighed against their cost. This is design principle 5: measured cost. This specification sets out what is metered, how, in what record, how a record is checked, and how it is reported. It does not yet define one CTU; Continuity Labs will state that definition, from the CTU book, in a later version. Until then, records keep the raw energy and compute figures, and CTU is left empty.

No CTU definition yet. Records keep the raw energy, compute and cost; the Conversion field reads none and the CTU field stays empty. Continuity Labs will state the definition, from the CTU book, in version 0.3.

2 What CTU is, and is not

CTU is a unit of measurement. In this specification it measures the compute and energy a cycle used. It is not money, a token or an asset, and it cannot be bought, sold, held or exchanged. CTU is not used in any reward or payment calculation; if that ever changes, the method will be published and approved first. On the CES Platform, Participation record (CTU) is a separate record of participation. The one list of what CTU is not, for both senses, is on the CTU page.

The four rules

Kept from version 0.1, with rule 4 reworded (Q2).

  1. Every cycle is metered, including cycles whose change fails.
  2. Capability is reported beside its energy and cost, never alone.
  3. No figure is published until it is measured. This draft contains no figures.
  4. In a sovereign deployment, each partner sees the compute and energy its own deployment used.

The method in pictures

Sixteen pictures set out the method: what changed, who reads it, how it measures, how a record is checked and reported, what CTU is not, and how the specification reaches 1.0.

What changed. Draft 0.1’s six sections, and what this version did with each finding.

Draft 0.1: six sections, and what version 0.2 did with each finding1 PurposeK1 · the unit is still not defined; now said plainly2 What is meteredK6, K7 · boundary tiers and the gain-per-CTU form3 RulesK9 · rule 4 reworded from “bought” to “used”4 Where reportedK4, K5 · one indicator, one direction (Q3)5 Open questionsK12 · shared and testnet hardware answered6 Changelogkept, now 0.2.0Missing: recordK8, K10 · fields, lifecycle, checks, test vectors addedMissing: what CTU isK2, K3 · a measure, not money; two senses explaineddone in 0.2waiting on a decision
The page before this update: six sections, and where the twelve findings sat.

Who reads it. Six readers, and what each now gets.

BuilderNeedsto emit arecord thatpasses the testvectorsNow getsthe record; thevectorsDeploymentpartnerNeedswhat they willsee, and how tocheck itNow getsroll-ups; thechecksAuditorNeedsto re-derive afigure fromsigned recordsNow getschecks; theledger linkResearcherNeedsthe candidatedefinitions ofa CTUNow getswhat adefinition muststateBenefitreaderNeedsone indicator,in onedirectionNow getsthe indicator(Q3)ParticipantNeedswhich CTU ismeant, and thatit is not moneyNow getsCTU on thissite
Who reads the specification: six readers and their first question.

Raw quantities first. CTU will be derived from measured energy, compute and cost under a versioned conversion.

Recorded for every cycleEnergyjoules, at a tierComputedevice-secondsCostcurrency, with basisConversionnone yet:Continuity Labs, 0.3CTUempty until definedWhy raw first: metering can start now; a new definition recomputes every past record andboth versions are shown; an auditor checks the meter readings and the conversion separately.
Raw quantities first; CTU derived under a versioned conversion that Continuity Labs will set.

The boundary. What is inside each tier.

T3 Network: data moved between sitesBytes moved × a stated energy rate · optionalT2 Facility: cooling, power conversion, building overheadA facility meter apportioned to the cycle, or T1 × a stated factor · when availableT1 Devices: what the cycle usedAcceleratorsCPUsMemoryStorageEvery record and report names its tier. Figures at different tiers are never added or compared. Required: T1.
The measurement boundary: devices, facility, network. Every figure names its tier.

A record’s life. From opening to the ledger.

Openwhen the cycle startsCloseat any outcomeSignby the metering agentVerifyfive checksLedgerfingerprint as evidenceafter signing: never edited; a correction is a new record that points backfails a check: unverified, excluded
Record lifecycle: open, close, sign, verify, ledger.

Verification. Five checks before a record counts.

Signed record1 Signatureregistered agent2 Cycleon the ledger3 Timeinside the cycle4 Plausibilitywithin published range5 Allocationsums to the node meterVerifiedcounts toward reportsUnverifiedexcluded; reviewedThen an auditor samples records under the audit method and re-reads the raw meter logs.
Verification: five automatic checks, then sampling by an auditor. “Verified” and “audited” mean exactly that.

Reporting. Three roll-ups.

Verified recordsone per cyclePartner reportthe partner, its own figuresnever:Other partners' figuresCRIS totalsCRIS; the Board; auditorsnever:Unverified recordsBenefit indicatorthe public, in the reportnever:Any figure not yet measuredIndicator: to be chosen (Q3); the count of local deployments is reported beside CTU, not in it.
Aggregation: a partner report, CRIS totals and one benefit indicator.

Corrections and disputes. History is never rewritten.

1 Raisepartner, auditor or CRIS2 Flagthe records concerned3 Investigateraw logs, calibration4 Decidecorrect, or confirm5 Reissuewith a noteAppealoutside Systems Engineering (Q8)Never overwrite: a correction is a new recordNo silent estimates: an estimate is marked as one
Disputes and corrections: five steps and an appeal. History is never rewritten.

Threats and guards. How a figure is kept honest.

Inflated or deflated readingsSigned records; plausibility check; audit re-reads logsA failed cycle left outOne record per cycle, any outcome; ledger cross-checkEnergy shifted between cyclesAllocation must sum to the node meterBack-dated or edited recordsTrusted time; fixed once signed; ledger fingerprintA stolen agent keyRegistered keys; revocation publishedTestnet passed off as deploymentDeployment field; testnet always kept apartA record holds no personal data, so the real risk is a figure made to look better than it is.
Threats: six ways a figure could be wrong on purpose, and the guard already in the design.

The money line. CTU is a measure, not money.

CTU in CRIS systemsthe compute and energy a cycleused · about machinesthis specificationCTU on the CES Platforma record of participation· about a participantthe CES Platform CTU pagenever convertsNeither is money, a token or an asset; neither can be bought, sold, held, spent or exchangedWords to use: metered, recorded, figure, measure · never: price, balance, wallet, earnedThe one gate to paypublished method + counselNot used in any reward or paymentcalculation today
The money line: two senses of CTU, one gate to pay, and that gate is closed today.

Conformance. Three levels and eight test vectors.

Level 1 · Recordfor testnet cyclesLevel 2 · Verifiedfor partner reportsLevel 3 · Facilityfor benefit-report figuresTest vectorsV1 · L1 · A passing cycle on one deviceV2 · L1 · A cycle rejected at the gateV3 · L1 · A cycle that fails before the ga…V4 · L2 · Two cycles sharing a nodeV5 · L2 · Missing meter readings for part …V6 · L2 · A correction for a calibration e…V7 · L1 · No CTU definition yetV8 · L1 · A record with a personal name in…A meter conforms at a level when it gives the expected result for every vector at that level. No meter has been tested yet.
Conformance: three levels and eight test vectors, so a partner can start at Level 1 and climb.

The road to 1.0.

0.1.0Published 11 Nov 2026Purposewhat is meteredfour rules0.2.0This draftBoundary tiersrecord fieldslifecycle0.3.0Q1 2027The definition of on…from Continuity Labs0.4.02027Testnet cycles meter…outside review of th…1.0.0After a metered runLicence confirmeda deployment metered…Each version earns one thing; 1.0 needs a licence and a deployment metered at Level 3. Dates after 0.2 are proposals.
The road to 1.0: one thing earned per version.

How this specification is built. The section map, the data files, the page and the build steps.

CTU metering, version 0.2twelve sectionsTest vectors →newCTU on this site →newAlignedSovereign Stack #ctuHow rewards workPublic benefit B2CES Platform CTUCIX FAQ
Section map: the specification, two new pages and five aligned pages. Select one to open it.
data/specs.jsonthe header: version, state,date, licence, ownerdata/ctu-metering.jsontiers, fields, checks, levels,vectors, conversionsdata/devhub-changelog.jsonone entry per version;the feedThe page, the vectors, the buildconversions stays empty until Continuity Labs and Systems Engineering both sign a definition.
Data: three files, each with one job.
1 Purpose2 What CTU is, and is notThe four rules3 The boundary4 What is measured5 The record6 Verification7 Reporting8 Corrections and disputes9 Security and privacy10 Conformance11 Open questions12 Changelog
The specification page at version 0.2: twelve sections, with the four rules from 0.1 kept.
1 Data filebuilt (draft)2 Table directivesbuilt (draft)3 Twelve sectionsbuilt (draft)4 Vectors pagebuilt (draft)5 CTU on this sitebuilt (draft)6 Align five pagespartly; Q3 waits7 Build checksbuilt (draft)8 Two signatureswaiting on you9 Changelog 0.2.0built (draft)Two signatures: Systems Engineering on the method; the Founder on the money line, and counsel if any link to pay is proposed.
Build pipeline: checks, then two signatures.

3 The boundary

Every figure names the boundary it was measured at.

TierInsideHow measuredRequired in 0.2
T1 DevicesAccelerators, CPUs, memory and storage the cycle usedDevice energy counters, or a power meter on the node, sampled over the cycleYes
T2 FacilityT1, plus cooling, power conversion and building overheadA facility meter apportioned to the cycle, or T1 × a stated overhead factor with its sourceWhen the site can meter it or states a factor
T3 NetworkT2, plus data moved between sitesBytes moved × a stated energy rateNo

From data. Every figure names its tier; figures at different tiers are never added or compared.

4 What is measured

For each cycle: energy in joules at the stated tier, with the meter type and its stated error; compute in device-seconds, by device model; cost in local currency, with its basis; and the cycle’s signed start and end times.

QuantityUnitSourceAccuracy to state
Energyjoules (reported as kWh)Device counters or node meter (T1); facility meter or factor (T2)Meter type and stated error
Computedevice-seconds, by device modelScheduler recordsClock source
Costlocal currency, with the basis (tariff, amortisation)The partner's tariff or contractBasis and date
Durationseconds, start and endSigned timestampsClock source

A cycle is one pass of the Continuity Recursion Loop: a proposal, its proof and its gate decision. Every cycle gets exactly one metering record, whatever its outcome. Work that is not part of a cycle (idle capacity, maintenance, training of staff) is reported separately and never folded into a cycle’s figure.

Where a cycle shares hardware, energy is allocated by the device-seconds it held, and the rule is recorded. On testnet nodes, such as those of the Botswana Global Testnet Initiative under a written agreement, the node operator’s meter is used and named; cycles on testnet nodes are labelled testnet and kept apart from deployment figures.

The Botswana Global Testnet Initiative. An organisation also led by our Founder. Any work with CRIS is under a separate written agreement on arm’s-length terms. Related organisations

Correspondence gain per CTU. The ratio needs a numerator. The proposal is that the correspondence proof states the cycle’s measured correspondence gain, and the metering record refers to that proof. Until the proof format defines the gain, the ratio is shown only as a form, gain (from the proof) ÷ CTU (from this record), with no example value (Q4).

5 The record

FieldRequiredMeaningExample (illustrative)
Record IDYesUnique and permanentexample: mr-0001
Cycle IDYesThe cycle metered, as on the ledgerexample: cy-0042
OutcomeYesThe gate decision: pass, staged, reject, or failed before the gateexample: reject
DeploymentYesDeployment or testnet, and which; never a personexample: testnet
Boundary tierYesT1, T2 or T3example: T1
Start, endYesSigned timestampsexample: 2027-01-01T10:00:00Z / 10:04:10Z
EnergyYesAt the stated tier, with meter type and stated errorexample: 9000000 J ± 2% (node meter)
ComputeYesDevice-seconds by device modelexample: 1000 device-s, model A
CostYesAmount, currency and basisexample: 12.50 in local currency, tariff
Allocation ruleIf anyHow shared hardware was split, if anyexample: by device-seconds
ConversionYesThe CTU definition version used, or noneexample: none
CTUIf anyDerived value; empty while no definition existsexample: empty
Proof referenceYesThe correspondence proof for the cycleexample: proof-0042
CorrectsIf anyThe record this one corrects, if anyexample: empty
SignatureYesThe metering agent that wrote itexample: agent-07 signature

Draft 0.2. Field names may change. Every value in the last column is an example, not a measurement.

Rules: one record per cycle, whatever its outcome, including cycles that fail; a signed record is never edited; a correction is a new record that points to the one it corrects, as the ledger entry format requires; a record names a deployment, never a person; raw values are kept after a CTU figure is derived.

6 Verification

Before it counts toward any report, every signed record must pass five checks. A record that fails any check is marked unverified and excluded.

#CheckFails whenResult of a fail
1SignatureThe signature is invalid, or the signer is not a registered metering agentUnverified; incident
2CycleNo ledger entry, proof or gate decision exists for the cycleUnverified
3TimeThe record's times fall outside the cycle, or two records overlap on one deviceUnverified
4PlausibilityEnergy is outside the published range for the devices and durationUnverified; review
5AllocationAllocated energy across records on a node does not sum to the node meter within the stated errorUnverified for every record on that node and period

The metering agent signs each record with a registered key that can be revoked. A partner can run the same checks on its own records with the Continuity Audit Suite, without CRIS. An auditor samples records under the audit method, re-reads raw meter logs and reports the share that matched. A figure may be called verified only when every record behind it passed, and audited only after an audit has covered it.

7 Reporting

Roll-upWho sees itContainsNever contains
Partner reportThe partner, for its own deploymentEnergy, compute, cost and CTU per cycle and per month, by tier; failed cycles; idle time apartOther partners' figures
CRIS totalsCRIS; the Board; auditorsAll deployments, by tier; testnet kept separateUnverified records
Benefit indicatorThe public, in the benefit reportOne figure per reporting period, with scope and tierAny figure not yet measured

The Knowledge Ledger’s entry for each cycle will carry its metering record’s fingerprint as an evidence reference, so any later change is detectable (Q6).

The benefit indicator is not yet chosen (Q3). The site describes it two ways, and they are different measures, not one stated twice:
  • Energy per unit of capability gain, in CTU: lower is better; used on this specification (0.1) and the Sovereign Stack page (recommended: it is the one gain per CTU supports).
  • Useful compute per unit of energy, in Compute Thermodynamic Units: higher is better; used on data/benefit.json B2.
Once chosen, it is stated once in the benefit data and every page reads its label and direction from there.

The second sovereignty indicator, deployments running on local infrastructure with local data, is a count. It is reported beside CTU and is not measured in it. No figure is published until it is measured.

8 Corrections and disputes

ErrorExample (illustrative)Fix
Meter faultA node meter stops reporting for an hourRecords for that hour marked unverified; an estimate is never substituted silently
CalibrationA meter reads 3% high against a referenceCorrection records for the affected period, with the factor and its source
AllocationShared hardware split by the wrong ruleCorrection records for every cycle on that node and period
ClockTimestamps out of orderUnverified until re-signed with a corrected time source
ConversionA new CTU definition versionNot an error: CTU recomputed under the new version; both shown

Anyone with a stake in a figure (a partner, an auditor or CRIS) can raise a dispute. The records concerned are flagged, investigated against the raw logs and meter calibration, and either corrected by new records that point back or confirmed with a written reason. A published figure that changes is reissued with a note. An estimate is always marked as one, with its method, and never called measured. Appeals go to someone outside Systems Engineering, to be named (Q8).

9 Security and privacy

Records are signed by registered keys and timed from a stated, synchronised source. A revoked key’s later records are rejected. Raw meter logs are kept for [a period to confirm] so they can be re-read. In a sovereign deployment, records and logs stay on the partner’s infrastructure and only agreed roll-ups leave. Records hold no personal data: they describe machines and cycles. Published figures are totals by tier and scope; a deployment small enough to identify a partner is grouped with others or withheld.

10 Conformance

A meter conforms at a level when it gives the expected result for every test vector at that level.

LevelA meter at this levelNeeded for
1 RecordEmits one complete record per cycle, with every required field and unit, including failed cyclesTestnet cycles
2 VerifiedLevel 1, plus signed records that pass the five checks, with T1 measuredPartner reports
3 FacilityLevel 2, plus T2 metered rather than estimated, and raw logs kept for auditBenefit-report figures

11 Open questions

  • The definition of one CTU (Continuity Labs, version 0.3).
  • How the correspondence gain in gain per CTU is stated in the proof format (Q4).
  • Which benefit indicator, in which direction (Q3).
  • Who hears appeals (Q8), and how long raw logs are kept (Q7).
VersionAddsGate to the nextWhen
0.1.0Purpose, what is metered, four rules, reporting, two open questions—Published 11 Nov 2026
0.2.0Boundary tiers, record fields, lifecycle, checks, the money line, disputes, test vectorsSystems Engineering review; Founder approves the money lineThis draft
0.3.0The definition of one CTU and the first conversion, from Continuity LabsContinuity Labs and Systems Engineering both signQ1 2027 (proposed)
0.4.0Testnet cycles metered at Level 2; outside review of the methodReview published2027 (proposed)
1.0.0Licence confirmed; a deployment metered at Level 3Sovereign Stack status set with evidenceAfter a metered run

12 Changelog

  • 0.2.0 · 12 November 2026 · minor · Adds the boundary tiers, the record, verification, reporting, corrections, security, conformance and test vectors; states what CTU is and is not; rewords rule 4 from bought to used. Awaiting Systems Engineering’s review and the Founder’s approval of the money line.
  • 0.1.0 · 11 November 2026 · minor · First draft, from the CTU book and the Sovereign Stack page.

Printed from the developer hub changelog, the one record of every version.

Owner: Systems EngineeringNext review: 2027-05-11