Expert guidelines
How good Patches are done.
Clients are builders, not specialists. Your job is to make the outcome obvious and the work safe.
Write outcomes, not diagnoses
Describe what will be true when you're finished, in language the client can verify themselves.
Keep your technical assessment in the private field. Full solutions aren't shared before hiring.
Respect scope
Fix what was agreed. If you spot something bigger, say so and propose it as a separate Patch.
Handle access carefully
Work only in the Patch workspace, keep changes isolated from the live product, and never ask for credentials outside HumanPatch.
Communicate while you work
A short update at the start, one when the cause is clear and one when testing is done is usually enough.
Plain-language summary for an early version of HumanPatch, not final legal text.