Evidence level: historically reviewed source and owner proposals; not freshly tested or certified for production.
Design and implementation invariants
- The customer mini app is static presentation: identity, balances, purchase admission and order status are handled by Commerce/Wallet owners.
- Ingress must route application pages and Commerce APIs to their separate recipients while preserving customer authentication and correct endpoint origins.
Verification still required
- Check authorized real Commerce customer endpoints, request idempotency and wallet/Executor coordination before claiming an end-to-end purchase.
- Review third-party client assets and non-root web-server deployment as separate frontend hardening work; static build success does not verify live proxy routing.
How to update
When the owner changes implementation or contract behavior, update this page and the relevant service interfaces. For cross-service changes, also update the platform interface map or decision register. State the actual verification performed; do not inherit historical pass claims without fresh evidence.