+ jHj4Rt^RIHt^RIt^RIt^RIHt^RIHt^RI H t ^RI H t ^RI Ht^RI Ht^R IHtHtHtHtHt^R IHt]P4!]4tR tR t]P>!R ]P@4t!]!RR44t"RRltRR/RRllt#RRlt$RRlt%RRlt&]!RR44t'RR/RRllt(R R!lt)R"R#lt*R$R%lt+R&RR'R/R(R)llt,R*R/R+R,llt-R#)-u}Kanban decomposer — fan a triage task out into a graph of child tasks. Invoked by ``hermes kanban decompose [task_id | --all]`` and the gateway dispatcher's auto-decompose path. Reads the profile roster (with descriptions), asks the auxiliary LLM for a task graph in JSON, then atomically creates the children, links them under the root, and flips the root ``triage -> todo``. The root stays alive as parent of every leaf child so it wakes back up when the graph completes and its assignee (the orchestrator profile) can judge completion and add more work. Mirrors ``kanban_specify`` (lazy aux import, lenient parse, never raises on expected failures). ``fanout=false`` collapses to the ``specify`` behaviour (tighten + promote, no children), making ``decompose`` a strict superset. Unknown assignees are rewritten to ``default_assignee`` — a child NEVER ends up with ``assignee=None``. ) annotationsN) dataclass)Optional) kanban_db)decompose_triage_task)kanban_db_connect)profiles) _call_aux_extract_json_blob_load_triage_task_task_prompt_fields _title_body)_profile_authoruYou are the Kanban decomposer for the Hermes Agent board. A user dropped a rough idea into the Triage column. Your job is to break it into a small graph of concrete child tasks and route each one to the best- matching profile from the available roster. You will be given: - The original task title and body - The list of available profiles (each with name + description) - The fallback "default_assignee" used when no profile fits Output a single JSON object with this exact shape: { "fanout": true, "rationale": "", "tasks": [ { "title": "", "body": "", "assignee": "", "parents": [, ...] }, ... ] } Rules: - "parents" is a list of INDICES (0-based) into this same "tasks" list, expressing actual data dependencies. Tasks with no parents run in PARALLEL. Tasks with parents wait until every parent completes. - Prefer parallelism. If two tasks can be done independently, give them no parents so the dispatcher fans them out at once. - Use 2-6 tasks for normal work. Don't create 20 tiny tasks. Don't cram everything into 1 task. - Pick assignees from the roster by matching the task to the profile's DESCRIPTION (not just the name). When nothing matches well, use null and the system will route to the default_assignee. - Each child task body is what a fresh worker will read with no other context — be specific about goal, approach, and acceptance criteria. When the task is genuinely a single unit of work (no useful decomposition), return: { "fanout": false, "rationale": "", "title": "", "body": "", "assignee": "" } In that case the task stays as one work item, just with a tightened spec and a concrete assignee. If no profile fits, use null and the system will route to the default_assignee. No preamble, no closing remarks, no code fences. Output only the JSON object. zTask id: {task_id} Title: {title} Body: {body} Available profiles (assignees you may pick from): {roster} Default assignee (used when no profile fits a task): {default_assignee} z^```(?:json)?\s*|\s*```$ch]tRt^pt$RtR]R&R]R&RtR]R&RtR]R &R tR ]R &R t R ]R&Rt R #)DecomposeOutcomez+Result of decomposing a single triage task.strtask_idboolokreasonFfanoutNzlist[str] | None child_ids Optional[str] new_title) __name__ __module__ __qualname____firstlineno____doc____annotations__rrrr__static_attributes__r@/home/ubuntu/.hermes/hermes-agent/hermes_cli/kanban_decompose.pyrrps85 L HFCFD"&I&#I}#r#rcV^8dQhRR/#)returnrr)formats"r$ __annotate__r)|s)))r#c\R4#)z0Mirror of ``hermes_cli.kanban._profile_author``. decomposer)_specify_authorrr#r$rr|s < ((r#fallbackc(V^8dQhRRRRRRRR/#)r&cfgdictkeyrr-rr'r)r(s"r$r)r)s)4c Y\r#c\V\4'dVPR/4M/pVPV4;'gRP4pYB;'gRP43F.pV'gK \P !V4'dVu#K0 \P!4;'gR# \ dK`i;i \ dR#i;i)ub``kanban.`` if it names an existing profile, else ``fallback`` (the root task's own assignee) if that does, else the active default profile — so a task is never stranded for lack of an owner. ``orchestrator_profile`` owns the root after fan-out; ``default_assignee`` catches children the decomposer can't route. The root's assignee sits before the active profile because the decomposer runs inside whatever profile hosts the dispatcher — an operator's credential-less incognito profile, say — and that profile must never silently become the owner of work the card was assigned away from (#114294). kanbanrdefault) isinstancer0getstrip profiles_modprofile_exists Exceptionget_active_profile_name)r/r1r- kanban_cfgexplicit candidates&&$ r$_resolve_profile_from_cfgr?s+5S$*?*?2&RJs#))r002HR 6 6 89 9 ..y99$$::335BBB   s0=CC"C>C CC C"!C"cV^8dQhRR/#)r&r'ztuple[list[dict], set[str]]r)r(s"r$r)r)s2222r#c \P!4p.pTFjpTP ;'gRP4pTPRTPRT;'gRTP: R2R\T4/4Kl Y Uu0uFq3PkK up3# \d-p\P RT4.\ 43uRp?#Rp?ii;iuupi) zd``(roster_for_prompt, valid_assignee_names)``; entries are ``{name, description, has_description}``.z&decompose: failed to list profiles: %sNrname descriptionz(no description; profile named )has_description) r8 list_profilesr:loggerwarningsetrCr7appendrBr) all_profilesexcrosterpdescs r$ _build_rosterrPs#113 F  ##**, AFF 4PP%DQVVJa#P tDz   L1LqFFL1 11 ?E35y2s#B% C% C0!CCCc V^8dQhRRRR/#)r&rM list[dict]r'rr)r(s"r$r)r)s:#r#cFV'gR#RPRV44#)u: (no profiles installed — decomposer cannot route work) c3t"TF.pRVR, VR,'dRMR RVR, 2xK0 R#5i)z - rBrEru ⚠ undescribedz: rCNr).0entrys& r$ !_format_roster..sDE uV}oE*;$<$NV]ViVi>i KK1h(@(@  ))I&,,"'4((G U[[]4( JtS$9$9DJJLr  7j7ajC.@Q!E\cR[nE\E\abai7j   )+6 R<ks.H H%H)H1Hc ,V^8dQhRRRRRRRRRR /#) r&rrrtr0rurfrvr'rr)r(s"r$r)r)s03xQar#c VPR4;'g.p\V\4'd V'g\VRR4#\ WV4wrVV'd\VRV4#\ P !4;_uu_4p\VVVPVVVPR7pRRR4Xf\TRR4#\TR R \!T4 R 2R TR 7# +'giL>;i \dp \TRRT 24uRp ? #Rp ? i\dDp \PRT4\TRR\T 4P 24uRp ? #Rp ? ii;i) tasksFz5decomposer returned fanout=true with empty tasks list)rirrvrhNzDB rejected graph: zdecompose: DB error on task %sz DB error: z.task already decomposed or moved out of triageTzdecomposed into z children)rr)r6r5rrrr|r}rrgrh ValueErrorr:rG exceptiontyperr) rrtrurvrrrrrrLs &&&& r$ _apply_fanoutrsK 7#))rI i & &i0ghh&w7CH 77S  " "d-%22!$11 I#0`aa )#i.)9CD\e !# " M2EcU0KLL S97C*T#Y=O=O  " " !$' !'..1 %55 CVKC {77 Y /F ~0MNN.._.L ::h  T7AA ' @@r#tenantc V^8dQhRRRR/#)r&rrr'z list[str]r)r(s"r$r)r)Ss$$}$ $r#c \P!4;_uu_4p\P!VRVRR7pRRR4XUu.uFq3PNK up# +'giL+;iuupi)z/Return task ids currently in the triage column.triagei)statusrlimitN)r|r}r~ list_tasksr{)rrrowsrows$ r$list_triage_idsrSsN    $}}T(6N " #dsFFd ##   #sAA/ A, ).r __future__rloggingre dataclassesrtypingr hermes_clirr~hermes_cli.kanban_db_graphrrr|rr8hermes_cli.kanban_specifyr r r r r rr, getLoggerrrGrrcompile MULTILINErrr?rPr[rdrfrqrrrrrrr#r$rs "# !&<//I   8 $9x  JJ2BLL A  $$ $) PT62&A  D"i&D:!A!!A" !AH$t$$r#