Skip to main content
Trust
Measurement before claims

Operational Sustainability

AltoaX publishes operational footprint data only after internal approval, methodology review, and snapshot capture. This page is intentionally narrower than the internal operator workflow.

Publication workflow in progress
No live mutable data exposed
Public disclosure boundary
This deployment is not configured to publish AltoaX public sustainability snapshots yet.

Internal tracking already runs inside the authenticated product surface. Public publication waits for an approved monthly snapshot so this route never reads live mutable entries.

When the first disclosure publishes, it will show approved monthly totals, measured coverage, methodology versioning, and a category breakdown for AltoaX own-operations data.

Disclosure controls
How AltoaX keeps this page narrow and reproducible
  • Figures on this route come only from approved monthly snapshots, not live draft entries.
  • Measured and estimated values stay separated through review, publication, and historical storage.
  • Published totals are framed as measurement and disclosure, not reduction or offset claims.

Methodology and source boundary

Published figures stay tied to recorded methodology versions, source citations, and measured-versus-estimated coverage. The links below reflect the public source boundary for the current implementation.

Included data
Public disclosure currently covers approved AltoaX own-operation entries only: cloud and AI usage, indirect cooling water, travel, and other internal operational records approved for publication.

Client and portfolio-company data stay inside authenticated product workflows and do not publish on this route.

Rejected records never publish, and draft or reviewed-only records remain private until snapshot approval.

Estimation controls
Estimated values carry factor versions, methodology versions, and source citations so historical disclosures remain reproducible after factor updates.

Measured values remain distinct from estimated values throughout review and publication.

Monthly public disclosure includes measured coverage so readers can distinguish direct observation from estimation-heavy periods.

Publication controls
Public figures read from approved monthly snapshots rather than live mutable entries, which keeps the public route stable after internal edits continue.

Only the AltoaX public-disclosure owner can publish new snapshots for this route.

Automated provider sync and manual operator entry both land in the same internal review workflow before any public publication can occur.

Current source boundary
The current implementation uses published government and provider documentation for operational estimates plus provider usage/billing APIs for monthly activity data.

OpenAI token usage currently maps to an AltoaX midpoint energy estimate of 0.002 kWh per 1 million tokens until provider-specific energy disclosures are available.

Vercel billing imports currently preserve monthly usage and cost context; direct energy conversion remains deferred until provider-specific sustainability factors are available.