Use intelligence where it improves the process.
Control it where it introduces risk.
Some steps of a process benefit from generation. Others must behave the same way every time. The architecture decides which is which.
Deterministic and generative are different tools.
The choice is a control decision, made per step of the process.
Deterministic
Same input, same result
- Rules, states and thresholds
- Verifiable and repeatable
- Used where a customer’s treatment is affected
- Easy to audit
Generative
Adapts to the moment
- Language understanding and phrasing
- Handles variation and free input
- Used where flexibility improves the outcome
- Bounded by grounding and guardrails
Five layers from model to control.
Generation sits inside a structure that keeps it useful and contained.
- 01ModelsSelected per use case.
- 02OrchestrationDecides which path a case takes.
- 03Grounding and toolsFacts and actions the model can use.
- 04GuardrailsLimits, validation and escalation.
- 05VersioningWhat changed, and when.
Model selection is process-dependent.
There is no single best model, only a best fit for a step and its risk profile.
| Step | Generation fit | Control requirement |
|---|---|---|
| Language understanding | High | Bounded by intent scope and validation |
| Dialogue phrasing | High | Constrained by approved content |
| Process decisions | Low | Deterministic rules and thresholds |
| Data extraction | Medium | Validated against source fields |
| Summarisation and notes | Medium | Reviewed against the case record |
Governance of the model layer.
Whoever changes the model changes the process. That is why the change path is explicit.
Vee operates
- Model selection per step
- Prompt and scenario versioning
- Guardrail configuration
- Monitoring and rollback
Client owns
- Risk appetite
- Regulatory interpretation
- Approval of consequential change
Shared
- Evaluation criteria
- Watch-list of model changes
- Definition of acceptable behaviour
Provider independence, without the platform tax.
The process should not be locked to one model provider, nor to the complexity of stitching many together.
Vee treats models as replaceable components selected per step, behind a stable orchestration layer. A provider can change without redesigning the process.
That keeps model change a controlled operational event rather than a migration project.
Independence means
- 01Provider swap without process redesign
- 02Consistent behaviour across providers
- 03Versioned and comparable configurations
Where to go next.
The model layer connects to the platform, to governance and to voice.
Control
Direction
Decide where intelligence belongs in your process.
We will separate the steps that should adapt from the steps that must not.