Code-derived guides to the API, GitHub App automation, and Mailer runtimes and their boundaries.
The three backend services form a trust chain, but each remains independently deployable and owns a different kind of state.
| Service | Public trust boundary | State it owns | Main downstream dependency |
|---|---|---|---|
| API | authenticated Portal requests | Better Auth, permissions, proxy settings | GitHub App and Mailer |
| GitHub App | internal API requests only | durable operation records and resource leases | GitHub repositories |
| Mailer | internal bearer-authenticated requests | no application database | SMTP provider |
The API contracts page is the canonical transport reference, Environment variables is the configuration inventory, and Operations owns deployment and recovery procedures. These service guides explain how the implementation joins those pieces together.
