AutoCore Legal Architecture Overview
How installation-scoped legal identity and policy publication fit together.
The legal model is installation-scoped. A legal profile identifies the operating entity and publication readiness; policy revisions carry type, locale, revision, status, effective time, author, and checksum.
Release candidate source
This article reflects the audited AutoCore source revision 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60 and immutable release-candidate tag v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f. Configuration and external provider behavior remain deployment-dependent.
Source boundary
| Control | Source-verified behavior |
|---|---|
| Legal profile | Stores public identity and governance fields; incomplete profiles cannot pass publication readiness. |
| Policy revision | Terms, privacy, cookies, marketplace rules, and refund revisions are versioned and status-controlled. |
| Public rendering | Only published policy content is exposed by the public legal route; drafts stay in the operator workflow. |
| Boundary | Documentation explains product behavior and operator evidence, not legal advice or compliance certification. |
Operational controls
Use the smallest verified control for the task. Keep provider, host, legal, and operator responsibilities separate from application behavior. When a control is not implemented or not verified, leave it disabled or mark it as a limitation.
Verification
Verify the route, relevant API or configuration state, negative path, audit/evidence result, and public effect before closing the task. Record unknown or configuration-dependent behavior as a limitation.