Orchestration
Classify intent, gather required context, manage operation state, and decide when work must stop.
Architecture guide
The operating layers around AI.
A production AI operation needs more than a model and an interface. These layers define how business work moves safely, visibly, and with accountable ownership.
The reusable model
Six layers define the work around the model.
They are the practical architecture a team needs to assess before asking an AI experience to perform real business work.
Approved actions
Retrieve, create, update, route, notify, or escalate only through permitted systems and scoped access.
Governance
Apply policy boundaries, data limits, consent points, escalation triggers, and review ownership.
Channels
Expose the same operation across the approved channels without recreating the control model in each interface.
Human handoff
Transfer the relevant context, reason, and next action when a person must take over.
Evidence
Preserve the request, boundary, action, owner, and outcome so the business can inspect what happened.
How the layers work together
Follow one request through the operation.
The layers are not a checklist to complete once. They shape each material move in a controlled workflow.
- 01
Receive the request
A channel receives the request and the operation identifies the context it still needs.
- 02
Test the boundary
Governance and orchestration determine whether an approved action may proceed or work must stop.
- 03
Move or hand off
The operation uses permitted systems or transfers the case with the context and next action a person needs.
- 04
Keep the record
Evidence connects the request, rule, action, owner, and outcome for operations and review teams.
The boundary
The interface is only one surface.
A chat, voice, web, or human channel can begin the journey. The operating layers decide what happens after the request is understood.
Conversation alone does not define approved system action, exception ownership, or a reviewable record.
A connector moves data. It does not decide whether the action is permitted or who takes over when it is not.
Capability becomes an operation when its boundary, owner, controls, and evidence are explicit.
Next decision
Review the operation that needs these layers.
Start with one workflow, then define the permitted actions, human boundary, and evidence your team needs to inspect.