What should an approval request show the reviewer?
Why A is the answer
The action, reason and likely effect
Reviewers need context to decide well.
In detail
- Reviewers need the action, the reason and the likely effect.
- A bare yes or no prompt invites rubber-stamping.
Use case
An illustrative scenario, not a real incident.
A reviewer sees the action, the reason and the likely effect, so approval is informed.
See it in different ways
sequenceDiagram participant G as Agent participant H as Human participant S as System G->>H: Proposed action and reason H-->>G: Approve or reject G->>S: Run if approved
sequenceDiagram
participant A as Agent
participant H as Reviewer
participant S as System
A->>H: Action, reason and likely effect
alt Approved
H->>S: Run
else Rejected
H-->>A: Stop
endmindmap
root(("Approval request"))
n1["Shows"]
n2["Action"]
n3["Reason"]
n4["Likely effect"]Key point: Reviewers need context.
Why the other options are wrong
- B. Only a yes or no button and nothing else
- A button with no context is a rubber stamp.
- C. The full model weights as an attachment
- Weights mean nothing to a reviewer.
- D. The agent's GPU utilization at that moment
- Utilization has no bearing on the decision.