## App map

Brothh is split across website, seller, facility, markets, admin, and git_book. Legal and documentation content should point back to git_book when it is reader-facing.

{% figure src="/docs-images/gitbook-platforms.png" alt="GitBook platforms overview page" caption="The platforms overview shows how the Brothh apps relate so cross-app docs can set boundaries before linking readers into the owning surface." /%}

## How the apps relate

- **website** is the public buyer and marketing surface.
- **seller** is the producer-facing operating system.
- **facility** is the facility operator experience.
- **markets** is the organizer-facing market workspace.
- **admin** owns internal operations and the shared Convex backend.
- **git_book** is the public documentation and legal surface.

## Admin relationship

The admin app owns the Convex backend and docs authoring surfaces.

## Cross-app rule

When you are documenting a workflow that spans apps, use GitBook to explain the boundaries between apps first, then link readers into the owning product surface for the authenticated work.