fastpace prices on outcomes the customer can verify from their own repo, not seats alone. This guide is the operator's-eye view of what fastpace measures, where each number shows up, and how those numbers translate into contractual guarantees on both Team and Enterprise.
Among the metrics fastpace publishes, one is the contractual backbone: audit-chain coverage. It's the percentage of AI-attributed commits in your repo's 60-day rolling window where every link of the evidence chain is present and verifiable.
An AI-attributed commit is "covered" when all three of these
primitives are present and pass fastpace verify:
The cross-cut catches anything that broke any single link in the chain. Manifest missing? Not covered. Trailer pointing at a manifest that no longer verifies? Not covered. Audit-log gap? Not covered.
Compliance auditors don't grade you on "did you produce a manifest once." They grade you on "for every AI commit you shipped, can you produce a verifiable trail." Coverage is the metric that answers that question with a single number.
| Coverage | Band | What it means |
|---|---|---|
≥ 95% | green | Audit-grade — Enterprise SLA threshold met |
80% – 94% | yellow | Procurement-ready — Team SLA threshold met |
< 80% | red | Below the Team threshold — billing pauses on Team plans |
$ fastpace audit coverage audit-chain coverage (last 60 days) 78 AI commits · 71 fully covered · 7 missing coverage: 91.0% · yellow meets team SLA (≥80%) · misses enterprise SLA (≥95%)
Same math is surfaced live in the local UI (fastpace ui),
in the org-rollup dashboard, and as the contracted metric in every
signed outcome snapshot.
A snapshot is a single signed JSON file that bundles every metric value, every contracted threshold, and the install's Ed25519 signature into one verifiable artifact you can hand to procurement or an auditor. The signature chains back to the install identity published in the trust portal — verifiable offline.
$ fastpace outcome snapshot ✓ wrote fastpace/outcomes/2026-05-13T18-44-02.json audit_coverage: 91.0% · yellow · meets team SLA signed by: install_id 7f3a91b4 · published in trust portal $ fastpace outcome verify fastpace/outcomes/2026-05-13T18-44-02.json ✓ signature valid ✓ metrics match recomputation against current audit chain ✓ entry_hash matches
Three reasons signed snapshots beat a screenshot of the dashboard:
fastpace outcome verify can re-prove the numbers
months later, even if your repo has moved on.
fastpace outcome snapshot — produce a fresh signed snapshotfastpace outcome verify <file> — re-verify offlinefastpace outcome list — list everything saved under fastpace/outcomes/fastpace outcome renewal-report — year-over-year trajectory artifact (see Part 3)fastpace outcome rate-card — generate the procurement-ready markdown quote with your current numbersfastpace outcome demo-snapshot --seed <slug> --basis team|enterprise — deterministic-from-seed fake snapshot for sales demos
Twelve months after activation,
fastpace outcome renewal-report produces a year-over-year
trajectory artifact: every signed snapshot in your history, the
monthly coverage curve, time below threshold, time above
threshold, the worst-case month. It's the document a customer
hands their procurement team at renewal time — a self-produced
proof that the rate-for-outcomes deal worked (or didn't).
Because the customer produces the report from their own audit chain, fastpace can't massage it. That's the design.
On Team plans, fastpace pauses billing if the audit-chain coverage gauge fails to clear the 80% threshold within 60 days of activation, and re-pauses on any subsequent 60-day rolling window that drops below threshold. No support ticket required — the install's local gauge triggers the pause and the org-rollup dashboard reflects it.
The pause is mechanical: a customer with a low coverage score either fixed the chain (and resumed billing) or proved the product didn't deliver (and kept the dollars). Either outcome is fine — what would not have been fine is dribbled-out monthly seat fees while the outcome metric stayed red.
Enterprise customers contract on two refundable SLAs:
fastpace verify's structural checks ≥ 99.5% of
the contracted billing period. Each 0.1% missed = 10% refund,
capped at 100% per month.
Both SLAs are computed from the customer's own audit-log + their own ticket history — no fastpace-side measurement to dispute.
Enterprise per-seat rate scales with the framework-readiness target the customer contracts to. Linear interpolation between three anchor points:
| Target | Per-seat / month | Posture |
|---|---|---|
50% | $99 | floor |
80% | $79 | procurement-ready |
95% | $59 | audit-grade |
Higher target → lower rate. Customers who commit to a stronger outcome get a cheaper seat — the math rewards posture, not the absence of it.
Outcome-pricing claims need a counter-weight: a public record of
what fastpace promised, when, and what happened. That's the
commitment ledger at
trust.fastpace.net/commitment.
Source of truth:
packages/trust-portal/src/data/commitments.json.
Each commitment carries:
id slug and posted_at datesigned_by attribution (founder)resolution block — null while open; populated with resolved_at + summary when the commitment closes as met or missed-refundedResolutions are public regardless of outcome. A missed commitment ships with the refund total disclosed and the root cause stated. The mechanism is intentional: a vendor that bets on outcomes must publish the receipts.
| Surface | Audience | What you see |
|---|---|---|
fastpace ui | The developer running fastpace locally | Live coverage gauge + status banner |
| org dashboard | Engineering/security leadership | Per-repo + rollup; missing-chain top offenders |
| Trust portal — /outcomes | Prospects, auditors, procurement | Public outcome spec, target bands, SLA mechanics |
| Signed snapshot | Procurement, auditors | Point-in-time signed JSON · verifiable offline |
| Renewal report | Customer's renewal committee | 12-month trajectory · time above/below threshold |
| Rate card (CLI / admin / /pricing download) | Prospect's procurement PR | Markdown quote with the math + verification commands |
| Commitment ledger | Public | What fastpace promised + what happened |
