> For the complete documentation index, see [llms.txt](https://docs.selcier.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.selcier.xyz/reference/name-and-channels.md).

# Name, voice and contact

The correct way to write Selcier, the voice Selcier writes in, and the only official places it can be reached.

## Spelling and naming

* Write **Selcier** as one word, with only its first letter capitalized. Running text never puts it in all capitals, and no abbreviation exists.
* Product names lead with it, as in **Selcier Console**, **Selcier Portfolio**, **Selcier Explorer** and **Selcier API**. Once a page has used the full form, plain "Console", "Portfolio" and "Explorer" will do.
* The tokens are **Selcier Share Tokens** on first mention, and "share tokens" from then on. Stay away from "coins" and "crypto stocks".
* The phrase for how Selcier relates to the network is always **built on Robinhood Chain**. As an independent company, Selcier must never be called a partner of, endorsed by or affiliated with Robinhood. The same goes for any company that has not onboarded.

## Tone of voice

The model is infrastructure writing: calm, exact and technical, and something a CFO would be comfortable forwarding to the board.

1. **Accuracy before promotion.** Point to the specific contract, event or rule. A phrase like "fully secure" tells the reader less than "holding periods enforced at the contract level".
2. **Let the mechanism speak.** Adjectives give way to interfaces, tables, transaction hashes and Explorer links.
3. **Treat the reader with respect.** Before someone acts, tell them in plain language what the action does and what cannot be reversed.
4. **Skip crypto slang.** Memecoin imagery, "airdrop", "degen" and "moon" have no place here. The vocabulary to use is "holders", "settlement", "share classes" and "stock tokens".
5. **Keep sentences plain.** One idea at a time, in the active voice, in brief paragraphs, and with no exclamation marks.

### Preferred and rejected terms

| Instead of                   | Write                      |
| ---------------------------- | -------------------------- |
| Crypto stock, coin           | Stock token, share token   |
| Bag holder, whale, degen     | Shareholder, holder        |
| Pump, unlock event           | Liquidity Window           |
| Price action, moon           | Clearing price, settlement |
| Partnered, official          | Issuer-sponsored           |
| The masses, anyone, everyone | Eligible investors         |

## Example lines

* **Headline:** Equity infrastructure built for tomorrow's companies.
* **Subhead:** Private companies use Selcier to bring stock tokens to Robinhood Chain, where issuance, transfers and corporate actions all settle in public view.
* **Calls to action:** Begin tokenizing · Browse the docs · Open in Explorer
* **Trust line:** ERC-3643 · Issuer-sponsored · Settles to Ethereum through Robinhood Chain
* **One line:** Payments infrastructure gives commerce a programmable layer in place of a slow, manual process. Selcier does the same for private-company equity, through an API.

## Where to find Selcier

| Channel           | Address                                                        |
| ----------------- | -------------------------------------------------------------- |
| Website           | [selcier.xyz](https://selcier.xyz)                             |
| Documentation     | [docs.selcier.xyz](https://docs.selcier.xyz)                   |
| Console           | [app.selcier.xyz/console](https://app.selcier.xyz/console)     |
| Portfolio         | [app.selcier.xyz/portfolio](https://app.selcier.xyz/portfolio) |
| Explorer          | [explorer.selcier.xyz](https://explorer.selcier.xyz)           |
| API               | `https://api.selcier.xyz/v1`                                   |
| X                 | [@Selcier](https://x.com/Selcier)                              |
| GitHub            | [github.com/selcier](https://github.com/selcier)               |
| General enquiries | <hello@selcier.xyz>                                            |
| Support           | <support@selcier.xyz>                                          |
| Security reports  | <security@selcier.xyz>                                         |

{% hint style="warning" %}
A request for your seed phrase or private key does not come from Selcier, and neither does an email or direct message asking you to send funds to an address. Contract addresses appear in the Explorer and through `GET /v1/contracts`, and nowhere else. If a domain, handle or address is anything else, assume it is not Selcier.
{% endhint %}


---

# 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.selcier.xyz/reference/name-and-channels.md?ask=<question>&goal=<user_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.