0015. MVP scope with time-based triggers and SES
- Status: Accepted
- Date: 2026-11-08
- Supersedes: 0004
Context
Section titled “Context”ADR 0004 fixed the MVP scope with event triggers only and left the first email provider open. Reminders such as “3 days before the trial ends” and weekly digests need time-based triggers, and the email provider is now Amazon SES (ADR 0024).
Decision
Section titled “Decision”In scope:
- Customer and event APIs.
- Inbound webhooks from external services: a per-source endpoint, signature verification, and a JSON-to-event/customer mapping that the user’s AI assistant drafts from a sample payload.
- Workflow triggers: events, and time-based triggers (
attribute_date,schedule,once) as defined in ADR 0016. - Workflow steps: trigger, delay, condition, send email, send outbound webhook, exit.
- Workflow goals: a workflow-level exit condition, rechecked before each send; a run whose goal is met exits with
exited:goal_met. - Re-entry policies and stop behaviour from ADR 0017.
- Outbound webhooks with HMAC signing, retries, idempotency keys, timeouts, SSRF protection, and secrets kept out of logs.
- Templates, unsubscribe (including RFC 8058 one-click for marketing mail), suppression, and an eligibility recheck immediately before each send.
- Email through Amazon SES on the managed service.
- Test runs that skip delays, are marked as tests, and can simulate the current time for time-based triggers.
- Per-step logs that explain why a message was or was not sent.
- Click tracking (ADR 0020).
- MCP for creating, inspecting, and operating everything above.
- Dashboard sign-in, workspaces, roles, and API keys (ADR 0025, ADR 0026).
Customer.lite does not configure external services, such as registering a Stripe webhook. The AI assistant gives the user instructions instead.
Deferred: open tracking, in-product AI agent, AI steps in workflows, SMS and push, external setup on users’ behalf, complex visual editor, recurring schedules more frequent than daily, external identity providers and SSO.
Every MVP feature follows the core invariants in ADR 0007.
Consequences
Section titled “Consequences”- The first email provider is decided (SES); the email adapter interface stays provider-neutral.
- The container self-host path (
apps/nodeon Postgres) is required before the open-source release, not for the managed MVP (ADR 0008).
Amendment (2026-11-19, the maintainer’s decisions, recorded in ADR 0046 and ADR 0048, Proposed): open tracking moves from deferred into the first release, on by default for marketing mail and never for transactional mail, with opens reported only as estimates (ADR 0046); A/B experiments on send steps, with a holdout, enter the first release (ADR 0048). Saved audiences (ADR 0045), analytics reports (ADR 0047), and broadcasts (ADR 0049) are added to scope, Proposed.
Amendment (2026-11-20, ADR 0051, decided by the maintainer): MCP OAuth is in scope for the first release, so claude.ai, ChatGPT, and Claude Code connect to /mcp without an API key. How it is built is Proposed in ADR 0051: Better Auth’s MCP authorization server with Client ID Metadata Documents, a consent page in the dashboard, and grants that act as their user on one project, built in slices behind MCP_OAUTH (Claude Code first, then claude.ai and ChatGPT, then revocation).