Skip to content
Silent Potato.
SearchTagsEN/中文
  • Start
  • Writing
  • Columns
  • Projects
  • Research
  • Work with me
  • Photos
  • About

Research · preprint · 0.6

Decompose First, Then Schedule: A Review of Multi-Model Task Decomposition, Capability Switching, and Subtask Routing

This paper examines task decomposition, subtask capability classification, model selection, and bounded execution-time fallback, while reducing the broader Agent scheduling problem to an engineering slice of dsh-quota-router.

LiyukLiyukPublished August 19, 2026
  • #AI
  • #Agent Systems
  • #Engineering
  • #Architecture
  • #Planning
  • #Observability
  • #Measurement
  • #Systems
  1. 1The Five Lenses: Connection-Oriented Problem LocationDeep research · 19 min read
  2. 2Data Measurement as Organizational Protocol: Definitions, Measurement, Tiering, and RetrospectivesDeep research · 11 min read
  3. 3Developer Productivity Is Not a Tool Catalog, but a Feedback SystemDeep research · 9 min read
  4. 4Defining the Boundaries Before Bringing AI Capability into an Engineering OrganizationDeep research · 9 min read
  5. 5When AI Lowers Workflow Barriers: How to Redivide Functional Lines and Business LinesDeep research · 14 min read
  6. 6Decompose First, Then Schedule: A Review of Multi-Model Task Decomposition, Capability Switching, and Subtask RoutingDeep research · 13 min readThis chapter
  7. 7Making an Agent a Collaborable Object: State, Feedback, and Result ConfirmationDeep research · 13 min read
  8. 8Let the Agent Execute: Emotional Adaptation, Trust Calibration, and Human Relief from Execution PressureDeep research · 13 min read
  9. 9The Laws of Human Motivation: The Situational Motivation ModelDeep research · 29 min read
  10. 10AI Does Not Automatically Create Productivity: From Local Acceleration to System ValueShort · 5 min read

Share to

XWeiboTelegramWhatsAppLinkedInFacebook

WeChat

Scan with WeChat

Open this article on your phone, or forward it to a friend.

Enjoy this site?

orSubscribe via RSS
← PreviousMaking an Agent a Collaborable Object: State, Feedback, and Result Confirmation
Next →The Five Lenses: Connection-Oriented Problem Location
View the column “Engineering & AI Judgment”← Previous: When AI Lowers Workflow Barriers: How to Redivide Functional Lines and Business LinesNext: Making an Agent a Collaborable Object: State, Feedback, and Result Confirmation →

Keep reading

Maybe related to this one.

  • WritingAI Does Not Automatically Create Productivity: From Local Acceleration to System ValueStarting from a multi-system integration experience, this essay distinguishes creation, task efficiency, organizational productivity, and business value—and asks where value and cost actually come from when AI enters a complex system.Read on →

    same column · shared 4 tags

  • WritingAI Gateway: From Backend Scheduling to Cost GovernanceUsing multi-backend model access as the setting, this article explains how an AI Gateway handles resource scheduling, capacity control, failure switching, distributed state, usage accounting, and enterprise cost governance.Read on →

    shared 3 tags

  • WritingData Measurement Guide (Part 2): Define What You're Measuring Before Arguing About MetricsA publicly reusable metric dictionary: from requests and users to tasks, explaining how availability, error, latency, performance, and feedback data should be defined, combined, and interpreted.Read on →

    shared 2 tags

© 2018–2026 Liyuk. Built slowly, published openly.

ElsewhereGitHub ↗X ↗LinkedIn ↗Email ↗Links ↗Favorites ↗RSS ↗
CC BY-NC-SA 4.0