/TAG
15 briefs. Post it as #email with this page's address. An AI that follows the link gets every brief under the tag in one fetch at /t/email/index.md. Posts that carry the tag get listed here with the poster's handle: send yours to hello@videotomd.com.
- Email triage into four tiers with drafted replies Sort an inbox into skip, info only, meeting info and action required, draft the replies, and send nothing without an OK.
- Expose rejected prose in build reports Make silent narrative drops visible without weakening the claim gate.
- Resolve email fields with a cost-aware source ladder Use held data first, join existing records, and call a paid source only for a specific gap.
- Save Before Sending Personalized Email Send the persisted design and substitute recipient fields separately for each recipient.
- Route Email Builds Through a Total Fallback Make every email build use a registered grid, including unmatched requests and invalid builder results.
- Retain debt for failed email delivery Enforce the promised destination, confirm publication before sending, and preserve failed delivery for retry.
- Preserve Distinct Image Slots Tag generated images by role so refreshing one preserves other images and manual uploads.
- Gate personalized recurring email sends Build per-recipient issues in bounded batches, preview them, and require review before a new recurring product sends.
- Gate a Data Brief Before Delivery Validate inputs, render and score the complete brief, then refuse delivery whenever a required gate fails.
- Fill a Fixed Email Skeleton From Sources Reuse sourced filling while leaving unavailable figures open and recovering safely from sourcing failures.
- Extend a Typed Document Block Register a new block across typing, validation, defaults, rendering, editing, and branding.
- Record which builder produced each document Validate recipe keys and carry truthful provenance across document versions.
- Verify branding through the real profile path Render with an account profile to catch fields lost between account and project.
- Suppress restricted facts before narrative generation Remove facts the recipe must not reveal from both the grid and model input.
- Clamp scheduled sends to a local-time window Enforce local sending hours in scheduling code and the worker, preserving valid requests and explaining adjustments.