A model refusal is not a business verdict.

Video caption

A model refusal is not a business verdict. The queue looks healthy while evidence disappears. Keep evidence, owner and approved fallback attached. #EricFieldNotes

Full written post / accessibility read

In an agentic workflow, a provider can refuse a request. That may be the right provider decision. But if your application interprets the empty classification as 'nothing to do,' it has silently made a business decision the provider never made.

Imagine an internal security triage agent. A refusal arrives while it classifies one report. The parser returns its default informational category and the ticket closes. No human saw the original evidence; the failure is the workflow's state mapping.

Make the model adapter return a typed outcome. Completed can proceed to business validation. Refused keeps the case open for an authorized human path. Unavailable gets bounded retry and alert. Uncertain goes to review. Preserve the response category and case owner.

Test a synthetic refusal and require the case to remain open under a named owner. Re-authorize any alternate model or human process before action. Do this because a provider's answer can govern service access, but it cannot own your business disposition.

#EricFieldNotes

Four-beat scene transcript

1. A model refusal is not a business verdict.

In an agentic workflow, a provider can refuse a request. That may be the right provider decision. But if your application interprets the empty classification as 'nothing to do,' it has silently made a business decision the provider never made.

Visual: An upstream policy response can strand downstream work.

2. A default category can close the wrong case.

Imagine an internal security triage agent. A refusal arrives while it classifies one report. The parser returns its default informational category and the ticket closes. No human saw the original evidence; the failure is the workflow's state mapping.

Visual: The queue looks healthy while evidence disappears.

3. Return a typed route result.

Make the model adapter return a typed outcome. Completed can proceed to business validation. Refused keeps the case open for an authorized human path. Unavailable gets bounded retry and alert. Uncertain goes to review. Preserve the response category and case owner.

Visual: Completed, refused, unavailable and uncertain need different paths.

4. Treat route loss as unfinished work.

Test a synthetic refusal and require the case to remain open under a named owner. Re-authorize any alternate model or human process before action. Do this because a provider's answer can govern service access, but it cannot own your business disposition.

Visual: Keep evidence, owner and approved fallback attached.

Research and claim limits

• OpenAI Usage Policies (S133)
• Anthropic Usage Policy update (S134)

The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.