Repository map
| Repository | Responsibility |
|---|---|
| storemesh-user-service | Identity, users, roles, sessions, HTTP and gRPC contracts |
| storemesh-product-service | Product catalog contract and future product ownership boundary |
| storemesh-inventory-service | Stock quantities and reservation ownership boundary |
| storemesh-order-service | Order lifecycle and cross-service commerce coordination |
| storemesh-helm-repo | Helm charts and chart release automation |
| storemesh-argocd-repo | Argo CD project and application definitions |
| storemesh-kind-cluster | Local multi-node Kind cluster configuration |
| storemesh-scripts | Repeatable local platform operations |
| storemesh-docs | Architecture, roadmap, and contributor guide |
| storemesh-frontend | Next.js, React, and TypeScript web storefront and admin dashboard |
| storemesh-android | Native Kotlin Android client using Jetpack Compose |
| storemesh-ios | Native Swift iOS client using SwiftUI |
Ownership rule
Application source, deployment configuration, and cluster bootstrapping remain separate so a service change cannot silently alter platform policy. Shared operational scripts contain no credentials and are safe to run repeatedly.