Legal Policy Lifecycle
Understand AutoCore legal policy types, revisions, publication, acceptance, and configuration boundaries.
AutoCore provides lifecycle and record-management capabilities for installation policies. It does not certify legal compliance, approve customer text, or replace jurisdiction-specific legal review.
Policy model
Policy revisions are installation-scoped and identified by type, locale, and
revision number. Current types are terms, privacy, cookies,
marketplace_rules, and refund. Each revision stores title, body, checksum,
status, effective/publication timestamps, and optional author identity.
Revision states
| State | Meaning |
|---|---|
draft | Editable candidate, not the current published policy. |
published | Publicly effective revision when its publication/effective dates allow it. |
superseded | Retained historical revision replaced by a later one. |
archived | Retained but not current or public. |
Acceptance records link an installation, policy revision, optional user, kind, locale, source, and timestamp. The record identifies what was accepted; it does not prove that the content is legally sufficient or that every visitor has a particular statutory right.
Configuration boundary
The customer supplies and approves legal text, publication timing, required or optional acceptance policy, and retention decisions. AutoCore supplies the recording model and lifecycle surfaces. Detailed Admin procedures and legal/ security operations belong to later phases.
Text alternative: a policy revision is drafted, reviewed, published, and later superseded or archived. Acceptance records identify the revision accepted and do not claim legal sufficiency.