docs(kanban): clarify decomposer profile roles
This commit is contained in:
@@ -2016,11 +2016,11 @@ DEFAULT_CONFIG = {
|
||||
# raise these to keep more early failure evidence.
|
||||
"worker_log_rotate_bytes": 2 * 1024 * 1024,
|
||||
"worker_log_backup_count": 1,
|
||||
# Profile that decomposes tasks in the Triage column. When unset,
|
||||
# falls back to the default profile (the one `hermes` launches with
|
||||
# no -p flag). Set this to a dedicated 'orchestrator' profile if you
|
||||
# want decomposition to use a different model/skills from your main
|
||||
# working profile.
|
||||
# Profile assigned to the root/orchestration task after Triage
|
||||
# decomposition. When unset, falls back to the default profile (the
|
||||
# one `hermes` launches with no -p flag). This does not control the
|
||||
# decomposer prompt, model, or skills; configure that LLM path under
|
||||
# auxiliary.kanban_decomposer.
|
||||
"orchestrator_profile": "",
|
||||
# Where a child task lands if the orchestrator can't match an
|
||||
# assignee to any installed profile. When unset, falls back to the
|
||||
|
||||
Reference in New Issue
Block a user