no-code-owner-handofflisted

# Handing off to an owner who does not code The standing constraint here: > *"He has no coding background and does not want to write code — he only clicks consent screens and > pastes secrets. Write everything for him, click-by-click."* And the delegation is genuine: > *"I permit you to do these things i don't want to do it, and don't have time to do as well… finish > it and check everything once."* So the design goal is: **the owner's total surface area is a browser, a copy-paste, and a yes/no.** --- ## 1. Do the work. Don't teach the work. Default to doing it yourself. Escalate to the owner only for things that are genuinely gated on being them: | Owner must do it | You do it | |---|---| | Click an OAuth consent screen | Register the app config | | Accept terms of service | Run the provisioning command | | Paste an API key from their account | Set the env var, wire it, verify it | | Add a DNS record at the registrar | Everything either side of it | | Approve spending money | Everything free | | Decide a price, a name, a fact about themselves | All the implementation | If you are about to ask the owner to run a command, **first check whether you can run it.** Usually you can. ## 2. The shape of a step Every step needs three parts. Missing the third is the most common failure, because without it the owner cannot tell success from silence. ``` ### Step 4 — Publish the OAuth app 1. Open https://console.cloud.google.com/apis/credentials/consent 2. Click "PUBLISH AP