> For the complete documentation index, see [llms.txt](https://myros.gitbook.io/bp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://myros.gitbook.io/bp/brand-assets.md). # Brand Assets #### Brand Guidelines {% embed url="" %} Download: {% file src="/files/Dz7Jl1zHxr7txEl5MRlD" %} #### Myros Partnership Template (Optional)
*** #### Asset Access & Usage Rules Official Myros assets will be shared through a private Collab Pack distributed inside approved private groups. Access will be granted to: * Media and press contacts * Ecosystem collaborators and partners * Builders contributing to Myros * Community operators deploying or supporting Myros agents All assets will be: * Versioned with clear update notes so collaborators know which files are current * Shared through the private group for controlled access and distribution * Licensed for permitted use by press, partners, builders, and approved collaborators * Protected against unauthorized modification, resale, misleading use, or implied endorsement * Documented with usage guidance, including clear-space rules, minimum size rules, light and dark variants, and misuse examples * Delivered in practical formats such as SVG and PNG for logos, with standardized sizes for icons, banners, screenshots, and social visuals #### Unified Presence Consistent use of Myros assets helps preserve the feeling of a living intelligence layer. Every logo, visual mark, interface preview, and written reference should reinforce the same presence: minimal, intelligent, futuristic, and quietly powerful. Until official assets are released through the private Collab Pack, avoid unofficial variations, altered logos, recolored marks, recreated typography, or unapproved visual treatments. Myros should feel recognizable wherever she appears. One identity.\ One signal.\ One mind for living knowledge. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://myros.gitbook.io/bp/brand-assets.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.