Dako's AI Builder Notes
⌘K
中EN
System
Color theme
Changsha HubOffline
大可 Dako
大可 Dako大可 DakoAI Builder · Agent PractitionerTurning AI into working software. Practical notes on agent engineering, vibe coding, and commercial delivery.
Platform links coming soon
If you cannot see the process, you cannot accept the result01WatchPlan, permission, andintermediate artifactsstay visible02StopIrreversible, uncertain,or failed checks stop therun03Take overSteps only you can do — donot let it force them04Release againContinue only after thestop is handled✓ Stopping is how the job finishes, not a lack of trust
You are not a spectator. You stand at the points where the work can still stop.

Watch, Stop, Take Over

An assignment needs a visible process. Stop before irreversible acts, take over logins yourself, and do not continue past a failed check.

Plenty of people assign and walk away, then come back for the last paragraph. The last paragraph often says “done.” You never saw which file moved, where it was unsure, or whether the original was overwritten. No visible process means no acceptance — only trust.

After reading, you should be able to answer:

  • What three things do you watch in the process?
  • When must you stop instead of “let it continue”?
  • How is taking over different from watching, or from taking the job back?

Watch three things, not the tone

  1. The plan: what it will touch, what it will not, how done looks. Releasing without a visible plan throws away the cheapest intercept in the five steps.
  2. Permission: is this step read-only, a reversible write, or irreversible. Official guidance is blunt: once you pick a folder, the product reads and changes that folder. Outside it is out of bounds by default.codex-quickstart
  3. Intermediate artifacts: drafts, change lists, items waiting for you. Grok Bot puts sensitive acts through review before they run. The durable judgment: show the irreversible step, then let a person click.xai-bot

A friendly tone and a moving progress bar are not what you watch. You watch the check.

Three kinds of stop

  • Irreversible: pay, send, delete, overwrite the original, merge to main. Stop at “waiting for you.”
  • Uncertain: sources do not match, permission is missing, two definitions appear. Stop and ask. Do not guess.
  • Failed check: numbers do not recompute, tests are red, a required column is missing. Repair before moving on. Pushing while broken turns every later step into fake progress.

Stopping is not distrust. It is what you keep applied to the process. The engineering ladder is in permission levels and human breakpoints.

Take over the step, not the whole job

Login challenges, face checks, one-time codes, secrets only you know — there is no “try again” for these. You do the step, hand control back, and let it continue from the stop. Do not punish a designed stop by taking the whole job back.

When the process is opaque, see debug the process first. The red-line list is in red lines.

References

  1. Grok Bot — xAI
  2. Codex / ChatGPT quickstart