Compute Accountability Record (CAR)
Overview and Adoption Guide

1. Purpose

This document introduces the Compute Accountability Record (CAR) in clear, public language. It explains the problem CAR is designed to solve, the value it is intended to provide, and how it fits into the wider CarbonStream Nexus publication series. It is intentionally written as an overview. The technical detail belongs in the CAR Technical Specification.

2. Executive Summary

Computation now sits at the center of modern business, science, and digital infrastructure. As organizations rely more heavily on AI, cloud platforms, data processing, and high-performance systems, they increasingly need a reliable way to describe the environmental impact of that computation.

CAR is CarbonStream Nexus's proposed answer: a structured record for computational activity and its related energy and carbon-accountability information.

“Make computational environmental claims more transparent, reproducible, exchangeable, and verifiable.”

CAR is not a replacement for existing sustainability standards or assurance frameworks. Instead, it is a record format that can support them by organizing information in a consistent and interoperable way.

3. The Problem

Computational activity now takes place across many environments, including public cloud, private cloud, hybrid systems, on-premise infrastructure, and specialized compute clusters. The environmental information associated with that activity is often just as fragmented. Different tools may report different numbers, use different assumptions, or describe the same workload in incompatible ways.

That fragmentation creates a basic coordination problem. The computation happens in one place, while its environmental accountability is often described somewhere else, using different formats and different rules.

CAR is designed to reduce that gap.

4. The Core Idea

The simplest way to understand CAR is to think of it as a receipt for computation.

Note: CAR stands for Compute Accountability Record. The receipt comparison explains how CAR behaves, not an alternative name for the format.

A receipt records what happened, when it happened, who issued it, and what information was captured at the time.

CAR applies the same general idea to computational workloads. A CAR can capture a workload description, the resources involved, the methodology used, the resulting accountability information, and the level of assurance attached to the record. That makes the record easier for humans to read and easier for software systems to process.

Computational Activity → Resource / Telemetry Data → Methodology + Assumptions → Energy Attribution → Emissions Calculation → Compute Accountability Record → Human Review / Software Processing → Verification / Assurance → Reporting Systems.

5. What CAR Is

CAR is:

• a structured digital record.
• designed for interoperability.
• methodology-aware.
• traceable.
• machine-readable and human-readable.
• capable of carrying verification information.
• extensible across different computational environments.

CAR is not:

• a replacement for greenhouse gas accounting standards.
• a carbon offset or emissions credit.
• a guarantee of accuracy by itself.
• a substitute for independent assurance.
• a claim that every workload can be measured perfectly.

That distinction matters. CAR standardizes the record of accountability. It does not solve measurement quality, data completeness, or verification on its own.

6. Why It Matters

A common record format can make computational accountability easier to communicate across tools, teams, and organizations. It can support better reporting, more consistent comparisons, stronger auditability, and clearer governance. It can also reduce dependence on proprietary reporting approaches that make interoperability difficult.

For organizations, that means less ambiguity. For ecosystem partners, it means a shared way to exchange information. For the public, it means computational claims can become easier to understand and scrutinize.

7. Where Methodology Fits

CAR is linked to methodology. A methodology defines how the record is produced, what assumptions are used, and how the resulting accountability information should be interpreted. That matters because methodologies evolve over time. If a historical record is later viewed under a newer method, the original context should still be preserved.

CAR supports that continuity by keeping the record tied to the methodology under which it was produced.

8. What a CAR Can Describe

At a high level, a CAR may include information about:

• the identity of the record.
• the computational workload.
• the resources used.
• the environmental attribution.
• the methodology behind the calculation.
• the provenance of the information.
• the verification or assurance status.

Note: The exact technical requirements for these elements are defined in the CAR Technical Specification. This overview explains their purpose in general terms only.

9. Example Scenario

Imagine a training workload that uses a measurable amount of compute over a defined period. A CAR can preserve the basic facts of that workload, the methodology used to interpret it, and the resulting accountability information in one structured record.

The value of the record is not just the calculation itself. It is the ability to trace how the calculation was formed, what it refers to, and whether it has been reviewed or verified.

10. CAR and Verification

CAR can support different assurance states. A record may begin as self-attested and later be reviewed or verified through additional processes.

Verification and record creation are different functions. CAR provides the record. Verification provides confidence in the record. Keeping those roles separate helps preserve clarity and trust.

11. Interoperability

CAR is designed to work across different infrastructures and organizations. That includes public cloud, private cloud, hybrid environments, on-premise systems, and future computational architectures.

The goal is to make accountability information portable rather than locked to a single vendor or platform.

This is one of the reasons interoperability is central to the CarbonStream Nexus approach. A useful standard becomes more valuable when different participants can adopt it and exchange information consistently.

12. Relationship to Existing Frameworks

CAR is intended to complement existing sustainability and accounting frameworks. It does not replace the GHG Protocol, ISO standards, assurance regimes, or organizational reporting systems. Instead, it provides a structured computational record that can feed into those processes where appropriate.

Computational Systems → CAR → feeds into existing frameworks: GHG Protocol; ISO standards; Assurance regimes; Organizational reporting.

That design choice matters because organizations already rely on established frameworks. CAR is meant to improve the quality and portability of the underlying data, not force a replacement of everything already in use.

13. Publication Series

The CAR documentation is organized as a publication series:

• CAR Overview. This document. A public introduction for non-specialist audiences.
• Interoperability Standards (Pub 1). Alignment, conformance, security, and identity and trust architecture.
• CAR Technical Specification (Pub 2). The normative technical definition of CAR.
• Methodology and Attestation Standards (Pub 3). Detailed methodology and attestation rules.
• Governance Model (Pub 4). Institutional governance and policy structure, published as a fast-follow during the pilot.

CAR Overview (public overview, unnumbered) → Interoperability Standards (Pub 1; Ready for Zenodo) → CAR Technical Specification (Pub 2; Under peer review) → Methodology and Attestation Standards (Pub 3; Forthcoming, MVP gate) → Governance Model (Pub 4; Forthcoming, fast-follow during the pilot).

This Overview sits outside that numbered series, as a public companion rather than a normative entry in it. The CAR Technical Specification remains the technical authority.

14. Intended Audience

This Overview is written for:

• executives and decision-makers.
• sustainability and reporting teams.
• engineers and architects who want the big picture first.
• researchers and standards participants.
• policymakers and institutional stakeholders.
• ecosystem partners evaluating adoption.

The document is designed to be readable without specialist knowledge. It should help readers understand what CAR is before they move into the technical specification.

15. Current Status

CAR is under active development within the CarbonStream Nexus publication series.

The CAR Technical Specification is the normative document that defines the technical requirements. This Overview is non-normative and exists to explain the idea, the value, and the publication structure in plain language.

16. Closing Statement

Computation is becoming a major part of the world's infrastructure. As that happens, the environmental accountability of computation needs a clearer and more interoperable record.

CAR is CarbonStream Nexus's proposed foundation for that record.

“Its purpose is to make computational environmental claims more transparent, reproducible, exchangeable, and verifiable.”

Document Relationship

CAR-OV-001 is non-normative. It does not override or replace the CAR Technical Specification. Where a conflict exists between this Overview and the CAR TS, the CAR TS governs. The CAR TS remains the authoritative technical document currently undergoing peer review.

CarbonStream Nexus | Compute Accountability Infrastructure | carbonstreamnexus.com | ceo@carbonstreamnexus.com