Request Flow

This page describes the public behavior of an Arif request. Internal method names and deployment routes are intentionally omitted.

Chat Request Flow

Tool Execution Flow

1. Arif identifies the needed capability.
2. It validates the requested inputs.
3. It checks Qriib permissions and safety policy.
4. It asks for approval if policy requires it.
5. It executes the approved tool.
6. It reports the result and records supported changes for rollback.

Plan Mode Flow

Plan mode changes the first step: Arif investigates and saves a plan instead of immediately executing a change. Applying a saved plan still uses the normal governed execution flow.

Failure Flow

If a request fails, Arif should explain what failed and why. Depending on the situation, the user can retry, revise the request, accept partial completion, or undo supported changes.