28 lines
1.2 KiB
Markdown
28 lines
1.2 KiB
Markdown
|
# Operator Approval Workflow
|
||
|
|
|
||
|
|
This document describes the process of reviewing and approving actions generated by the reconciliation supervisor.
|
||
|
|
|
||
|
|
## Workflow Stages
|
||
|
|
|
||
|
|
### 1. Action Identification
|
||
|
|
When the supervisor identifies a delta between desired and actual state, it generates a pending action in `/opt/homelab/actions/pending/`.
|
||
|
|
|
||
|
|
### 2. Risk Assessment
|
||
|
|
Actions are categorized by risk level:
|
||
|
|
- **Safe**: Low impact, high confidence. Can be auto-approved in autonomous mode.
|
||
|
|
- **Guarded**: Moderate impact. Requires explicit operator approval.
|
||
|
|
- **Dangerous**: High impact (e.g., node redeploy). Requires multi-step approval or senior operator override.
|
||
|
|
|
||
|
|
### 3. Review Process
|
||
|
|
1. Navigate to the **Action Queue** view.
|
||
|
|
2. Review the **Confidence Score** and **Correlation Chain** to understand why the action was proposed.
|
||
|
|
3. Check the **Rollback Availability**.
|
||
|
|
|
||
|
|
### 4. Decision
|
||
|
|
- **Approve**: Moves action to `approved` state.
|
||
|
|
- **Reject**: Moves action to `rejected` state and suppresses similar recommendations for a cooldown period.
|
||
|
|
- **Execute**: Transitions an approved action to `running` status.
|
||
|
|
|
||
|
|
## Mobile Approvals
|
||
|
|
Approval requests can be acknowledged via the Telegram bot integration, allowing for remote operational control.
|