# Reading the console

Everything on the dashboard exists to keep two different kinds of facts
honest at once: modeled estimates (with uncertainty) and exact retirements
(without any). This page explains each element. A public, read-only
[demo console](/demo) shows all of it with synthetic data.

## Monthly usage-phase footprint

Three charts: Water (gallons), Carbon (kg CO2e), Energy (kWh), one bar per
month.

- **The bar rises to P90**, the retirement accrual basis for every account.
- **The shade change** inside the bar marks P50, the central estimate. The
  lighter segment above it is deliberate conservatism headroom, not a
  higher belief about the footprint.
- **The whisker** spans P05 to P95, the 90 percent plausible range. It
  ships with every figure; hovering a bar shows the numeric range with
  both ends in the same unit scale.
- The estimates credit cache reads at the methodology's cached-input
  coefficient and apply conservative treatment where providers hide
  reasoning tokens; banner notices appear when the model-registry
  disclosure threshold (over 15 percent unclassified tokens) or the
  hidden-reasoning multiplier fired.

## Filters

The API multi-select and date range filter every figure on the page at
once. The cap readout shows billable tokens against your tier cap
(billable = fresh input + output + 10 percent of cached input; reasoning
tokens are a subset of output, never double-counted).

## Retirement history

Whole registry units retired per month, one panel per category. Solid bars
are confirmed retirements, the only kind certificates report; dashed
outlines are funded orders awaiting supplier confirmation. This strip is
deliberately separate from the estimate charts: retirements are exact
instruments, estimates are modeled, and the two are never overlaid.

## Credit position

Per category: units retired to date, pending fulfillment, buffer coverage,
and the carryover obligation (fractions below a whole unit roll forward to
the next close). Categories never mix; there is no combined score.

## Invoices

One local invoice per closed period, mirroring your Stripe subscription
charge. Self-serve accounts are charged by the subscription itself, never
twice. The Manage billing button opens the Stripe customer portal for card
changes, invoice history, and cancellation.

## Certificates

Each closed period's four-section certificate, downloadable as PDF and
JSON. See [Certificates](/docs/certificates) for the anatomy.

## Managed connections and Report usage

Add provider connections (Anthropic, OpenAI, Google), trigger a manual
sync for any window, remove or rotate credentials, or self-report monthly
totals. The full setup guide renders below these cards inside the console.

## Close a billing period

Operator tooling for the monthly close: aggregate the period, accrue at
P90, retire (buffer first, then supplier orders), enforce the
certificate-share floor, issue the certificate, and invoice. Every step is
journaled and idempotent; re-running a closed period changes nothing.