> For the complete documentation index, see [llms.txt](https://docs.metacces.com/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metacces.com/whitepaper/team/core-7-values.md). # Core 7 values At Metacces, we believe that building a truly integrated digital future starts from within — with a team that stands by the right principles, works with passion, and engages authentically with its community. ## Human-Centered Thinking * We design technology for people — not the other way around. * Every decision and experience in Metacces begins with one question. * How can we give users real value and deeper meaning? *** ## Decentralization with Purpose * We don’t use Web3 as just a tool — we embody it as a philosophy. * Users are given real ownership of decisions, resources, and outcomes. *** ## Play as Growth * We redefine the purpose of gaming — not as escape, but as a means of discovery, self-expression, and building a digital identity for a new era. *** ## Radical Innovation * We reject off-the-shelf solutions. * strive to create never-before-seen concepts that blend augmented and real worlds, AI, Web3, and symbolic philosophy. *** ## Transparency & Integrity * We keep our community informed, design with openness, and value user input as part of the decision-making process. *** ## Clan Spirit * We believe a real team operates like a digital clan — celebrating wins together, sharing challenges, and growing as one living entity. *** ## Digital Responsibility * We hold ourselves accountable for the digital worlds we build — in how they impact society, the environment, AI, AR/VR, and Web3 ethics. *** Metacces is an extension of our values before it is a project.\ We design, innovate, and build because we believe in a smarter, more human digital world. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.metacces.com/whitepaper/team/core-7-values.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.