liveBook · Manning

Pre-execution validation

As explained in AI Governance

A pre-execution check verifies that an operation's required conditions are satisfied before the operation runs.

Before an AI system changes a record or moves money, verify that the operation’s required conditions are met—not just that someone clicked “confirm.” These checks can catch errors a confirmation dialog misses. section 4.7.1

Check the conditions relevant to the action:

  • For an approval-status update, confirm required documentation exists and the amount is within the automatic-approval threshold. section 4.7.1
  • For a refund, confirm the original transaction exists and has not already been refunded. section 4.7.1

Pair validation with approval controls scaled to the action’s impact. Require users to verify critical parameters individually for high-impact actions. section 4.7.1

How AI Governance covers it

How deep it goes
Names concrete checks for approvals and refunds without prescribing a general implementation.
Examples
Uses approval updates and refunds to illustrate documentation, threshold, transaction-existence, and duplicate-refund checks.
What you can do after
Apply it by verifying required records, limits, and transaction state before allowing an action to execute.
How it connects
Pairs validation with tiered approval and user confirmation for consequential actions.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of AI Governance. The section links point to the parts of the book it draws on.