Skip to content

Compute accountability infrastructure

Making Compute Accountable.

CarbonStream Nexus develops infrastructure protocols that make digital compute measurable, attributable, and governance-legible.

Prototype — functional

A working browser prototype generates non-authoritative demonstration Compute Accountability Records from declared inputs, assumptions/defaults and illustrative scenarios. It is not a production system, measures no infrastructure and does not verify workloads or inputs.

Compute accountability chain
  1. 01Compute

    A workload runs: training, inference, or general processing.

  2. 02Measurement

    Compute activity is quantified in explicit units.

  3. 03Context

    Location, grid and operating conditions are attached.

  4. 04Attribution

    Impact is assigned to a responsible subject.

  5. 05CAR

    A structured Compute Accountability Record is produced.

  6. 06Governance

    Evidence becomes legible to institutional processes.

Position

Compute is consequential. It is rarely accountable.

Digital compute consumes energy in specific places, under specific conditions, on behalf of specific parties. That chain is almost never recorded in a form an institution can act on. CSN treats it as an infrastructure problem: define the record, define the method, make the evidence legible.

Measurable

Compute activity expressed in explicit units, with every input declared and every assumption named.

Attributable

Impact assigned to a subject through a stated method, with the full calculation path exposed.

Governance-legible

A structured record that regulators, funders and operators can read, check and reference.

Build state

What exists, and what does not

CSN is early-stage. This site labels every capability with one of four states so nothing has to be inferred.

  • Compute Accountability Demonstrator

    Prototype — functional

    A working six-step, browser-based workflow that turns declared workload inputs into a timestamped structured record with a fully visible calculation trace.

  • CAR artefact generation (structural)

    Prototype — functional

    Human-readable and machine-readable views of a timestamped demonstration record, with copy, download and structural validation.

  • Provenance and truth-state labelling

    Prototype — functional

    Every value carries its origin — declared, assumed, scenario or simulated — and every capability carries its build state.

  • CAPS-Core protocol foundation

    Specified

    The protocol layer is being defined in writing. The authoritative specification governs; this site does not implement it.

  • Authoritative CAR schema

    In development

    CAR Technical Specification RC1 is technical review only, not ratified, and is normative over CAR Overview for technical conflicts. The prototype uses a non-authoritative demonstration schema and claims no RC1 conformance; technical source text is not incorporated here.

  • CSN attribution method

    In development

    The prototype runs the CSN Demonstration Calculation Engine, whose arithmetic is fully visible. The authoritative production calculation specification is pending.

  • Telemetry ingestion and measurement APIs

    Research / future

    No telemetry is ingested. No infrastructure is instrumented. No live data of any kind reaches this application.

  • Verification and attestation

    Research / future

    Third-party verification, signing and registry mechanics are research topics, not implemented functionality.

Start where it is concrete

The demonstrator is the shortest path to understanding what a Compute Accountability Record is, how one is produced, and what it does and does not prove.