Skip to content
Community226

Video

Any video featuring Sol Mamy uses her canonical appearance and personality exactly as defined in Mascot Book — Visual Identity and Mascot Book — Personality & Voice. This chapter adds only what’s specific to the video medium.

  • Sol Mamy’s established personality (playful, mischievous, resourceful) should carry into motion and performance, not just static appearance.
  • Any costume shown should be a canonical variant (R1/R2) or an approved Design Variant — see Mascot Book — Design Variants for both — never an invented one-off costume for a single video.
  • Do not redesign her appearance, proportions, or silhouette “for video” — the same invariants apply regardless of medium.
  • Do not attribute institutional Brand voice (Brand Book — Voice & Tone) to her when she is speaking in-character.
  • A formal reference/exemplar video establishing general motion and camera rules does not exist yet. Full video production rules (beyond this brand-level chapter) are a separate, not-yet-produced deliverable — this chapter states the brand constraints that will govern them once they exist, not the production rules themselves. Real production-pipeline/technical-implementation material exists elsewhere (camera-movement vocabulary for AI video-generation prompting, motion-transfer technical specs), but that category is exactly what this book’s own Purpose/Scope excludes (“does not cover editing pipelines, rendering, software, or technical workflow”) — none of it states a brand-level motion or camera rule, so this gap is genuine, not an oversight.

Do: A video opens on Sol Mamy in R1, playful expression, gesturing toward the Lunar Vault Module (her signature prop — see Mascot Book — Costume & Design System; Story & Universe Book — Progression). Don’t: A video redesigns her in an unapproved costume with a different proportion system “for a cinematic look.”


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.