Usage Rules

Это содержимое пока не доступно на вашем языке.

Allowed usage

Using the mascot as the sole visual mark in any first-party context.
Using the institutional voice register and Foundation drafts (flagged Canonical or Proposed as stated) in copy.
Using the cyan/teal/pearl-white/pink (multi-element accent, not bow-only) color direction — no gold in this costume/brand palette (one unrelated, already-classified legacy site asset uses gold; see Color System for that exception). Exact digital hex values are now measured and PROPOSED (see Color System); confirm current status there before treating a specific hex as final.

Prohibited usage

Designing or commissioning a second logo/mark.
Inventing exact color hex codes, font choices, or a formal Brand Story to fill a currently open gap.
Presenting any Foundation element (mission, vision, tagline, etc.) as finally adopted before an owner decision.
Using Sol Mamy’s own in-character crypto-slang vocabulary (diamond hand, stack, brrr, flywheel, wen, combo szn, and similar — Mascot Book — Voice’s own exact wording) as SOLMAMY’s institutional voice. This vocabulary is Sol Mamy’s own in-character speaking voice (Mascot Book — Voice, Canonical), not SOLMEME’s — the real distinction is register (institutional vs. character), not entity ownership.
Implying SOLMAMY currently has users, revenue, or a live product — it has not launched (Foundation — Status).

Do / Don’t example

Do: “SOLMAMY is a trusted launch and discovery infrastructure being built around transparent, verifiable project information.” (institutional register, correct pre-launch framing) Don’t: “Diamond hands stack through every drop — the Vault goes brrr.” (Sol Mamy’s own in-character vocabulary, not SOLMAMY’s institutional voice) Don’t: “SOLMAMY’s users already trust our Reputation scores.” (implies a live product that does not exist yet)

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.