# Oshun V1 Messaging Boundary

This is the release boundary for third-party messaging channels. Messaging is
customer-tier and curated-creator-tier only. Operator, admin, AAA-tier
generation, privacy management, consent management, payment management, and
model-promotion workflows stay in authenticated Oshun web or admin surfaces.

| Channel           | Content classes                                                                            | Residency              | Retention                                         | Consent                                                           | Provenance and disclosure                                          | Audit events                                         |
| ----------------- | ------------------------------------------------------------------------------------------ | ---------------------- | ------------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------ | ---------------------------------------------------- |
| Telegram bot      | Grounded Q&A, Tara reminders, identity verification, crisis resources                      | Global                 | 30-day operator audit, chat memory off by default | Verified Login Widget binding; explicit remember-from-chat opt-in | Body-copy AI disclosure, source count, confidence, provenance link | receive, send, crisis suppression, revocation        |
| Telegram Mini App | Today, Sophia, Veritas, Nyx, Arete, Nisaba, curated illustration                           | Global                 | Session-scoped, server re-verifies initData       | Verified initData and scoped JWT                                  | Same disclosure and provenance as web                              | initData verify, entitlement resolve, surface access |
| Telegram channel  | Veritas briefings, Nyx alerts, Tara programs, Arete reflections, Nisaba passage-of-day     | Global                 | Channel default plus Oshun audit                  | Operator-managed channel binding                                  | Disclosure in post body, evidence CTA, UTM attribution             | scheduled publish, embargo, takedown                 |
| WhatsApp Business | Approved transactional templates only                                                      | Global                 | 30-day channel audit                              | Meta-compliant opt-in and approved template                       | Body-copy disclosure where relevant                                | template send, status webhook, opt-out               |
| Email             | Transactional, billing, reminders, grounded summaries, editorial briefings                 | Tenant mail region     | 365-day support audit                             | Verified email, DKIM/SPF/DMARC, unsubscribe                       | Body-copy disclosure and provenance footer                         | send, bounce, complaint, unsubscribe                 |
| Push FCM          | Android/web reminders, action nudges, silent sync                                          | Google provider region | 30-day delivery audit                             | Device grant and tenant allowlist                                 | Payload metadata and deep-link provenance                          | send, receipt, revoke                                |
| Push APNs         | iOS reminders, action nudges, silent sync                                                  | Apple provider region  | 30-day delivery audit                             | Device token grant and tenant allowlist                           | Payload metadata and deep-link provenance                          | send, receipt, revoke                                |
| SMS               | Verified reminders, login codes, password reset, billing alerts, crisis hotline escalation | Provider region        | 30-day delivery audit                             | Double opt-in; US A2P 10DLC                                       | Body-copy where length permits                                     | send, status webhook                                 |
| Slack             | Institutional Metis commands and notifications                                             | Workspace policy       | Workspace policy plus Oshun audit                 | OAuth install and Metis institution binding                       | Body-copy disclosure and source links                              | OAuth, command, uninstall                            |
| Discord           | Creator-community coordination only                                                        | Server policy          | Server policy plus Oshun audit                    | Bound community server                                            | Body-copy disclosure and source links                              | OAuth, command, uninstall                            |

Memory ingestion from chat is denied unless the user explicitly enables
remember-from-chat for that channel. Every durable memory write carries channel
ID, external message ID, retention class, and redaction rules.

Revoking a channel binding terminates Mini App sessions, cancels scheduled
sends, removes chat-state caches according to retention policy, and posts a
revocation notice where the channel supports it.

Any crisis flag suppresses non-essential sends across every channel for the
affected user until cleared with operator audit and user-visible notice.
