3.3 The Ambiguity Protocol

What happens when Amy is confused?

If the Router (Article 3.2) cannot determine the deal with >90% confidence, we DO NOT GUESS. Guessing leads to filing the wrong contract in the wrong SkySlope file.

Instead, we trigger the Ambiguity Protocol.

The "Clarification Loop"

Amy automatically replies to the sender asking for help.

The Workflow:

Router returns null or ambiguous.
n8n triggers Gmail/AgentMail Send Node.
To: The Sender.
Template:

Subject: Re: [Original Subject]
"Hi! I received your message, but I'm managing a few different files for you right now.
To ensure I file this correctly, could you please reply with the Property Address?
Thanks, Amy"

The Human Fallback

If the user replies and we still can't figure it out:

n8n sends a Slack/Email Alert to YOU (The Human Supervisor).
Message: "Routing Failure. Sender: lender@bank.com. Subject: Docs. Please manually route in Airtable."
You go to Airtable, find the "Unprocessed Emails" view, and drag the email to the correct deal.

Why this matters: This ensures zero data loss. Even if the AI fails, the email lands in a "Manual Review" bucket, keeping the system bulletproof.