Synthetic demonstration
The website example uses invented records to show the workflow and output format. No customer data or outcome is represented.
SAVINGFOUNDING CUSTOMER OFFERLimited to the first five customers
EVIDENCE & METHOD
What is proven.
What is not claimed.
RepeatProof separates product verification, synthetic demonstration, founder experience and customer-approved outcomes. They are different forms of evidence and are never presented as interchangeable.
PRODUCT BENCHMARK6 labelled synthetic scenariosRELEASE ASSERTIONS42 required checksFOUNDER EXPERIENCE25+ manufacturing-quality yearsCUSTOMER OUTCOMESNone claimed without approval
EVIDENCE LADDER
Label every claim
at the right level.
A passing synthetic benchmark shows that a defined engine behaved as expected on labelled scenarios. It does not prove customer savings or recurrence reduction.
Versioned verification
6 labelled synthetic scenarios test expected signals, evidence traceability, decision boundaries and deterministic repeat.
Inspect the benchmark ↗Relevant experience
Founder experience supports the operating method; it is not presented as proof that the software has delivered a customer result.
Review founder evidence ↗Customer-approved outcome
Requires an agreed baseline, method, sample, limitations and recorded customer publication approval.
Open the outcome register ↗CONCISE DATA FLOW
A bounded calculation path.
A named decision path.
Exact providers, regions, retention and deployment boundaries are agreed for each customer. This summary describes the application pattern, not a universal customer configuration.
Approved historical export
The customer data owner provides only the records and fields in the signed pilot boundary.
Tenant-isolated workspace
Access is restricted to authorised members. Raw identifiers and files remain inside the controlled workspace.
Versioned calculation engine
Normalisation, retrieval, recurrence, measurement and cost rules produce source-linked evidence with confidence and limitations.
Named human review
The reviewer accepts, edits or rejects the prepared output. The QMS and authorised people retain the official decision.
ACCESS MATRIX
Least privilege
made visible.
Roles are confirmed in the engagement plan. The matrix below is the default pilot boundary, not a substitute for the customer's approved access design.
| Role | Approved records | Prepared analysis | Quality decision | Configuration |
|---|---|---|---|---|
| Reviewer / Quality Manager | Read scoped | Review, edit, reject | Authorised in customer process | No |
| Data owner | Prepare approved export | Inspect mapping | No | Data boundary only |
| RepeatProof delivery lead | Minimum scoped access | Configure and support | No | Pilot scope only |
| RepeatProof calculation engine | Process scoped fields | Prepare source-linked result | Never | Versioned rules only |
Available due-diligence evidence
Prospective customers can request the architecture and data-flow summary, role/access matrix, retention and deletion schedule, model-processing description, release and incident runbooks, subprocessor list and security questionnaire response. Certification or penetration-test evidence is supplied only when it exists.
PUBLIC OUTCOME TEMPLATE
The proof asset
every approved result must complete.
This is a publication template, not a result. A customer-approved outcome will fill every field and state the measurement method and limitations beside the numbers.
| Required field | What must be disclosed |
|---|---|
| Baseline | The agreed current preparation time, evidence-completeness measure and start date. |
| Sample size | Records evaluated, exclusions, review population and the period covered. |
| Retrieval precision | Reviewer-accepted related events divided by all displayed related events. |
| Preparation-time result | Comparable median assisted time using the same start and stop definition. |
| User acceptance | Accept, edit and reject counts with recurring edit reasons. |
| Limitations | Missing fields, selection effects, short observation period and constraints on generalisation. |
Set the measurement method
before the result.
The pilot plan fixes preparation-time, retrieval-precision, evidence-completeness and user-decision definitions before delivery.