Confidence should be traceable
Every important claim needs a source, test condition or visible label.
Important claims are separated into observations, calculations, assumptions, recommendations and unresolved requirements so a planning value is never presented as a proven outcome.
Operational ownership
The handover should make responsibility easier to see.
- 01 / Owner
- Name who controls updates, access, recovery and incidents.
- 02 / Record
- Make versions, tests and handover evidence visible.
- 03 / Exit
- Keep portability and supplier boundaries written down.
Five classifications
Observed claims come from a dated source. Calculated figures show their inputs. Assumptions are planning choices to test. Recommendations explain the preferred option. Open items identify evidence required before an order.
A high-value infrastructure claim without a source, calculation or visible qualification should not influence the purchase.
Change record
A controlled change leaves an evidence trail
- Request Reason, owner and affected service.
- Test Focused acceptance and rollback plan.
- Approve Named person accepts the change.
- Record Version, date and result recorded.
Look behind the claim at the operating record.
Management, recovery, evidence and physical serviceability make responsibilities easier to inspect at handover.
Benchmark conditions matter
Model, quantisation, runtime, driver, prompt, context, output length, batch, concurrency and hardware configuration all affect results.
A credible result states those conditions and retains the summary evidence. No tokens-per-second figure is claimed until the exact system has been tested.
Recovery boundary
Recovery spans equipment, configuration and business data
- Equipment Hardware fault and warranty route.
- System Build record, settings and secrets.
- Data Backup, retention and restore authority.
- Service Fallback, incident and return to use.
Commercial data expires
Supplier prices, stock, exchange rates, API prices, marketplace terms and competitors can change quickly. Pages show a review date and high-risk claims require monthly or pre-campaign checks.
A customer quote uses a fresh supplier position, not a value copied from an old page.
Exit path
Ownership should preserve a practical route out
What still requires confirmation
OEM terms, whole-system warranty, reference benchmarks, customer demand, support capacity and any UK integration partnership remain commercial gates.
Treat each item as unresolved until it appears in a current quotation, test record or signed agreement.
Questions answered
Straight answers to common questions
Are the package prices final?
No. Displayed figures use dated supplier inputs and explicit allowances. A final order needs a current written quote.
Where are the performance benchmarks?
They will be published only after the exact reference configurations pass the documented protocol.
Do you have customer case studies?
No customer case studies are currently published. Any future case study must identify the real outcome, system and operating conditions.
Continue the decision
Useful next steps
Next decision
Turn this guidance into a testable requirement.
The brief asks about workload and operating conditions - not just budget.