Skip to content

COMM-013: default render fallback is the platform tier's own template - #103

Merged
agreenspan merged 1 commit into
mainfrom
feat/email-platform-fallback
Sep 10, 2026
Merged

agreenspan merged 1 commit into
mainfrom
feat/email-platform-fallback

Conversation

@agreenspan

Copy link
Copy Markdown
Contributor

Follow-up ruling after #102 merged: the default when a branded render has an issue (or cannot be composed) is to re-render the platform tier's own row of the same slug — unbranded but stable — so the mail still goes out. fail becomes the opt-in for a template that would rather wait and be fixed. degrade and an explicit substitute slug are unchanged. A render that already resolved at the platform tier has nowhere to fall back to and fails as before. Every fallback must render clean.

Tests: apps/api/src/lib/emailTemplate.test.ts — a broken Organization-tier template sends the platform version; the platform tier's own issue still refuses; fail opt-in refuses instead of unbranding.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Uyo2oHpjDz4zjRyqRWH6bP

…w — unbranded, stable, still sent; fail is the opt-in

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Uyo2oHpjDz4zjRyqRWH6bP
@agreenspan
agreenspan merged commit 23abfe4 into main Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant