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

# Repository layout

The organization is `StoneForgeTeam`.

| Repository                                                         | Contents                                                                                          | Versioning                                                                   |
| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| [StoneForge](https://github.com/StoneForgeTeam/StoneForge)         | API, loader, native bridge, patcher, source generators, DataDump, tests and build/install tooling | One coordinated StoneForge release                                           |
| [ExampleMod](https://github.com/StoneForgeTeam/ExampleMod)         | Sample C# code, GML, assets, manifest and editor project                                          | Independent mod versions; `mod.json` declares the minimum StoneForge version |
| [StoneForgeDocs](https://github.com/StoneForgeTeam/StoneForgeDocs) | This documentation, published with GitBook                                                        | Follows StoneForge releases                                                  |

Keep the code checkouts as siblings, with the sample folder named `ExampleMod`. There are no submodules or project references between them. The sample references the API and GML generator from an installed StoneForge release; its README explains SDK configuration and installation.

The API, bridge and loader share runtime contracts. The patcher, DataDump and generators also depend on the same game-data and generated-code conventions. Keeping them together lets a change to these contracts be built, tested and released as one unit. Documentation lives in StoneForgeDocs; a StoneForge change that alters documented behavior should update the matching page for the same release.

Third-party libraries remain pinned under `lib/`, with their licenses, source provenance and rebuild tooling. The small Aurie and YYToolkit patches stay alongside their pins. Separate forks are unnecessary for the current scope. A dedicated Aurie fork would make sense if native changes grow enough to need their own releases or upstream collaboration.

Regression fixtures stay in the main repository so its tests do not require the sample checkout. New independent mods can follow ExampleMod's repository structure.


---

# 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://stoneforgeteam.gitbook.io/stoneforgeteam-docs/development/repositories.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.