Social
Это содержимое пока не доступно на вашем языке.
Canonical — Confirmed channel usage
Section titled “Canonical — Confirmed channel usage”Per Mascot Book — Usage Guidelines:
- Twitter/X: profile avatar and header, meme/GIF/reaction posts, announcements, engagement replies.
- Telegram: sticker pack, short reaction GIFs, bot avatar, announcement posts.
- Discord: role names, sticker set, bot avatars, channel icons, event announcements.
Canonical — Discord rank role names
Section titled “Canonical — Discord rank role names”The five rank titles are fully specified: Kit Raccoon (entry level) → Digger Raccoon (level-gated) → Stash Raccoon (level-gated) → Vault Raccoon (manually selected, not purely level-gated) → Galaxy Raccoon (Elite tier). These are rank/role labels distinct from the character’s own name (Sol Mamy) — the “Raccoon” suffix names the rank tier, not the character.
Why this counts as Canonical, unlike some other design-brief-sourced material in this system: these five names are cross-confirmed across two independent design-brief documents and directly underlie the Lunar Vault Module’s own five-state progression (Story & Universe Book — Progression), which is itself established fact. Contrast with narrative specifics (ship name, artifact names) in Story & Universe Book, which appear in only one authored document and are correctly kept at Proposed status.
Canonical — Community site usage
Section titled “Canonical — Community site usage”Beyond Discord/Twitter/Telegram, the community site itself has confirmed mascot usage: onboarding new members, explaining rules/mechanics via guides, visualizing rank progress, and announcing events/activities.
Character-attributed social content (posts written “as” Sol Mamy) uses Mascot Book — Personality & Voice. Institutional/announcement content with no character attribution uses Brand Book — Voice & Tone’s institutional register (Intelligent, Confident, Transparent, Technical, Selective, Modern — Proposed, SOURCE-DERIVED, pending final owner approval, per Brand Book’s own current status) — never Sol Mamy’s own in-character crypto-slang vocabulary (diamond hand, hold, stack, vault, flywheel, drop, wen, brrr, combo szn, old bags, much wow, very [X] — Mascot Book — Voice’s own exact list, Canonical), which is not part of SOLMAMY’s institutional voice. The real distinction is register (institutional vs. character), not entity ownership.
- Reaction GIFs/memes: any canonical or approved-variant appearance, matched to the reaction’s tone.
- Announcements: institutional voice per Brand Book — Voice & Tone, canonical mascot imagery where an image is used.
Do not use
Section titled “Do not use”- Do not blend character voice and institutional voice within a single post without making clear which is speaking.
- Do not use Sol Mamy’s own in-character crypto-slang vocabulary as SOLMAMY’s institutional voice, or present it as established SOLMAMY institutional vocabulary.
Canonical — Community gamification activities
Section titled “Canonical — Community gamification activities”The mascot has a confirmed role across a set of recurring community activities:
| Activity | Mascot’s role |
|---|---|
| Treasure Hunt | Hides clues and gives hints |
| Meme Battles | Judges and rewards entries |
| Quests | Assigns community tasks |
| Trading Contests | Announces winners |
| Mini-games | Appears as an in-Discord NPC |
| Charity Events | Collects donations |
These are community-engagement formats, not video/game production — they belong to social/Discord content, not Game Book.
Canonical — Treasure Hunter (horizontal role)
Section titled “Canonical — Treasure Hunter (horizontal role)”Distinct from the five vertical ranks above: a seasonal “Treasure Hunter” role, earned through wins in games/contests/activities, shown as a trophy-badge overlay on the member’s current rank badge. New winners are selected each season, synced with the monthly product cadence.
Part of the SOLMEME Brand Documentation System. Content status (Canonical/Proposed/Open/etc.) is this book’s own axis; ownership/rights are separate — see OWNERSHIP_AUTHORITY.md at the documentation system’s root.