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
Ask if you can accept it before you ask if you can assign itHand offClear rules, reversible, obviously right orwrongThe product executesYou sample-checkKeepJudgment, irreversible acts, missing sources,outbound voiceYou do it or you release itThe product stops at a draftExecution can leave. Consequences stay.
What you can assign is checkable execution. What you keep is anything with consequences.

What to Hand Off, What to Keep

Hand off work that is rule-clear, reversible, and checkable. Keep judgment, irreversible acts, and anything that leaves the building.

Not every job belongs on a product. The wrong handoff is rework at best, and sent mail, spent money, or an overwritten original at worst. The cut is not “is this hard.” It is “if this is wrong, can we take it back.”

After reading, you should be able to answer:

  • What kind of work should you assign first?
  • Which four kinds stay with you even when the product is strong?
  • What do you do with work that sits in the middle?

Hand off checkable execution first

First jobs and repeating jobs should pass three tests: the rules are speakable, the action is reversible, and right versus wrong is obvious. Sorting a folder, rolling up a table, filling a template, making a small repo change — those qualify. xAI’s line is that teammates come back with finished work and pull you in only for judgment calls. That only holds if those calls were marked in advance.xai-bot

The cost is that you still write the five things and sample the process. Assign without that, and you also assigned “what counts as right.”

Keep these four

  1. Judgment and tradeoffs: the goal, the priority, whether to do it, the public voice. The product has no stance and cannot carry the consequence. See the human boundary.
  2. Irreversible acts: pay, send, delete, overwrite the original, merge to main. It can walk the steps to “waiting for you.” It cannot press the button.
  3. Missing material: the key file, permission, or definition is not in the brief. Gaps get filled. Filling is invention.
  4. Steps that need you: login challenges, face checks, one-time codes, secrets only you know. Take over. Do not “try again.”

How to grade permission is already in permission levels and human breakpoints. On a product, treat high-risk writes as a stop by default.

Split the middle

Most real work has both sides. A weekly update: roll-up and layout can leave; numbers and the claim stay. A code change: the implementation can leave; the merge stays. Company documents: retrieval can leave; sending internals to the wrong place cannot.

The split is fixed: assign the execution through the five-step loop, and write the judgment as a stop. Do not delete the stop to make it “end to end.” How to pick the first job is in pick the first job.

References

  1. Grok Bot — xAI