UIF Admin Contract
Batoi UIF can render AIF administration and review interfaces. AIF should expose the data and actions; UIF should render clear, consistent product surfaces.
Useful Admin Surfaces
- provider registry
- prompt registry
- policy configuration
- execution register
- audit detail view
- human review queue
- evaluation results
- provider health and operational metrics
- durable queue status and dead-letter review
UI Boundary
UIF pages should not own provider logic, approval validity, or policy decisions. They collect user intent, render server-provided state, and call backend endpoints that execute through AIF.
Example Review Payload
{
"decision": "approve",
"notes": "Approved for this workspace request."
}The backend authenticates the reviewer, persists the decision, validates request-hash and workspace binding, consumes approval once, and decides whether execution may resume.