Trust verdict · coverage, gaps, and one fix
Can I trust this number?
—
—
—
Raise coverage — highest gain first
Other inputs that sharpen this result
What is unattributed, ranked by money
Next action
—
AI FinOps
Import a provider export and this page names how much of your AI spend is recoverable, what to do first, and how far to trust the number.
Bundled synthetic example
Did what we committed to work?
No track record on file: this browser is keeping no period. Importing one provider export keeps the month it covers and starts the record.
Modelled recoverable AI spend · USD per month $51,254
Summed over the 5 of 5 departments carrying a completed FinOps score for 2026-06-01 to 2026-07-01. Unscored departments contribute zero and are never extrapolated to. Modelled potential, not realized savings.
Move Atlas Platform's short, low-context requests to the standard modelAttested finops-recoverable-attestation/1.0.0 — the headline above is the one figure this region states, on the monthly basis of record · confidence medium · provenance 5 of 7 operands declared by the export, 2 derived here · coverage 5 of 5 departments scored. Each carries its assumption in tests/fixtures/finops-consolidated-answer-attestation.json, and a drift in any of the four fails by naming it.
Analysis readiness
Reading Resolving one annual figure, the benchmark behind it, and the action it implies.
Resolving the annual figure from the analyzed scenario…
Bundled synthetic example Every figure in this briefing is modelled in this browser from invented provider-export records — not your spend, not a realized saving.
Analyzing the bundled provider export selected in the chooser below.
Checking that figure against the analysis benchmark…
The answer is resolved locally, from the analysis this page already loaded.
Provenance is stated with the figure, from the analysis's own signal names.
Yes for an illustrative scenario recommendation; no for an organization-specific savings commitment.
Readiness is calculated from four required evidence categories.
Current evidence is limited to bundled synthetic scenarios.
No conclusion about your organization is supported.
The prioritized illustrative action is read from the bundled scenario's own next-step record.
Ranking the recommended actions…
Evidence behind the recoverable AI spend answer. Illustrative only, from hand-authored synthetic cohort boundaries rather than your own export: Your AI spend is in the most expensive quarter of organizations like yours, at $38.63 per successful task for June 2026. $51,254 of that is modelled as recoverable. Atlas Platform is driving the increase. Moderate confidence. Hand-authored synthetic cohort boundaries.
Bundled synthetic example · nothing of yours needed
Bundled synthetic example Illustrative — invented data for an invented company, not your spend, customer data, or realized savings.
Illustrative only, from hand-authored synthetic cohort boundaries rather than your own export: Your AI spend is in the most expensive quarter of organizations like yours, at $38.63 per successful task for June 2026. $51,254 of that is modelled as recoverable. Atlas Platform is driving the increase.
$51,254 · 33% of analyzed spend
$51,254 of $154,500 analyzed. A modelled ceiling on what re-routing this work could save — not money already saved. Modelled, not graded: the rubric has scored $143,500 of the $154,500 in scope, and this figure is taken over all of it.
Peer comparison unavailable
Benchmark fit has not been evaluated. Synthetic cohorts are privacy-preserving and do not imply access to customer, provider, or HRIS data.
Most expensive quarter · $38.63 per successful task
Cost per successful task for June 2026. 0th percentile for cost efficiency among 40 synthetic peers, compared with organizations that declared the same size and industry — Enterprise · 2,000+ employees · Software-as-a-service. A quarter of that group spends less than $18.40 and a quarter spends more than $31.50 per successful task, so this organization is in the most expensive quarter, measured over 4,000 successful tasks. Lower cost per successful task is better. Published band name for this quarter: Bottom quartile.
Atlas Platform
Atlas Platform contributed +$34,500 of the +$39,200 change (88% of it).
Do this first, before any spend cap is set. What was actually measured, and which input was not checked? Promoted to rank 1 by clause unchecked_basis under destination-priority/1.0.0: the finding's confidence carries one limit, so the basis is checked before a spend cap is committed.
Is the trend a one-off? See the period-over-period comparisonThe five lines above as plain text — the figure, what to do first, the department driving it, and the label saying which dataset they are as of. Aggregates only: no row, no filename, and nothing leaves this tab.
Your export · headline contract
Your export · period-over-period movement
Your export · brief completeness
Spend we can stand behind92.9% of spend in scopeThis is the share of spend classified reliably enough to act on; a higher share is better.as of Bundled synthetic example · nothing of yours needed · June 2026
Coverage: $143,500 of $154,500 of spend in scope sits in departments the rubric scored. Grade: high coverage tier — At least 80% of imported spend sits in departments the rubric scored. Residue: $11,000 of that spend has no scored query, the largest single block of it in Ember Studio. All of it as of Bundled synthetic example · nothing of yours needed · June 2026.
Record and verify a savings commitment — go to Act and verifyScope: the share of in-scope spend the rubric scored. Whether this analysis is ready to circulate is a separate question, answered below.
Circulation decision · bundled analysis only
Scope: the finding, comparison, and first action below. It is not a claim about how much spend the rubric scored.
Atlas Platform is the first intervention priority because over-provisioning is its largest recoverable cost line.
Atlas Platform scores 71, 10 points above the synthetic enterprise SaaS cohort median of 61 under rubric literacy-mix/1.0.0.
First, in Atlas Platform: enable automated down-routing for short, low-context prompts. The bundled example ranks it first on $10,650 of recoverable_spend_usd over 25 Jun–25 Jul 2026 — a modelled figure from invented records, not realized savings.
High confidence — 760 sampled queries, current through the source-period end; synthetic evidence only
Source period 2026-06-25 to 2026-07-25 — hand-authored bundled provider aggregates and org mapping; not live provider or HRIS data
Prompt text is excluded from this circulation decision. Provider-level rows are excluded; only bundled synthetic aggregates are in scope.
Executive briefing payload
Briefing claims generated locally
Open or share this exact printable briefing
Hand-authored synthetic cohort boundaries Moderate confidence
This month · evidence, action, and the checkpoint
Bundled synthetic example Invented review, action, and verification records for an invented company. Not your spend and not realized savings.
This step and its checkpoint are composed from what this browser holds, and from the bundled synthetic example when it holds nothing.
Evidence behind the recoverable AI spend answer. Recoverable spend: $51,254 · 33% of analyzed spend. Do this next: Open the recommendation evidence. Source: Bundled synthetic example · nothing of yours needed.
Example result
Bundled synthetic example Illustrative — invented data for an invented company, not your spend, customer data, or realized savings.
33% of analyzed AI spend is recoverable AI spend
$51,254 in recoverable AI spend for the reporting period
literacy-mix/1.0.0, weighted by each department's spend.Where each figure came from: unmarked values — the department names, the reporting period, and the record counts — are read straight out of the example's export files. Every marked figure below says whether this page derived it or could not find it, and opens to show the working.
Correct a derived name or figure
The answer: 33% of analyzed AI spend is recoverable AI spend. 14 of the 16 names and figures below were derived on this page rather than read from the example's export files.
| What the figure is called | What it says |
|---|
Confidence in this brief is bounded by how much of it was derived: 88% of it still is (14 of 16). Nothing below has been corrected by a reader yet.
33% of analyzed AI spend
$51,254 of $154,500 analyzed · 5 invented departments · 2026-06-01 to 2026-07-01 (end exclusive).
$51,254 in the reporting period
A modelled routing scenario over invented departments — a ceiling on what re-routing could recover, not realized, invoiced, or promised customer savings.
Bottom quartile
Bottom quartile · $38.63 per successful task
Synthetic comparison against an invented peer cohort; lower cost per successful task is better. This is not customer performance or realized savings.
A full band behind
Atlas Platform is a full band behind Boreal Support on cost per successful task.
Synthetic cost-per-successful-task comparison across the invented company's own departments — Boreal Support, Cinder Research, Quartz Analytics, Ember Studio, Atlas Platform — not customer performance or realized savings.
B · 85 of 100 · literacy-mix/1.0.0
$143,500 of $154,500 in-scope invented spend was scored — high coverage, 4 of 5 invented departments, 141 of 144 synthetic prompts classified. Not graded: Ember Studio. At least 80% of imported spend sits in departments the rubric scored. Synthetic prompts from an invented company, scored by a published rubric — not customer behaviour and not realized savings.
Pilot lower-cost routing in Atlas Platform, the top-spend invented department. Cap the pilot at $51,254, then compare it with a similar period.
Accountable role: Platform Engineering Lead
0.85 of 1.00 · moderate
Coverage 1.00 — all 15 bundled example records were analyzed and all four required aggregate inputs were present — less 0.15 because the rank-1 routing candidate's call shape could not be verified. Coverage asks how much of the data was read; this score also asks how much of the recommendation was checked, which is why it sits a band below coverage.
Estimated · $39.81 per successful task · Bottom quartile
Modelled recoverable range $20,772–$49,854 a month against Enterprise · 2,000+ employees · Software-as-a-service (most expensive quarter of the cohort). Modelled · every declared fact used as given. Estimated from declared facts and published assumptions — not measured from your usage, not verified against an invoice, and not a realized saving.
Fills every panel below with six invented months. No file is needed.
Choose your export files. They stay in this browser and are not uploaded.
Opens the printable one-page sheet on this same Bundled synthetic example, with the same recoverable share and scenario. Invented figures, not your spend; nothing of yours is read, uploaded, or stored.
Forward this address to open the figure where it is stated: /evolution.html#workspace-answer
Estimated: we spend $39.81 per successful AI task — Bottom quartile, the most expensive quarter of the cohort. Lower cost per successful task is better.
Estimated recoverable: $20,772 to $49,854 a month, modelled from these five declared facts — not a measured, invoiced, or realized saving.
Next: move one month of standard-tier traffic that does not need the tier to a cheaper one, then check the invoice against this estimate before booking anything.
Rung 1 of 3 · Declared · you are hereRung 2 of 3 · EstimatedRung 3 of 3 · Verified
A declared fact supports a shared starting point — what your org says is true of itself, written down where everyone can see it. It does not support a figure of yours, because nothing on this screen has been modelled from your answers yet: the five facts above are still the bundled example's.
One step up: answer the five facts above and press "Estimate from these five facts" to reach Estimated.
No readiness benchmark has been taken for this analysis yet.
Nothing to guide yet: no analysis has been read.
The claim above and its inputs are quoted here once the analysis has been read.
Where to go next · 3 destinations
Recoverable spend this quarter $16k
Evidence for the headline figureConfidence and source are not available until the Bundled synthetic example is prepared.
Next step · one of three doors
Ranked from the Bundled synthetic example The order was computed from six months of invented data, not from your spend.
No destination is ranked from the Bundled synthetic example.
One destination is open at a time. The answer above stays available while you work.
Now showing
Is our AI spend classification trustworthy enough to act on?
Evidence · destination
Departments · destination
Departments moved to their own screen: open this department’s screen
Act and verify · destination
Local synthetic demonstrations. No real data is entered, uploaded or transmitted — every figure is computed locally in this browser from invented records.
The guided department detail moved: open this department’s own screen
Ready · Page status
Bundled synthetic example ready The verified invented example is shown above.AI literacy
unmeasured
Score not available yet
Coverage · share of spend graded
Sampled-spend coverage not available yet
Confidence in this letter
Not established yet · no scored sample read
Under review · no letter published
Why this letter: no scored sample has been read, so no driver can be named yet.
Action not available yet
Fills in once a scored query sample is read.
No portfolio combined · every provider in one answer
Result not available yet
Benchmark not available yet
Impact not available yet
Confidence not available yet
Action not available yet
Provenance not available yet
FinOps briefing · headline
Next step not available yet
Not decision-ready
Peer benchmark
Benchmark not available yet
Trust verdict · in one line
Confidence not available yet
Prioritized action
Action not available yet
These panels are progressive-disclosure support, not primary content. Each answers a narrower question than the one above; a panel that cannot be computed still names the one input that would answer it.
Bring your own exports · browser only
One provider export is enough to get a FinOps briefing. Add a second, equal-length period to compare spend across time, and an org mapping to put your own department names on it. Three steps: choose files, check the mapping, read the briefing.
Start here · one question
Choose the provider you pay above. This panel then names the one report to pull, hands you a starting file for it, and gives you one next step. Nothing is uploaded either way.
Contracted rates · synthetic, this tab only
Declared rates are synthetic and held locally only: nothing is uploaded, no credential or contact detail is accepted, and no live provider connection is made. One record per line — model, unit, rate, effective date, source label — or paste a JSON array of the same five fields. Accepted units: usd-per-million-input and usd-per-million-output. A line that cannot be read is handed back with every other problem in the paste, and none of them are applied.
No contracted rate is declared for a destination this analysis prices, so every one of them is priced at the published list — a ceiling, not your contract.
Start with one file
Use your provider export for this decision. One provider period export — CSV, TSV, or a v1 JSON envelope — is validated and analyzed in this tab. You do not name the provider: which console the file came from is read from its own columns, and if it cannot be read the panel below says which importer it is nearest to and what was missing.
The Bundled synthetic example is active. Choose your provider export to answer this question with your own spend.
Evidence preflight · bundled local example
Not yet classified · No evidence has been validated. Processing stays local to this tab; no file is uploaded or retained.
Checking evidenceResults will appear after local validation.
Prioritized next actionWaiting for the evidence check.
Evidence is processed locally in this tab. Incomplete query evidence limits classification confidence.
Compatibility contract is available when this client-side demo starts.
Full static contract, normalization rules, fixtures, and failure behavior: native provider export contract v1.
Bedrock, Vertex AI, Azure OpenAI · browser only
Check a bundled example against the published contract without a credential, a connector, or a single network request. Your own export does not belong here: drop it into the one import above and it is recognized from its own content.
Contracts are available when this client-side demo starts.
No export has been checked yet. Choose a bundled example or one of your own export files, then run the check.
Recognition score · reproducible, local, browser only
Every bundled example below is a labelled fixture with one expected score. Choosing one recomputes that score in this tab from the published provider contracts: the same example always produces the same number, and every point of the number is listed under it.
The recognition score for the selected bundled example appears here when this client-side demo starts.
Your own export · read in this tab
Read a bundled example below and the answer, the confidence behind it, and the one thing to do about it appear together. Your own export goes through the one import at the top of this panel, which recognizes the provider from the file itself.
No export has been read yet. Choose the provider you exported from, then drop a file here, pick one with the file control, or read a bundled example.
The rate table and the recognition evidence appear here once an export has been read.
localStorage keys on this origin: shiplog.finops.workspace.v1 (consent, periods, commitments) and shiplog.finops.journey-snapshot.v1 (derived figures and references — never raw rows or prompt text). Clear them with Discard all files and results above, or by clearing this site's data.fetch, no beacon, no socket, no form post — and the page is served with connect-src 'self', so the browser refuses cross-origin requests from it.Enforced, not promised: a test drives this import with every browser transport replaced by a recorder and fails the build if one is called.
Import your provider export
Drop the file anywhere on this page, or browse for it below. Any supported provider export is recognized from its own content — you are never asked which console it came from.
This import reads two files, and each one answers a different half.
Spend export · Not imported yet
Conversation export · Not imported yet
Required: at least one provider period export, as CSV, TSV, or a v1 JSON envelope. Optional: an org mapping for your own department names, a query sample, and a Shiplog delivery-history JSON export if the releases you want spend compared against live in another install. Choose them together or add them in batches; every provider period must come from the same source.
Choosing again keeps the files that already loaded. Discarding drops every file you chose and any result with them, and restores the Bundled synthetic example.
The full package contract, including the unsupported-package path and what happens to partial, stale, malformed, and reordered data: provider export package contract.
Not read here, and what to bring instead:
The full source contract, including attribution, bucketing, sampling bounds, and partial, stale, malformed, and reordered behaviour: organizational query-source contract.
Invented sample prose only. Downloads from this tab; nothing is uploaded.
This is not the import. It reopens a briefing this page already wrote: choose a FinOps briefing JSON file this page exported. It is read in this browser only — nothing is uploaded, and nothing is saved after you close this tab. It opens read-only below the current briefing and never replaces it.
Your track record
The whole record lives in this browser, on this device, and nothing about it is uploaded. Exporting writes a file this tab builds; importing reads a file you choose, in this tab. Neither one sends anything anywhere.
No period is kept in this browser yet.
From your own imported evidence
Every rule above — what makes a record admissible, how a partial floor is summed, the priority order that picks the single next action, and why a peer comparison is never measured here: partial evidence policy.
What each adapter declares, including its schema version and its behaviour for partial, stale, malformed, reordered, and mixed-currency exports: multi-provider intake contract.
Before you combine them
Judged from a bundled sample portfolio Invented delivery counts and provenance labels — no cost, no account, and nothing of yours. Your own files are judged by the panel above.
Three of the four samples cannot be combined. Each one fails differently, and each names the one action that recovers it.
Every term above — evaluation unit, period alignment, coverage, comparability, the closed field set a portfolio may carry, and the rule that picks the single next action: portfolio comparability contract.
The full schema, the versioning rule, and what happens to partial, stale, malformed, reordered, and period-incompatible exports: Shiplog delivery-history contract.
Step 2 · check the mapping
Reviewing
| Your column | Becomes | Proposal | Sample from your file |
|---|
Step 1 · what your export carries
Read in this tab from the file you chose. No credential, no account, and no connection: nothing here needs a live provider login, and no cell of your file is shown, exported, or stored.
From your provider export
Limits
Next action
Optional. Your provider export is not re-requested, and this result stays on screen while the new file is read.
Trust verdict · coverage, gaps, and one fix
—
—
—
Raise coverage — highest gain first
What is unattributed, ranked by money
Next action
—
—
—
—
—
—
—
The question this answers
The answer, and how far it reaches
—
Confidence unavailable —
—
—
Prioritized next action
—
—
—
—
Keeping this briefing
Derived values only. Nothing is kept until you turn this on.
Per-model overspend
Recommended department action
Waiting for an imported file.
Only column headers, one sample value per column in the mapping step, declared contract fields, and aggregate totals are read into this page. No other cell value or record identifier is rendered, announced, or written to an export, and your file name appears only as the provenance label on your own result.
Supporting evidence · read after the finding above
Material trend
Peer benchmark
Progressive disclosure
Expand a department finding to inspect impact, trend, confidence, and provenance in that order.
Want to go through this briefing — or your own numbers — with a person?
Only the work email address you type is submitted. No imported file, figure, column value, department name, or prompt text is attached.
Reopened from a file · not the current analysis
Restored from this browser · not the current analysis
Coach one prompt · browser only
Grading a single prompt has its own page. Paste a prompt, or the few turns around it, and grade it against the same rubric this page grades an imported corpus with. The bundled synthetic example is graded there on arrival, so a real result is readable before anything is pasted, and the text stays in that tab: nothing is uploaded, stored, or attached to your organization’s grade.
Next step
Everything above is computed in this tab. If you would rather go through these numbers with a person, request a Shiplog follow-up: submitting sends one thing, the work email address you type.
Your email address is still in the field, and nothing from your analysis was sent. Try again in a few minutes — the briefing above is unchanged and stays until you refresh.
Next, while you wait: open the one-page Executive FinOps briefing — the same figures, built in this tab and formatted to print.
Illustrative figures · invented sample These figures use invented example data. They are not your spend or realized savings.
Example recommendation
Use a bounded gateway rule while leaving high-value prompts unchanged.
Your grade
Prompts of yours behind this grade 0 imported · 25 needed in one department
Import a prompt export to grade your own departments. Until then every panel shows the Bundled synthetic example.
Bundled synthetic example
Classifier agreement
Scoring the labelled sample…
Recompute it: the labelled queries are in the published corpus, which states who labelled them and how, and they are scored by src/finops-classifier-agreement.js.
A local import carries no peer organizations, so the comparison stays the bundled cohort's.
Bundled synthetic example
The full comparable-peer method — the published contract finops-peer-cohort/1.0.0 and its synthetic reference snapshot, the eligibility rule, the three ranked metrics, the percentile and quartile arithmetic, and the trust labels behind the single prioritized action — is loaded when this panel is opened. It contains no customer data and is never changed by an import. If it does not appear, read it directly: the comparable-peer method record.
The Bundled synthetic example's lowest-scoring team, drawn from invented prompts.
Bundled synthetic example
Spend against shipped delivery
Department evidence moved: open this department’s own screen
The department fix pack moved: open this department’s own screen
Monthly action decision
The monthly department decision moved: open this department’s own screen
Your plan
$0 planned: no move has been committed at a stated scope.
Routing slate
No analysis has been read yet, so there is no routing change to rank.
Routing score
Nothing has been committed in this browser, so there is no prior period to score a routing policy from and no follow-up period it is answerable for.
Bundled synthetic example
AI spend · period
unmeasured
–
Across all providers
Recoverable spend
unmeasured
–
Down-routing, training, and leakage
High-value share
unmeasured
–
Of scored spend
Peer position
unmeasured
–
Published synthetic peer cohort
Next step from this comparison
Supporting metrics
Method and cohort
The department priority drill-down moved: open this department’s own screen
Decision 1 of 3 · intervention
Lowest eligible performance score first. Unavailable samples are not scored or ranked as poor performance.
Sample provenance not available yet
Open this department’s own screen
Selected department
Department results will be available after the Bundled synthetic example is prepared.
–
Priority 01 · recommended intervention
A recommended intervention will be available after the Bundled synthetic example is prepared.
Why this action: Diagnosis not available yet
Decision 2 of 3 · trajectory
Comparison not available yet
Decision 3 of 3 · comparator & evidence
Peer comparison not available yet
The department spend mix moved: open this department’s own screen
Quality engine
Spend split by what the prompt was actually asking for, not by token count alone.
Spend mix not available yet
Finance leader action portfolio
The ranked recommendation leads; related findings stay available as supporting evidence.
No actions counted yet
Defensible evaluation · static fixture
Every point maps to a labelled criterion, evidence statement, and documented weight assumption. Unsafe content cannot be averaged into approval.
Bundled synthetic fixture · deterministic rubric · no stored prompts, credentials, customer data, or live provider calls.
No fixture scores read yet
Privacy & compliance
Prompts pass through redaction before any judge model or score record sees them. Structure survives; identity and credentials do not.
Sample data only This tab renders hand-authored sample data. No production gateway, HRIS connection, customer prompt, or telemetry store is read by this page.
Gateway unavailable until the bundled sample starts.