Research Note
Structural AI Workflow Evidence Model
Durable integration requires more than an interface around a model. The system must connect an authorized task to source data, identity, access, state, business rules, re
Structural AI Workflow Evidence Model
Workflow layers
Durable integration requires more than an interface around a model. The system must connect an authorized task to source data, identity, access, state, business rules, review, action authority, evidence, monitoring, failure handling, and change control.
| Layer | Evidence question |
|---|---|
| Task | What decision or work unit is owned? |
| Data | Which sources are authoritative, permitted, current, and traceable? |
| Identity | Who or what is acting, for whom, and with which access? |
| State | Where does durable workflow state live? |
| Rules | Which deterministic constraints and policies apply? |
| Review | What must a qualified person inspect before action? |
| Authority | Which action can the system recommend, draft, stage, or execute? |
| Evidence | What inputs, outputs, versions, approvals, and changes are preserved? |
| Failure | How are uncertainty, disagreement, outage, misuse, and rollback handled? |
| Change | Who owns monitoring, evaluation, update, and retirement? |
Wrapper boundary
A thin interface can be appropriate for exploration or a disposable low-risk task. The problem begins when the interface is presented as integration while the user manually performs all data retrieval, validation, state management, review, and recovery.
The presence of an AI model does not determine workflow depth. A structural workflow may use a model for one bounded extraction step and deterministic systems for validation and commitment.
Evidence sources
NIST's Generative AI Profile organizes risks and actions across the lifecycle. NAIC's current insurance AI work emphasizes governance, risk mitigation, data, documentation, and examination.
These sources do not supply one architecture. The actual design depends on the use case, law, organization, system, data, and failure consequence.
Public boundary
Do not claim that wrappers always fail, that custom software is always superior, or that an AI workflow is production-ready because it can write to a database.
Sources
Follow the evidence.
- Holland and Kavuri, HICSS-56aisel.aisnet.org
- Google: Our next-generation model, Gemini 1.5blog.google
- Liu et al.: Lost in the Middleaclanthology.org
- OpenAI: Video generation models as world simulatorsopenai.com
- Google AI for Developers: Long contextai.google.dev
- NAIC: Artificial Intelligencecontent.naic.org
- Spotify episode recordpodcasters.spotify.com
- OpenAI: Sora is hereopenai.com
- NAIC: Model Bulletin on the Use of Artificial Intelligence Systems by Insurerscontent.naic.org
- NIST: Artificial Intelligence Risk Management Framework, Generative Artificial Intelligence Profilenist.gov