Metrics, provenance, and quality

Session span is elapsed time between the first and last supported event and can include long idle gaps. AI active time is source-reported or adapter-derived working time: for current Codex rollouts it is the sum of completed-turn durations without separately adding nested tool spans, and for Claude web exports that spell out assistant content blocks it is the union of those blocks' start and stop instants, so blocks that overlap are counted once rather than twice.

User active time and waiting time are permanently unavailable, and that is a decision rather than a gap. No supported export records how long you spent reading or typing, and waiting on the model is exactly the AI active time already shown. Producing either number would mean relabelling one you can already see, so the tiles were removed and the coverage rows say why.

Prompts, responses, tools, and agents depend on source capability. Token categories remain separate. Missing token telemetry is unavailable, not zero.

Every metric, for every provider, with the reason for each gap, is listed on the integrations page. It distinguishes a value your export does not contain — which no future release can recover — from one your export contains that we do not read yet.

API-equivalent cost is not a subscription bill. It is shown only when model identity, token categories, a dated rate table, and a valid calculation are available.

The current text-token snapshot was reviewed on 2026-07-29 against the official OpenAI model catalog, Claude Platform pricing, and Gemini Developer API pricing. It uses standard pay-as-you-go rates. It excludes taxes, negotiated discounts, tools, data-residency multipliers, long-context premiums, and cache storage time. If more than one differently priced model appears in a session, the estimate remains unavailable because token attribution would be ambiguous.

• OpenAI model and pricing catalog (opens in a new tab)
• Claude Platform pricing (opens in a new tab)
• Gemini Developer API pricing (opens in a new tab)

A metric is compared with the previous period only when both periods were fully covered and every contributing session agreed on adapter version, normalization version, quality, source, and calculation. Anything less and the comparison line reads No comparable prior-period value rather than reporting a movement that is really a change in how much of your work the export described.

The What changed panel at the top of the dashboard is built from exactly those comparisons and nothing else. It ranks them by size, narrates the three largest, and states how many metrics it held out. Two further rules keep it from overstating:

• A movement of less than 5 percent is reported as held steady rather than narrated.
• A metric whose previous period held nothing is described in words with no percentage attached, and is never ranked above a metric that has a real rate. Growth from zero is not a percentage.

An empty summary means no honest comparison was available, not that nothing happened.

Every section of the dashboard carries a disclosure stating what it measures, how it is calculated, how to read a high or low value, and what could mislead you about that section specifically. The wording lives in one registry, and the test suite fails if a section is rendered without an entry or an entry is written without a section, so the method cannot quietly fall out of a redesign.

Each chart also publishes the series it was drawn from as a table, built from the same array the chart received. Days and hours that no source described read Not available there rather than zero.

Open a session to see adapter version, normalization version, source, last import, metric quality, calculation provenance, warnings, and limitations.