[
https://issues.apache.org/jira/browse/CAMEL-25147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-25147:
-----------------------------------
Assignee: Claus Ibsen
> camel-jbang - TUI: capabilities view grouping the route topology by the AI
> project overview's business capabilities
> -------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-25147
> URL: https://issues.apache.org/jira/browse/CAMEL-25147
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
>
> Follow-up to CAMEL-25143 (AI project overview).
> CAMEL-25143 lets an AI group a project's routes into business capabilities
> (for example "Ticket intake & lookup", "AI triage & alerting"). These are
> saved in integration-summary.md, but today they only appear as text. This
> ticket adds a capabilities view in the TUI: a zoom level above the route
> topology, so a project with many routes stays readable instead of turning
> into a flat spaghetti diagram.
> h3. Proposal
> * A top level in the Diagram topology with one box per capability (typically
> 3-6).
> ** Capability names are drawn in the ai-assisted style with the ✦ mark, since
> the grouping is AI-assisted.
> ** Each box shows facts from the sources: its entry points (HTTP, schedules,
> consumers), the external systems it uses (Kafka, SQL, OpenAI, ...), how many
> routes it has, and any warnings from the findings.
> * Lines between boxes are the existing route links, merged per capability
> pair, labelled with the strongest kind (call, hand-off, event).
> * Enter on a box drills down to its routes in the existing topology, Esc goes
> back up: capability -> routes -> steps.
> * The CLI (camel overview) can print the same grouped view.
> Most of the data already exists: capabilities and their route lists in the
> summary, links, systems and findings from ProjectOverview. The work is mostly
> TUI layout and navigation; the existing topology layout engine can lay out
> capability boxes as nodes.
> h3. Open design questions
> * Routes the AI did not place in any capability: an "Other" box, or a finding?
> * Routes in more than one capability: the prompt currently asks for exactly
> one, which keeps it a strict tree.
> * A route group set in the source (the DSL group field): it should probably
> win over the AI grouping. Such boxes are facts and are then shown without the
> ✦ mark.
> _Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
