Supplier bank-detail change
Situation: Before AP replies, updates supplier records, or acts on a payment-detail change sent by email.
Likely output: Unsafe or high-caution decision with blocked action_gate, a governed safest move to verify via a known supplier contact, and audit references for later review.
Must not do automatically: Do not auto-send, auto-approve, or auto-update supplier master data because a signal came back green or amber.
Urgent payment pressure
Situation: Before an agent or AP operator replies to an urgent payment request that relies on time pressure or senior-name authority.
Likely output: Unsafe or caution decision highlighting authority gaps, pressure signals, and blocked or reviewed action_gate.
Must not do automatically: Do not interpret urgency as authority. Do not draft a reply that implies payment approval automatically.
Contract commitment reply
Situation: Before sending a reply that may imply acceptance, scope agreement, delivery commitment, or liability.
Likely output: Decision object explaining commitment risk, safest move, and whether a bounded safe reply may be inserted.
Must not do automatically: Do not auto-send the safe reply draft. Allowed means prepare under accountable control, not autonomous send.
AI agent about to send an external message
Situation: Before an agent sends an externally-visible message that could create consequence for a person or organisation.
Likely output: Decision with action_gate, signal, safest_move, and secondary audit references.
Must not do automatically: Do not treat allowed=true as a send permission. Genius is a risk gate, not an autonomous execution grant.
Support agent about to promise refund or credit
Situation: Before a support workflow promises a refund, credit, waiver, or exception with financial or policy consequence.
Likely output: Decision showing money, authority, or exception risk and whether escalation is required.
Must not do automatically: Do not auto-grant commercial concessions because the tool did not block.
Procurement agent about to approve supplier update
Situation: Before procurement or a workflow agent approves a supplier setup or supplier-record change with control implications.
Likely output: Decision highlighting authority gaps, missing protections, and safest next move.
Must not do automatically: Do not use Genius as a replacement for supplier onboarding controls or finance control policy.