cristiano.hoshikawa/agent_platform_oci
1
2
Fork 0
mirror of https://github.com/hoshikawa2/agent_platform_oci.git synced 2026-11-06 03:14:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

new feature: Multi-Intent

Browse Source
This commit is contained in:
Cristiano Hoshikawa
2026-09-10 22:55:50 -03:00
parent 05410adf09
commit 3f884d028a
198 changed files with 566 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/features/en/16_multi_intent_planning.md
View File

@@ -2,9 +2,8 @@
`MultiIntentPlanner` recognizes independent requests in one utterance and
builds a plan constrained to the intents, agents, and tools declared in
`config/routing.yaml`. It does not execute operations or let the LLM invent a
sequence: the router selects the primary operation and the domain workflow
continues to own the transaction.
`config/routing.yaml`. It does not execute operations: the router selects the
primary operation and the domain workflow continues to own the transaction.
## Configuration and execution
@@ -12,12 +11,21 @@ No additional configuration is required. The planner uses the intents already
declared in `routing.yaml`, selects the single transactional operation from
`tool_policies.yaml`, and persists the remaining requests as `pending_topics`.
When `ENABLE_LLM_ROUTER=true`, a compound message whose deterministic plan is
missing or incomplete is sent to a structured multi-intent classifier. The LLM
may return only configured intent names and source fragments. Agent, domain,
and tool ownership are always hydrated from `routing.yaml`; unknown intents,
low confidence, and invalid JSON are rejected. The default confidence threshold
is `0.65` and can be overridden with
`multi_intent.llm_confidence_threshold`.
Known read-only topics execute through their own agent. A second mutation stays
pending for its own confirmation, while an unknown clause becomes off-context.
The router resolves clauses from registered intent keywords and routes the
transactional operation first. The graph drains read-only pending topics before
output supervision. During an open transaction,
The router first resolves clauses from registered intent keywords, then uses the
semantic fallback only for an absent or incomplete compound plan, and routes
the transactional operation first. The graph drains read-only pending topics
before output supervision. During an open transaction,
`yes, and send me the invoice` confirms the transaction and records the
secondary request instead of causing an intent shift.