# Let the model propose; let deterministic code commit

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Let the model propose; let deterministic code commit

ID: MHC-D-RESEARCH-1176 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/let-the-model-propose-let-deterministic-code-commit

Use the model for judgment; use the control plane for authority.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- An agent can trigger consequential mutations directly from model output.

### Avoid when

- Deterministic guards constrain effects but cannot guarantee the model chose the right business objective; consequential intent still needs appropriate review.

### Explanation

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.

### 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

A malformed or unauthorized proposal fails before mutation, and a later operator can reconstruct why an accepted action ran.

### Limits

- Deterministic guards constrain effects but cannot guarantee the model chose the right business objective; consequential intent still needs appropriate review.

### Evidence and sources

- supports: A deterministic control plane can treat model outputs as proposals, validate them, commit permitted actions and keep a decision history for recovery and audit. — RS-CC5DC111315BEF2B. Deterministic infrastructure cannot make model judgment deterministic; it constrains effects and records decisions rather than eliminating model uncertainty. (3:08-6:27, model proposals, control-plane decision history, coordinated state and distributed-systems protections)
- RS-CC5DC111315BEF2B: Building Deterministic Infrastructure for Non-Deterministic AI Agents — https://ai.engineer/talks/APh1Vx0oLmQ-building-deterministic-infrastructure-non

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/enforce-permissions-outside-the-model
