The atomic object
This is what a client gets: one record, evidence to outcome.
Not a score, not a dashboard, not a prompt. A proof record follows one growth move from the moment the evidence was observed to the moment the change was measured, with every source and every approval attached. The example below is fictional; the structure is exactly what Brandlism keeps.
Riverside Physiotherapy · example
One finding, carried from evidence to outcome.
Baseline, decision, approval, work, rescan and result stay on one record a client can open without a login.
- 01Observe
Homepage read: no Organization markup, title names nothing local
Fetched https://example-clinic.com · HTTP 200 · 2026-08-02 09:14 UTC. The served HTML has no JSON-LD and a <title> of "Home".
Source kept · content hash recorded
- 02Find
Search and AI systems cannot tell what this clinic is or where it is
Confidence 92%. Affects the homepage and every page that inherits its title. Unknown: whether the clinic has a Google Business Profile — not connected yet.
Severity high · 12 points of Search Visibility
- 03Decide
Rewrite the homepage title and add LocalBusiness markup
Expected outcome: the clinic is named and located in results and in AI answers for its service and city. Impact 78 · effort 25 · ranked first of nine.
Ranked by expected value, confidence, effort, urgency
- 04Approve
Approved by M. Okafor (agency) · owner J. Reyes · due 2026-08-16
Done when: the title names the service and city; LocalBusiness JSON-LD validates in the Rich Results Test; a rescan no longer reports the finding.
Named approval on the record
- 05Ship
Shipped 2026-08-14: new title and markup live
Deliverable attached: the diff of <head> before and after, with the approval it was made under. Nothing published without the sign-off above.
Work evidence kept next to the baseline
- 06Verify
Rescanned the same URL 2026-08-21: finding resolved
Same target, same check. Title now "Riverside Physiotherapy · Bristol"; LocalBusiness markup present and valid. Search Visibility 61 → 73 on the same weighting.
Before and after on one record
- 07Prove
Added to the client portal and the August report
Client-visible explanation in plain words, with the limit stated: rankings and clicks are not yet measured because Search Console is not connected. That is the next unlock.
Attribution stated, uncertainty included
Measured change
Search Visibility 61 → 73, same weighting, same target
Attribution
High for the on-page change; clicks not yet measured (Search Console not connected)
Client-visible
Plain-language explanation on the portal and in the August report
What every proof record contains
- Baseline evidence and timestamp
- The exact public or connected source, when it was read, and whether it was available.
- Finding and confidence
- What is wrong, how sure we are, which surface it affects, and what is still unknown.
- Recommended action and expected outcome
- The next move, ranked by expected value, confidence, effort and urgency.
- Owner, approval, due date, acceptance criteria
- A named person accepts the work, its scope and what "done" means.
- Deliverable or completed-work evidence
- The asset or the diff, kept with the approval it was made under.
- Rescan evidence
- The same stable target, checked again.
- Measured delta and attribution confidence
- What changed, and how confidently the change can be attributed to the work.
- Client-visible explanation
- Plain words on the portal and in the report, uncertainty included.
Start your first record with a real domain.
The free proof scan reads a homepage the way the full product does and returns the first stage of a record. No signup.