EVIDENCE

Show the work. Label the proof.

Cade Labs does not use invented testimonials, anonymous logos or unsupported ROI. Evidence is published with a clear label so you can see what is real, what is illustrative and what is still being proved.

INTERNAL CASE STUDY

Cade Labs website migration to Cloudflare

Repository-backed
PROBLEM

Move the production website without breaking the surrounding system.

The migration had to preserve the website, HTTPS behaviour, deep routes and the existing IONOS mail/DNS setup while establishing a source-controlled deployment path.

CHANGE

GitHub → Cloudflare became the deployment path.

The repository records the migration, keeps hosting verification scripts and checks routes, canonicals, redirects, assets, security headers, robots, sitemap and branded 404 handling.

PROOF

Automatic deployment and production verification were recorded.

The migration record documents successful GitHub deployment, production route verification and preservation of the mail DNS records.

9 production routes checked before V3HTTPS and canonical redirect path verifiedMail and DKIM records preserved through the migrationRepeatable hosting verification kept in source control
INTERNAL CASE STUDY

Website quality assurance and mobile hardening

Repository-backed
PROBLEM

More routes and diagnostics created more ways for the site to regress.

Service pages, the Business Friction Check and responsive layouts all needed to remain usable without relying on a single desktop screenshot or manual spot check.

CHANGE

Browser regression became part of the repository workflow.

Playwright projects cover desktop, tablet and mobile viewports, with checks for responsive overflow, readable text, keyboard focus, target sizing and diagnostic behaviour.

PROOF

Quality checks run alongside the production build in CI.

The repository CI runs formatting checks, ESLint, TypeScript, the production build and the Playwright regression suite so presentation changes are checked as code changes rather than accepted from appearance alone.

1440 × 900 desktop browser project768 × 1024 tablet and 390 × 844 mobile projectsReflow checks at 100%, 125%, 150% and 200% text sizeKeyboard focus, target-size and mobile readability checks in the suite
LABELS

Not all evidence means the same thing.

The label is part of the evidence, not a footnote.

Internal case study

Work Cade Labs can verify from its own systems, repositories or operating records.

Client result — permission granted

External work shown only when the client has approved publication.

Illustrative example

A clearly marked teaching example used to explain a method or output.

In progress

Work where evidence exists but is not yet complete or ready to publish.

MORE PROOF, AS IT EXISTS

The evidence library will grow with the work.

Future entries can include governed automation, operating-system work and permitted client case studies. They will be added when the underlying evidence is strong enough to publish—not to make the page look busier.

Start with your own friction check