Programmable Messaging API · View 15 of 22 · Runtime
Decisions
- The lanes share Resolve, Pace and Settle and diverge only at Adapt, Submit and Receipt — that split is the adapter boundary made visible.
- RCS is drawn with an explicit capability probe and a fallback, because a rich message that cannot be rendered is a different message with a different price.
- The inbound lane runs the same stages in reverse and writes consent before the tenant is notified.
Assumptions
- Nine channels at full scope; the MVP ships one and the adapter contract is proven by the second.
- WhatsApp conversation pricing and SMS segment pricing are both expressed as rated usage per attempt.
Risks
- RCS receipts are frequently absent, which inflates the unknown rate for reasons that are not the platform's fault and will be read as if they were.