01 / Context
First understand what must not break.
We record the goal, users, decision owners, access constraints, and unknown areas.
02 / Evidence
Separate facts from assumptions.
Every material conclusion needs a source, coverage, and a clear effect on the plan.
03 / Change
A small verifiable batch.
Stage, backup, acceptance criteria, and rollback are defined before a risky change.
04 / Handoff
The result does not depend on team memory.
Code, settings, decisions, checks, and open questions stay understandable to the next practitioner.
Tell us what the site needs.
A goal, the current difficulty, and an optional website address are enough. Do not send passwords, keys, or private exports.