# Welcome

Welcome to the **RWA Tokens Marketing Wiki** — the central library for everything we publish about the platform to the outside world. Articles, pitch decks, the lightpaper, investor presentations, SEC filings and staff statements we cite, regulatory commentary, and ongoing news coverage all live here, organized so the comms team, partners, and counsel can find the right asset for the right audience without rebuilding it from scratch.

You'll find collateral grouped by the three asset-class modules — **Equities (ST22), Real Estate, and CORECM** — alongside cross-cutting materials that apply to the platform as a whole: corporate-identity assets, SEC regulatory framework references (Release No. 33-11412, the January 28, 2026 Joint Staff Statement, the April 13, 2026 Covered User Interface Providers statement), and the live news and X/LinkedIn campaign archive. Each item is tagged by audience (institutional investor, issuer prospect, regulator, press) and by stage (draft, internal review, legal-cleared, published) so nothing ships externally without the right approval state.

This wiki is the canonical source for any RWA Tokens marketing artifact under the Groovy Company, Inc. brand (the "OTCM Protocol" dba was retired May 1, 2026; CEDEX, ST22, and GROO remain as product and instrument names). Platform URL is [**https://rwatokens.net**](https://rwatokens.net/); trading venue is **cedex.market**. When in doubt about which version of a deck or letter is current, this wiki is the answer — anything found elsewhere should be checked against the version here before sending.

#### &#x20;<a href="#join-our-community" id="join-our-community"></a>


---

# Agent Instructions: 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://bitbook.rwatokens.net/foundation/welcome.md?ask=<question>
```

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.