Iterate on Orchestrator Mode

[nissa-seru]

Something like:

• Mode should define:
  - Planning model; does not execute, only plans, delegates (and revises plan per progress at checkpoints.)
  - Any number of worker models, each with any number of verbs they can perform.
  - Each verb has an input format and and output format. These may markdown templates or json/xml schema.
  • Use a DSL to enable the planning model to incorporate the outputs of already-executed steps in the inputs of subsequent steps (using a variable reference format or similar.).
  • Process:
    • Orchestrator model (I am going to call it planner) should not be executing, only planning, delegating, and revising plan per progress as needed.
    • Planner should be provided with a list of models and their capabilities.
    • Planner should essentially output an ordered dict of model:verb
    • Planning should be done in stages:
      • Conceptually decompose the task
      • Validate decomposition; does each item truly do one thing?
      • Check for opportunities where shared context is overwhelmingly helpful, update the decomp accordingly.
      • Identify any pause points for the planner to check progress and modify unexecuted segment of the plan to adapt as needed.
      • Review the abilities of each worker, assign steps to workers
      • Populate the input format for the verb comprising each step.
      • Yield to first step to begin execution.

[BradKML]

So grand orchestrator => planner/delegator => single task coder?