PUBLIC EVIDENCE PACK · EXAMPLE ONLY

See the paperwork
before the pitch.

These artifacts show the minimum evidence Computavia expects before production traffic. They are examples—not an offer, supplier commitment or service guarantee.

00 / REFERENCE OFFER PREVIEWFIELDS, NOT TERMS

What a signable offer must identify

This public preview is deliberately unpriced and non-executable. A real quote is incomplete until every field below is named, dated and approved.

Quote ID / version
Assigned when issued · version controlled
Seller legal entity
TO BE NAMED BEFORE SIGNATURE
Supplier / model
TO BE VERIFIED IN ROUTE SCHEDULE
Region / retention
TO BE EVIDENCED IN WRITING
Failover behavior
NO DEFAULT SUBSTITUTION
Price / currency
WRITTEN USD QUOTE REQUIRED
Validity / capacity
DATED WINDOW REQUIRED
DPA / SLA status
NOT EXECUTED
01 / SAMPLE ROUTE SHEETSUPPLIER PENDING

U.S. protected planning route

Commercial status
PLANNING · SUPPLIER PENDING
Model scope
Named family and version bounds in final schedule
Processing region
Requested: United States; provider evidence required
Data eligibility
Non-sensitive business data only during qualification
Retention / training
Not represented until supplier terms are verified
Minimum volume
100M tokens/month planning assumption
Service objective
To be negotiated; no public SLA applies
Failover
Not configured in the planning environment
02 / SAMPLE QUOTENON-BINDING

100M-token planning scenario

$—Final price intentionally withheld until a supplier route is verified.
  • Assumption: 70% input and 30% output tokens.
  • Prices shown in the planning book are directional USD estimates.
  • Taxes, cache pricing, support and implementation are excluded.
  • Only a written quote names the supplier, model, route, price and validity period.

Invoice, taxes, payment instructions and authorized seller details are supplied only in the approved commercial package. This sample requests no payment.

03 / BENCHMARK METHODSIMULATION DEFAULT

Measure, label, then decide

  1. Declare mode.Every result is labeled SIMULATION or LIVE PROVIDER.
  2. Freeze the prompt set.Use representative, non-sensitive tasks and a documented scoring rubric.
  3. Record the route.Capture model, region, time, latency, throughput and error rate.
  4. Separate evidence from promises.A benchmark is not an SLA or guarantee of future capacity.
  5. Make it reproducible.The signed report must include prompt-set version, sample size, date, model identifier, parameters, region and raw-result retention location.
NEXT STEP

Ready to scope a real route?

Review what sign-in creates, what information we need and what remains unverified.

Review qualification steps
SAMPLE INVOICEReview the invoice layout and billing boundaries →BENCHMARK METHODReview prompts, repetitions, percentiles and evidence →ELIGIBILITY MATRIXCheck which workloads are currently excluded →REQUEST GOVERNANCESee each status, owner and approval gate →