Developer Guide Overview
The source-backed map for building, testing, and extending AutoCore.
Start with repository boundaries, edition identity, contracts, and local verification.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
AutoCore is a pnpm/Turborepo monorepo with API-first business logic, shared packages, web/admin clients, and a worker. The /docs hierarchy in the source repository remains the implementation authority; this public guide records verified developer behavior.
| Check | Source-backed expectation |
|---|---|
| Scope | Use a clean branch, explicit AUTOCORE_EDITION, and small phase-based changes. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | pnpm 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 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.