The KAGAMI mark КАГАМИ
kagami.bg/academy · lesson · machine-readable viewVERIFIED 2026-10-01 · UPDATED 2026-10-01
IDENTITY
module
KW W3 · Delegation & Effort
series
KAGAMI Way · Track W — Method
level
Intermediate
duration
~10 min
trust_label
VERIFIED 2026-10-01 (official model docs and help-centre article) · UPDATED 2026-10-01 (generalised for publication; model line-up and effort levels refreshed)
language
human view: en · bulgarian edition: /academy/moduli/KW_W3_Delegation_Effort.html
previous
KW_W2_Chain_Pressure_Stages.html · The chain: from conversation to artifact
next
KW_W4_Conventions_Session.html · Conventions & session
PURPOSE

Defines how work is delegated across model tiers and how much effort a task deserves. Five laws of delegation act as a hard fuse against irreversible actions (moving, deleting, sending). Human-in-the-loop (Law 4) is the core control: no agent decides alone on anything irreversible.

KEY CONCEPTS
COMMANDS / PATHS
CHECKLIST
NEXT MODULE

KW_W4_Conventions_Session.html · Conventions & session · offer: Quick experiment (kagami.bg/stalbata/)

SOURCES
TAGS
delegationhuman-in-the-loopeffortmodel-choicetoken-economysub-agents
VERIFIED · 01.10.2026 UPDATED · 01.10.2026

Delegation & Effort: 5 Laws for Working With AI

How you split work across models, and how much “effort” each task deserves. The five laws of delegation are a hard fuse against irreversible mistakes — moving, deleting, sending. The core is a human in the loop: no agent decides alone on anything irreversible.

⏱ ~10 min Intermediate Method Delegation · Effort
Claude (chat or Cowork)🌐 global model
🔄
UPDATED · 01.10.2026 — what changed (summary)
The lesson was generalised for publication: the method (the five laws, the human in the loop, the effort levels) is kept, and internal details were removed. The specific case was replaced with a neutral example. Models and effort levels were checked against the official documentation as of this date.

01What you will learn

02Before you start

03Steps

  1. Why we need laws

    When you hand work to AI helpers, the costliest mistake is not “a bad paragraph” but an irreversible action in the wrong direction. A typical trap: an automated helper tidies a temporary folder and saves its own draft notes, while the only copy of an important file stays there and is wiped at the next clean-up. The system “saves” the junk instead of the treasure. The five laws stop exactly that.

  2. The five laws

    LawWhat it says
    1 · No one judges above their levelThe light model WATCHES (counts, flags, does not touch). The strong one DECIDES where. The mid-tier one MOVES to a given address.
    2 · The executor does not guess, it is given an addressThe order contains an exact target folder, not “decide where it belongs”. The executor is an archivist, not a matchmaker.
    3 · Closed listMove only into places that already exist. No new places are invented.
    4 · Human in the loop — mandatoryThe executor reports “I will move A→X, B→Y” and WAITS for an explicit “yes”. No confirmation, no irreversible action.
    5 · Save the treasure, not the junkImportant things leave temporary storage for the permanent folders. Leftovers of the draft process do not enter them.
    ⛔
    Law 4 is not politeness, it is a fuse
    A move is irreversible for the process. So report the intent, list the “source → target” pairs and wait for the explicit “yes”. Silence is not consent.
    Order template for an executor
    Move the files from <input-folder> into EXISTING folders.
    Do not create new folders. Do not guess the topic — the target is given: <list file → folder>.
    First show a “file → folder” list and STOP.
    Move nothing until I write “yes”.
  3. Division of labour

    Principle: if a registry remembers for you, your mind stays free for the next thing, not for the filing. The light model keeps the process awake; the strong model and the human think.

    RoleWhat it does
    Light model · border guardCatches every new item the moment it appears and writes a row in the registry: identifier, location, date. It does not read meaning — only “it exists, here it is, it is registered”.
    Mid-tier model · doctorReads content, fills in kind and status, checks against a standard. Wakes the human only when a review is needed.
    Strong model + human · the brainThey do not maintain the process. They do the next thing. The registry remembers for them.
  4. Model and effort by the stakes

    The model menu next to the send button controls three separate things: the model, the effort and thinking. You can change them at any point — a change applies from the next response. On Fable 5.1, Opus 5.5 and Sonnet 5.5 thinking cannot be turned off in the app; a thinking toggle exists on older models (on Haiku 4.5 it is called “Extended”). Higher effort gives a more thorough answer but is slower and uses more tokens, so you reach your usage limit sooner.

    Model (as of 01.10.2026)For what
    Fable 5.1Demanding reasoning and long-horizon agentic work; when Opus 5.5 at higher effort still falls short.
    Opus 5.5The default starting point for most tasks.
    Sonnet 5.5The best combination of speed and intelligence.
    Haiku 4.5The fastest; for small, high-volume work. It has no effort setting.

    Default effort according to the official documentation: Fable 5.1 — high, Opus 5.5 — medium, Sonnet 5.5 — high. Thinking is adaptive: always on for Fable 5.1 and Opus 5.5; on Sonnet 5.5 the model decides how much to think.

    LevelFor what
    Max (and Extra high for long agentic work)Anything that goes out or up for approval: offers, contracts, legal texts, pricing and financial models, funding applications, new knowledge others will rely on.
    High (our working default; the default in the menu depends on the model)Drafts, brainstorming, analysis of status and blockers, standard offers, translation of a finished text.
    Low / MediumRenaming and tidying, quick look-ups, text extraction, simple formatting.
    ♻️
    AIlyak
    Systematically removing effort until only the value remains. The heavy model is not wasted on routine — but a light setting is not used for anything that leaves the building.
  5. Verification and practice

    When a strong model checks work, rely on it to flag the doubtful spots itself — but always ask explicitly “what worries you here?”. Silence is not a clean pass. And never trust the self-report alone: look at the real output.

    🛠️
    Exercise
    Delegate one routine task to a light sub-agent and check the real result, not its report. Any irreversible action along the way happens only with your “yes”. Do, don't consume.

04Check

1. Who DECIDES where a file is moved?

2. What does the human-in-the-loop law require before an irreversible move?

3. Which role only WATCHES — counts and flags, without touching meaning?

4. When do you use the highest effort?

05What's next

06Sources

  1. Models overview — the current model line-up, default effort and thinking (checked 01.10.2026).
  2. Change the model, effort, and thinking settings — the effort levels and thinking.
  3. KAGAMI working practice, generalised for publication.