Principle
Let the model propose; let deterministic code commit
Use the model for judgment; use the control plane for authority.
Before you use it
- Use when
- An agent can trigger consequential mutations directly from model output.
Keep this limit in mind
- Deterministic guards constrain effects but cannot guarantee the model chose the right business objective; consequential intent still needs appropriate review.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Treat model output as a proposed action. Deterministic infrastructure validates schema, permissions, limits, idempotency and current state before committing the mutation. Record the decision and result so failures can be audited, retried or reconciled without asking the model what probably happened.
An example
An agent proposes updating 500 customer records. The control plane validates the allowed fields, batch size and authorization, assigns an operation ID and performs the write.
Check your result
A malformed or unauthorized proposal fails before mutation, and a later operator can reconstruct why an accepted action ran.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingLet the model propose; let deterministic code commit
Evidence and sources
A deterministic control plane can treat model outputs as proposals, validate them, commit permitted actions and keep a decision history for recovery and audit.
Deterministic infrastructure cannot make model judgment deterministic; it constrains effects and records decisions rather than eliminating model uncertainty.
Building Deterministic Infrastructure for Non-Deterministic AI Agents · 3:08-6:27, model proposals, control-plane decision history, coordinated state and distributed-systems protections
Edition and review
Version 0.1.0
No review details are supplied for this edition.