Case CASE-2

nonzero discrepancy (hold)

Authority: NONE at every stage. The classifier, guard, and any journal record below are a simulation — no real payment, balance transfer, or human authorization occurs. Deterministic logic and model output never grant execution authority.

Source facts

Invoice: INV-200 (supplier SUP-200)
Invoice stated total: $100.00
Invoice computed total: $100.00
PO lookup state: FOUND
Purchase order: PO-200 ($95.00)
Supplier lookup state: MATCH
Discrepancy: $5.00

Decision & authority trace

Classifier proposal

Exact-match eligible: False

Reason codes: LINE ITEMS NONCONFORMING NONZERO DISCREPANCY

Proposal only — not an action. execution_authority = NONE.
Guard decision

Action: HOLD

Deterministic permission check — a simulated decision, not a payment or human authorization.
Simulated journal action

No committed action (held or not executed).
Independent verification

Outcome: NOT_ELIGIBLE

Reasons: case is not an eligible exact match

NOT_ELIGIBLE means this case is ineligible for the simulated exact-match approval path — not an independent certification of the held case.

Selective Intelligence — B3 Routing

OFFLINE SIMULATION — NO LIVE AMD REQUEST. The model output below is produced by a local mock adapter exercising the accepted validator; no external service is contacted.

Route: INFERENCE

Offline adapter invocations: 1

Advisory outcome: SUCCESS

Source-consistent: True

execution_authority: NONE

Advisory interpretation: supplier SUP-200, invoice INV-200, amount $100.00, discrepancy $5.00, confidence 0.9.

Advisory only — this does not change the B1 guard or journal decision above.
Authority-claim rejection adversarial example

Injected model output asserted an authority key (“approve”).

Advisory outcome: AUTHORITY_CLAIM

execution_authority: NONE

Rejected by the accepted validator — authority remains NONE; no journal action.

Back to cases