Package com.smartgwt.client.docs

Interface CoTHistory

public interface CoTHistory

The history mechanism automatically maintains a list of the last N actions taking by an AI as part of executing a CoTProcess, to help the AI maintain context when it needs to execute a series of CoTTasks as part of an overall, logical task.

This is needed to support the more predictable "AI Workflow" execution model for enterprise AI workflows.

What is recorded

History is tracked automatically for: (a) transitions (the model emitted {goTo,intent,stepAfter}), and (b) successful non?transition results that were validated and applied to state (for example via CoTTask.stateUpdates).

History storage

The primary list is kept on the process as history. For ease of serialization and prompt access, a bounded mirror is also maintained at process.state.history. Both lists are append?only during a run.

Including history in prompts

History is typically referenced from standard prompt template via the "${promptPart('history')}", which includes the CoTProcess.historyPrimer and history data.

Manual entries

Add entries programmatically via CoTProcess.addHistory(). This appends to the process history and mirrors to state.history within configured limits.

  process.addHistory({
    taskID: task.ID,
    summary: "Added field 'orderDate'",
    ts: Date.now()
  });
  

Maximum history entries

The in?memory maximum is controlled by CoTProcess.historyMaxItems. The mirrored state.history maximum is controlled by CoTProcess.stateHistoryMaxItems and defaults to the in?memory maximum if unset. Older entries are dropped when limits are reached. Implementations may summarize older entries into a compact note before dropping them.