Demonstrator
Compute Accountability Demonstrator
Prototype — functionalDescribe a workload, declare inputs, select context, inspect attribution and generate a simulated, non-authoritative Compute Accountability Record (CAR). Everything runs in your browser; nothing is measured.
1 — Define workload
Describe the compute activity being accounted for. All fields are declared inputs.
What this demonstrates, and what it does not
What it demonstrates
- That a compute workload can be described in explicit, structured terms.
- That every input can be labelled as declared, assumed or scenario-supplied.
- That each calculation step can be exposed as input, unit, calculation and output.
- That the result can be assembled into a timestamped, uniquely identified, machine-readable demonstration accountability record. A third party can inspect and recompute the disclosed arithmetic, but this does not verify the workload or its inputs.
What it does not demonstrate
- It does not measure real infrastructure or ingest any telemetry.
- It does not use verified national or facility emissions factors.
- It does not attest that the described workload actually occurred.
- It does not certify anything: no independent verification, no signature and no CCAS certification grade exists.
From receipt to infrastructure
Direction
From receipt to infrastructure
The prototype illustrates a possible demonstration record structure. Turning that artefact into infrastructure requires measured inputs from instrumented facilities, sourced and citable context factors, an authoritative calculation specification, and an independent verification process that can attest a record rather than merely timestamp it.