Shared Packages and Contracts
How shared packages support web, admin, API, worker, and mobile compatibility.
Update the smallest shared package that owns a contract.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
Shared packages cover database, contracts, validation, constants, types, configuration, edition identity, i18n, and design tokens. Package names and identifiers remain English; user-facing copy remains locale-ready.
| Check | Source-backed expectation |
|---|---|
| Scope | Do not duplicate API business rules in a client package. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | pnpm --filter @autocore/contracts 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/contracts 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.