Information Request Workflow

AgentInformationRequest records capture missing context the assistant cannot infer safely.

Information requests can be open, answered, cancelled, or archived. Answering a request supplies human context for later review; it does not re-run an assistant automatically or mutate source records.

Sprint 17B makes assistant runs deterministically create information requests when missing context is detected. The checks are read-only and cover examples such as:

• CRM company/contact records missing phone or email
• CRM leads missing next action or owner context
• audits missing load/runtime data
• products missing cost or selling price
• projects missing owner or next-action/task context
• support tickets missing an assigned engineer
• source-of-truth records needing review, partially migrated, or missing an owner

Each generated request links back to the agent, run, module, target entity type, target entity id, requesting user, and assigned user where available. AgentRunStep logs both CHECK_GUARDRAILS and CREATE_INFORMATION_REQUEST.

The Read-Only Company Assistant page includes a manual preset called Create missing-information request for QA. It creates a linked test information request without editing any production record.