1. Describe the human-in-the-loop (HITL) controls your platform provides, including the granularity at which a customer administrator can require human review (e.g. per-tenant, per-workflow, per-action, per-decision-type).
Why it matters. HITL that can only be set per session or per tenant cannot require review of a single high-risk action. Granularity determines whether the buyer can actually deploy in higher-risk contexts. The NIST AI RMF asks that processes for human oversight be defined, assessed and documented (MAP 3.5).
- Names specific HITL configuration scopes (workflow, action, decision type, risk tier)
- Describes admin UI or API to configure HITL without code changes
- Differentiates HITL for read-only vs. state-changing actions
- HITL only available at session or tenant level
- HITL described as a roadmap item rather than current capability
- No way to require review for specific high-risk actions