[ 
https://issues.apache.org/jira/browse/CAMEL-26773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-26773.
---------------------------------
    Resolution: Fixed

Merged in https://github.com/apache/camel/pull/29466 (a5667912eff8).

_Claude Code on behalf of davsclaus_

> camel-chaos - the journal of an exploration: a budget it enforces, the 
> baseline, and the rules tried, in the report
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-26773
>                 URL: https://issues.apache.org/jira/browse/CAMEL-26773
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 4.24.0
>
>
> Step 4 of CAMEL-26760 ("let there be chaos"). Decided with Claus: the journal 
> of an exploration lives in camel-chaos, with the deadline, so the TUI, 
> {{camel get chaos}} and the report read it, it survives the agent losing 
> context, and camel-chaos enforces the budget whatever the agent does.
> * {{ChaosManager.startExploration(budget, focus)}}: one exploration at a 
> time, a budget of 10 minutes by default and at most 2 hours. It records the 
> baseline: the counts per route when it starts, so the errors already there 
> are not blamed on chaos.
> * While it runs, a rule ends at the deadline at the latest, and a rule that 
> would start after it is refused.
> * At the deadline (checked whenever chaos is used: a rule added, the report 
> read, which the status does every second), the rules are removed and the 
> exploration is finished. {{finishExploration()}} finishes it before.
> * The report has the exploration: when it started, the deadline and the time 
> left, the focus, the baseline, the rules added during it, and how it 
> finished. It stays in the report after it finished, until the next one starts 
> or the report is reset.
> * The chaos action of the CLI connector: {{explore-start}} and 
> {{explore-finish}}. {{camel get chaos --report}} shows it.
> The experiments (one per call) and the AI and MCP tools come with step 5.
> _Claude Code on behalf of Claus Ibsen_



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to