Web and Admin Client Boundary
How client applications consume the shared API without owning business rules.
Keep fetch, presentation, i18n, and interaction concerns in clients; keep invariants in the API.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
Web and Admin use the same versioned API and shared contracts. Admin route visibility and permission UX must not be used as a substitute for server-side authorization.
| Check | Source-backed expectation |
|---|---|
| Scope | Mobile compatibility is a design constraint for every client-facing contract. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | pnpm --filter @autocore/web typecheck |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
pnpm --filter @autocore/web typecheck
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.