> For the complete documentation index, see [llms.txt](https://spawnmeme.gitbook.io/spawnmeme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spawnmeme.gitbook.io/spawnmeme-docs/whitepaper/13-ecosystem.md).

# 13. Public resources and participation

## A public information layer

SPAWN's public repository provides platform guides, a roadmap overview, creator preparation material, community links and media resources. It supports a more inspectable, versioned record of how the platform is described.

The repository does not contain the production application or its private deployment configuration. Publishing documentation on GitHub does not make the entire platform open source or grant unrestricted rights to its branding. Reuse is subject to the repository's rights notice.

## Official destinations

| Resource           | Destination                                                   |
| ------------------ | ------------------------------------------------------------- |
| Platform           | [spawnmeme.com](https://spawnmeme.com/)                       |
| GitHub             | [spawnmeme/spawnmeme](https://github.com/spawnmeme/spawnmeme) |
| Medium             | [@spawnmeme](https://medium.com/@spawnmeme)                   |
| X                  | [@SpawnMemeX](https://x.com/SpawnMemeX)                       |
| Telegram community | [The Nest](https://t.me/spawnmemetg)                          |
| Trending channel   | [SPAWN Trending](https://t.me/spawntrending)                  |
| Telegram bot       | [@spawnmeme\_bot](https://t.me/spawnmeme_bot)                 |
| Roadmap            | [The Hatching Plan](https://spawnmeme.com/roadmap)            |
| Support            | [Help](https://spawnmeme.com/help)                            |

## How to contribute

Participants can report unclear documentation, describe reproducible interface issues and propose features around actual tasks. A useful report includes the relevant page, the expected result and what happened. Private credentials and exploitable security details do not belong in a public report.

Creators contribute by publishing clear project information, maintaining their links and explaining their own commitments accurately. Community members contribute by asking specific questions, sharing constructive feedback and distinguishing verified information from speculation.

## Direction

SPAWN's intended contribution is a connected environment for turning ideas into public projects and maintaining the activity around them. Its development priorities combine creative tools, practical transaction flows and community participation, with clear boundaries between what the platform provides and what each creator is responsible for.

***

[Previous: 12. Roadmap: The Hatching Plan](/spawnmeme-docs/whitepaper/12-roadmap.md) · [Next: 14. References and edition notes](/spawnmeme-docs/whitepaper/14-references.md)


---

# 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://spawnmeme.gitbook.io/spawnmeme-docs/whitepaper/13-ecosystem.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.