Contracts, Validation, and Error Codes
Where HTTP schemas, pagination, and error codes are defined.
Change shared contracts before changing clients and keep runtime validation aligned.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
packages/contracts owns API version/prefix, error codes, pagination response types, and domain DTO schemas; packages/validation supplies reusable validation. Zod validation is applied globally in the API.
| Check | Source-backed expectation |
|---|---|
| Scope | Do not invent enum values or response shapes in client code. |
| 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.