Anthropic describes checks every few hours, without a guaranteed alert time. Confirm the supported timing and notification controls in your account before setting up follow-up.
Ask Duet to propose a follow-up plan. 8:30 a.m. is a preference; confirm whether your account supports that time.
I want this project included in your morning brief. Between briefs, alert me when a new source message creates a launch risk or explicitly needs my decision. Keep ordinary progress for the next brief. Do not repeat an unchanged alert.
Use only the same test mailbox, sender, and DUET-PRACTICE-01 subject label. Include later messages with that label. Preserve the current launch until a source explicitly approves a change. Missing information or a failed read must remain visible.
Prefer a morning brief at 8:30 a.m., America/New_York. Tell me which timing and notification settings are actually supported; do not promise an exact time if you cannot set it. Avoid creating a second schedule that duplicates your existing brief.
Show the supported setup for my review before changing it. Keep all external sending, source edits, calendar changes, purchases, and publishing out of scope.
Review whatever persistent setup the invited account actually exposes, including scope, usage, notification delivery, and how to stop it. Approve only that setup. A chat promise alone is insufficient evidence that follow-up is configured. If you cannot inspect or confirm the setup, keep the test marked unverified and use on-demand briefs.
If you proceed, choose a bounded observation window. Then send M4 through your own email app, from the same test sender:
Subject: DUET-PRACTICE-01 M4: Image delayed
Fictional practice. Ben’s revised delivery for the main launch image is October 30, 2026 at noon, America/New_York. This replaces the October 27 estimate. The image needs a reshoot and will not be ready earlier. The October 29 launch has not moved, and no replacement image has been approved.
Record when the email arrives. Do not tell Duet what changed or ask it to refresh during the observation window. A useful alert would identify that the image now arrives after launch, cite M4, and request a decision. It should leave the launch, approvals, and outgoing messages unchanged.
Keep these outcomes separate in your log:
- An unsolicited message inside Duet.
- A phone or operating-system notification.
- An answer produced after you explicitly ask for an update.
The third outcome proves only an on-demand check. If no alert arrives, record that result. A later manual refresh can help investigate source access, but it cannot count as the proactive alert. Keep normal deadline tracking in place.
