GENESISCODE DOCTOR AI
THE GENESIS REPAIR GUIDE

What do we repair?
Understand the why.

Look up a website issue in plain language. See what it means, what could go wrong, and what evidence would prove a repair worked.

REPAIR KNOWLEDGE MAP
UnderstandWhat the finding meansApproachHow a repair is scopedVerifyWhat would prove it worked
40plain-language explanationsacross 8 diagnostic categories

40 matching topics · 40 in the guide

Why it matters

A change can appear successful while leaving the original cause unresolved or damaging a different feature.

What Genesis checks today

One scan, a generated patch, a paid invoice, and a delivered file do not establish a verified repair.

How a repair would be approached

Bind the original finding, authorized change, exact revision, test results, and rollback instructions to one repair record.

What would prove it worked

Only completed, attributable before-and-after and preservation tests justify a verified outcome. Missing evidence stays Not verified.

Backend assessment only · not accepted

YOUR RECORD, NOT A SALES CLAIM

“Found” is not “fixed.”

A verified repair record must connect the original issue to the exact authorized change and the tests that followed. The public diagnostic does not currently supply a verified repair-completion record.

1

Observed

A time-stamped finding with its scope and limitations.

2

Proposed

An exact repair and price still awaiting the required checks and approval.

3

Applied

Evidence of a change—not proof it worked.

4

Verified

Recorded before-and-after, regression, and preservation tests.

When evidence is missing, the correct label is Not verified—even after a payment, file delivery, or successful page load.