Current price on the blocked order line.
Public verification artifact · Synthetic case
One pricing exception. One governed path to a truthful result.
This artifact shows the control semantics of ZEODEC Order Resolution on an illustrative B2B order-price mismatch. It is not a customer case study, traction claim, ROI claim or production certification.
Verification path
SUPPORTED → APPROVED → EXECUTED
Each state must be independently true. A supported target price is not the same as approval, and approval is not the same as successful execution.
Synthetic case
A blocked line price conflicts with supported customer evidence.
Illustrative numbers are chosen only to make the control path concrete.
Derived from the eligible customer pricing evidence.
Eligible units on the affected line.
Difference between current ERP value and supported correction.
Arithmetic: (€128.00 − €121.50) × 240 = €1,560. The value is illustrative and is not a savings or customer-outcome claim.
Evidence reconstruction
The price must be supportable before authority is evaluated.
Evidence can support a target price, but it cannot silently create authority to mutate the ERP.
01Exception signal
Blocked order line reports a pricing mismatch.
02Evidence intake
Customer PO and current eligible price schedule are retained with provenance.
03Conflict handling
Superseded or contradictory evidence is excluded or escalated.
04Supported resolution
Target unit price €121.50 is supported for this line.
Authority boundary
Supported does not mean authorized.
In this synthetic case, the €1,560 economic delta crosses the configured approval boundary, so automated mutation is held.
The target price is evidence-backed.
The economic impact requires a verified principal.
No ERP mutation is claimed at this stage.
A verified approval applies to the already-supported correction. It does not permit an arbitrary price, destination or execution path.
Controlled execution
Only an authorized correction can enter the mutation boundary.
The public product boundary currently describes Microsoft Dynamics 365 Business Central as the first-party ERP path, plus a qualified trusted customer HTTP execution contract.
05Verified approval
Authorized principal approves the supported target price.
06Pre-mutation verification
Current ERP state and line identity are rechecked before write.
07Governed mutation
Only the authorized unit-price field is sent through the configured execution path.
08Validated acknowledgement
EXECUTED is recorded only after a valid acknowledgement confirms the intended mutation.
Truthful output
Resolution Receipt
The receipt preserves the difference between what was supported, what was authorized and what actually happened.
RESOLUTION RECEIPTSYNTHETIC
- Exception
- ORDER_LINE_PRICE_MISMATCH
- Supported target
- €121.50 / unit
- Eligible quantity
- 240
- Economic delta
- €1,560
- Evidence
- SUPPORTED
- Authorization
- APPROVED
- Execution path
- TRUSTED / CONFIGURED
- Execution outcome
- EXECUTED
- Acknowledgement
- VALIDATED
No receipt field should imply successful execution before acknowledgement validation.
Fail-closed semantics
Uncertainty must not become a false success.
Any material break in evidence, authority or execution truth changes the result.
Do not produce a supported target. Escalate.
Do not enter the mutation boundary.
Do not overwrite a changed line. Re-evaluate.
Do not record EXECUTED. Preserve the failed execution state.
What this proves
The product boundary is the governed transition, not merely the recommendation.
Order Resolution is designed to keep evidence, authority, execution and audit truth separate while still completing the supported workflow when every boundary passes.