How do you govern messy human instructions before machine execution?

Separate the actor, intent, action, target, constraints, authority, ambiguity and applicable policy. Ambiguous terms must be clarified or escalated before execution.

Informal language can hide undefined thresholds, targets and exceptions that matter at execution time.

“Pay urgent suppliers but nothing unusual” must define urgent, unusual, eligible suppliers and approval limits before any payment instruction is formed.

Receive instruction → extract fields → identify ambiguity → request clarification or escalate → evaluate policy → authorize bounded action

Guardian

Retain the source instruction, normalized fields, unresolved ambiguity, clarification and decision.