Community Stream
Communication Plan
A platform-by-platform strategy for explaining Stables, routing feedback, growing useful community attention, and keeping Navi and Dashboard indicators connected to communication work.
Explain
Make the Charter, Demo status, Navi cards, Dashboard indicators, and community participation routes legible before asking for broad attention.
Route
Send each audience to the right action: read, review, ask questions, join groups, test Demo flows, or prepare ambassador and merchant work.
Measure
Connect publication output, reach, engagement, feedback, and agent questions to Dashboard metrics and Navi card progress.
Social Profiles
| Channel | Status | Primary Role | Dashboard Measures |
|---|---|---|---|
| X | Live | Fast public updates, release notes, short threads, response routing. | x_followers, x_recent_posts, x_engagement_actions |
| Live | Visual education, product screenshots, ambassador stories, short reels. | instagram_followers, instagram_recent_posts, instagram_engagement_actions | |
| Facebook Page | Live | Public explainers, local merchant/community announcements, event-style updates. | facebook_page_followers |
| Facebook Group | Live | Community discussion, questions, feedback prompts, ambassador/merchant interest. | facebook_group_members |
| YouTube | Baseline pending | Longer explainers, demos, walkthroughs, recorded Q&A, ambassador education. | youtube_subscribers, youtube_recent_views |
| TikTok | Baseline pending | Short education clips, simple user benefits, merchant discovery, visual summaries. | tiktok_followers |
| Twitch | Optional | Live build sessions, reviews, community walkthroughs, release inspection. | twitch_followers |
| Moltbook | Optional | StablesAgent social presence and community discovery surface. | moltbook_followers |
| Telegram Community | Community members | Member discussion, questions, support routing, and early coordination after people have chosen to join. | telegram_community_members, telegram_community_messages |
| Telegram Council | Community members | Official Council notices, controlled announcements, and security-sensitive updates for people already following the project. | telegram_council_members, council_official_ready |
| Discord | Community members | Working groups, longer-form discussion, technical review, and contributor coordination. | discord_members |
Platform Strategy
General-public channels explain Stables outward. Telegram and Discord are intentionally treated as community-member coordination spaces: they support people who already opted into discussion, review, support, or contribution.
| Platform | Audience | Content Cadence | Content Types | Next Action |
|---|---|---|---|---|
| X | Crypto-native builders, Minima users, fast-moving observers. | 3-5 posts per week once Demo package is coherent. | Release notesShort threadsFeedback asks | Draft the Navi/Dashboard launch thread and one Demo-review thread. |
| Visual-first users, merchants, ambassadors, local community leads. | 2-3 posts or reels per week after the first visual set is approved. | ScreenshotsReelsMerchant stories | Create a first visual pack: wallet, ambassador, merchant, dashboard. | |
| Local communities, merchants, non-crypto participants, long-form readers. | 2 posts per week plus group prompts when a clear question exists. | ExplainersGroup questionsLocal updates | Prepare an introductory pinned group post and a merchant-facing explainer. | |
| YouTube | People who need demos, walkthroughs, and longer proof of how the system works. | 1 video per major public milestone. | WalkthroughsCouncil explainersDemo reviews | Outline a 5-minute Navi and Dashboard walkthrough. |
| TikTok | Short-form discovery audience and mobile-first education viewers. | Only after the visual message pack is stable. | Short explainersMerchant hooksMyth/fact clips | Hold until we have three approved short scripts. |
| Twitch | Live-review audience and contributors who want to inspect progress directly. | Optional; use only for meaningful build/review sessions. | Live walkthroughReview sessionQ&A | Keep as optional until Demo review sessions justify live format. |
| Telegram | Community members, early contributors, support seekers, and Council-following members. | Short updates around real milestones; weekly digest when enough changed. | Member noticesQuestionsReview routing | Define which updates belong in Community versus Council Official. |
| Discord | Working contributors, technical reviewers, and longer-form community coordination. | Asynchronous working threads; weekly summary when active. | Work threadsReview notesTask routing | Set the first working group channels and link them back to Navi cards. |
Immediate Work
Baseline the channels
Record the first weekly manual values for followers, members, posts, engagement, and views in Dashboard inputs.
Build the first content queue
Create five posts tied to Navi cards: launch explanation, Demo review, feedback intake, ambassador path, and Council/Charter draft.
Publish only what is true
Every post should name the correct Dapp phase and avoid implying Test or Prod mechanics before they exist.
Route feedback visibly
Questions and reactions should become Dashboard signals, feedback entries, StablesAgent gaps, or Navi card next steps.
