Setup, Installation, Legal, and Privacy APIs
The boundary between public policy surfaces and installation/operator control.
Keep installation control routes private while publishing only the legal and privacy behavior needed by clients.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
Setup and system routes are internal-only in the source classification. Legal/privacy routes may be public or authenticated depending on controller metadata; published policy content is distinct from the guarded mutation workflow.
| Check | Source-backed expectation |
|---|---|
| Scope | This documentation is product behavior, not legal advice or an installation credential guide. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | curl -i https://api.example.invalid/api/v1/privacy |
| 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.
curl -i https://api.example.invalid/api/v1/privacy
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.