root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(FN-3703): implement assigned-agent triage inheritance in engine and tr

Browse Source 
Implements assigned-agent triage inheritance (FN-3703), allowing triage logic to be delegated to the assigned agent rather than always routing through the original owner, with test coverage and documentation. Also adds immediate wake controls for agent inbox and message API (FN-3087), wires shared s

Fusion-Task-Id: FN-3703
This commit is contained in:
Fusion
2026-05-07 11:18:56 -07:00
committed by gsxdsm
parent 13808fc5e7
commit edbc8b2535
8 changed files with 311 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/agents.md
View File

@@ -110,6 +110,17 @@ Executor precedence for task runs:
If the assigned agent runtime model is missing or incomplete, Fusion falls back to the normal task/settings execution hierarchy.
### Assigned-agent identity + planning model precedence for task triage
When a triage/specification run targets a task with `assignedAgentId` and that agent is durable, planning now inherits the assigned agent context instead of only generic triage-role defaults.
Triage inheritance behavior:
1. The triage system prompt includes assigned-agent identity context and resolves instructions/soul/memory from that agent (including existing rating-aware instruction composition)
2. Triage memory tools are created with assigned-agent memory context (`createMemoryTools(..., { agentMemory })`), so `fn_memory_search` / `fn_memory_get` can access `.fusion/agent-memory/{agentId}/...` during planning
3. Planning model resolution prefers a complete assigned-agent runtime model pair first, then task planning overrides, then normal planning/project/global fallbacks
As with execution, incomplete assigned-agent model configuration falls through cleanly to the existing planning hierarchy.
### Task Detail Agent Log model provenance
The Task Detail → Agent Log model header prefers runtime provenance markers written during execution/review: