Conversations and actions

A conversation can retrieve context, explain an operational state, or propose an action. It should never hide the boundary between those modes.

For answers, show the records and freshness that supported the response. For actions, show the intended change, affected systems, and approval requirement before anything is executed. The resulting run is the durable record: it captures the policy decision, tools called, outputs, and final status.

If a request needs deterministic orchestration or can wait for days, route it into a workflow rather than treating the chat response as the process.