OFF
OPT-IN REQUIRED
BUCKVISIONAICONTROLLED EMAIL DELIVERYKnow the Difference Between Sent and Delivered.
80.4 keeps the 80.3 controlled-email contract but separates BuckVisionAI transport state from verified provider delivery truth. Only an already-approved unread 80.2 priority notification can become an email candidate, and the member remains in control of consent, severity choices, quiet hours, and the rolling delivery cap.
Email is OFF by default. Enabling still requires the exact application confirmation. Receiving or delivering an email does not acknowledge, snooze, resolve, or execute the linked 80.1 action.
0 / 4
Rolling member transport cap.
0
Provider-confirmed delivery truth.
0
Ambiguous outcomes are never blindly resent.
0
Failed, bounced, complained, or provider-suppressed.
Loading…
Delivery remains bound to the authenticated account email.
READY
DELIVERY TRUTH ACTIVEControlled Email Preferences
Explicit Email Opt-In
To enable external email transport, type the exact confirmation below. BuckVisionAI will use the email address on your authenticated member account.
Recent Email Transport + Delivery Truth
Transport state records what BuckVisionAI did. Delivery state records the latest verified provider truth available to 80.4.
80.4 remains the transport and provider-delivery-truth layer over existing 80.2 notification evidence. A transport marked SENT or PROVIDER ACCEPTED is not automatically treated as DELIVERED. Provider delivery truth is tracked separately, and provider safety events can pause additional transport without erasing the member's consent history. New 80.5 priority emails use an authenticated BuckVisionAI action bridge; loading the bridge does not create an action-open event until the member explicitly continues to the linked tool.