Purpose
Role Assistants keep people in authority by presenting a clear human task when governed work needs information or a decision. A human response records a typed decision. The platform evaluates that response with current business context and required controls, then continues, waits, completes, or stops safely.
What this shows: Ask and Approval are a second conversation loop — not a different product. ChatGPT, Copilot, or Teams present the decision; AI Fabrix evaluates it.
What this is not: The interface approving work on its own, or a chat message that bypasses Operational Trust.
Ask, choice, and approval
An Ask requests information that the work cannot safely infer. The response can provide a value for this work only, point at existing supporting evidence, decline, or choose from allowed options. An Ask answer is not certified Evidence by itself.
A choice resolves a defined conflict or alternative; it is not an approval.
An Approval accepts or rejects a proposed business change — for example certifying Evidence that may be reused, or accepting a capability outcome that creates or updates business records. Approving records that the person stands behind that proposal as business data for the work. It does not invent Reality from chat, grant new permissions, or skip later trust checks.
Does approval certify business data?
Yes — for the proposal under review. Approval means the person accepts or rejects that proposed business change (including Evidence certification when that is the task). The platform still applies trust controls before work continues. An Ask answer alone is not certified Evidence.
Review Workspace
Simple asks and approvals should remain in the conversation where the work began (channel cards). When the decision needs visual comparison, several related objects, structured information, or conflict resolution, the person opens the Review Workspace in Work — a temporary rich review, not the daily home. It presents one business problem in context, captures the response, and returns the person to conversation.
This distinction makes the choice clear: a conflict choice selects an allowed option; an approval accepts or rejects a proposal. Neither response replaces the platform’s evaluation of what happens next.
Why?
Why? gives a readable explanation for an allow, deny, or wait outcome. It helps a person understand the business context, required control, or missing information that affected the work. A useful explanation answers what is happening now and what can happen next, without exposing technical traces or making the user interpret internal policy logic.
When work is denied, Why? helps the person decide whether to correct information, request an appropriate review, or ask an operator to investigate a trust boundary. When work waits, it clarifies who needs to respond and what decision is pending.
See Governed work execution for the controls that govern capability requests and Audit and regulatory readiness for how completed work supports review.
Expiry and honest outcomes
An expired task remains readable so people can understand what was requested and why it did not proceed. It is non-actionable: the person cannot replay an old response against changed business context. The outcome should state plainly whether work completed, failed, was denied, expired, or is waiting for more information.
Honest status avoids treating a rejected response or a stale proposal as successful work. If the objective still matters, a new governed request can begin from current business context.
Example
A Finance Assistant proposes an update based on a discrepancy. The owner opens the Review Workspace because several records must be compared, chooses the correct source, and approves the proposed update. That approval accepts the proposed business change for this work. The platform evaluates the response, current information, and required controls before deciding whether to continue. The resulting evidence records the decision and outcome.
Business value
Typed human tasks make accountability clear without making people operate a technical workflow. People can supply knowledge, resolve an allowed conflict, or approve a proposal in the right context, while the platform retains responsibility for governing the next step.
Limits
Available task presentation and Review Workspace detail vary by deployment. An expired task is intentionally readable but cannot be acted on, and an explanation describes the current result rather than guaranteeing that a future request will receive the same outcome.