PickupHub Internal Engineering Wiki
Internal documentation of PickupHub architecture, business domains, cross-domain workflows, integrations, operational behavior, ownership boundaries, and important exceptions.
Internal documentation of PickupHub architecture, business domains, cross-domain workflows, integrations, operational behavior, ownership boundaries, and important exceptions.
The wiki is organized around system concepts, workflows, and ownership boundaries. Each section connects the decisions and exceptions that engineers and operators need to understand together.
| Section | Scope | Pages |
|---|---|---|
| System Architecture | Runtime surfaces, request boundaries, client generations, and asynchronous execution within the Laravel monolith. | 5 |
| Identity and Accounts | Player and provider authentication, onboarding, privacy, dependent accounts, media, and personal configuration. | 8 |
| Discovery and Hub | Personalized game discovery, saved filters, global search, and public provider presentation. | 4 |
| Games and Participation | The game aggregate, registration windows, position ownership, waiting lists, provider management, and cancellation behavior. | 7 |
| Payments and Ledger | Purchase orchestration, payment instruments, transaction records, preauthorization, e-transfer reconciliation, refunds, and passes. | 7 |
| Provider Operations | Organization tenancy, permissions, operational workspaces, catalog ownership, and privileged support access. | 6 |
| Reporting and Audit | Operational metrics, program analysis, embedded reports, and durable records of sensitive actions. | 4 |
| Delivery and Integrations | Notifications, broadcasting, maps, image services, media storage, short links, and browser runtime configuration. | 4 |
| Production Operations | Automated business tasks, service topology, health monitoring, deployment, previews, and safe database synchronization. | 5 |