How it works
The record, step by step
It is built from what was stored, not written afterward
Each line comes from something recorded at the moment it happened — the sentence the writer checked, the date, the reading, the reward — so there is nothing to compose and nothing to exaggerate.
It says who gave the permission
A testimonial written on your form carries the writer's own agreement. One you imported or added through the API carries your statement that you hold their permission — a weaker record, and it is printed as a weaker record.
It is on our address, not yours
A record a business can host is a record a business can dress up. The page is plain, unbranded, and the same for every customer.
It travels with the words
The link is on the wall, in the API and in what an assistant reads, so whoever republishes your testimonial can carry the proof with it.
Safe by design
The rule that makes it safe to have
Clear boundaries
What it will not do
Every capability page ends with this list. It is the part that says what you are actually buying.
- It is not a score, a rating of you, or a mark we sell. Nothing on that page can be bought.
- It is not proof that what the person wrote is true — only of how their words were collected, kept and published.
- It will not show what the risk reading found, or anybody's email address.
- It will not exist for a testimonial that is unpublished or whose writer kept it off websites: that address answers exactly as one that was never written.
Where it lives in the code: lib/provenance.ts · app/v/[id]/page.tsx · components/WallBody.tsx · lib/api-auth.ts
This is running now
Open a project and use it. Nothing on this page is a roadmap.