1.0.0-rc.1 · Release Candidate2 min read
Lifecycle and State Reference
Consolidated source-verified state summaries for installation, listings, media, search, legal, consent, and payments.
This reference names states that are enforced by current enums, transition maps, or service behavior. Where the source has statuses but no formal transition engine, the table describes a service-controlled lifecycle rather than inventing transitions.
| Model | States or phases | Public/operational consequence |
|---|---|---|
| Installation | uninitialized → in_progress → initialized | Setup gates change; initialized is the ordinary completed boundary. |
| Listing | draft, pending_review, active, reserved, sold, expired, rejected, archived | Only active plus public category conditions enter current public search. |
| Media | pending, processing, ready, failed | Ready assets can be consumed; failed assets require retry or review. |
| Search | source projection, synchronized document, delayed/failed projection, PostgreSQL fallback | Meilisearch is derived; PostgreSQL remains authoritative. |
| Policy revision | draft, published, superseded, archived | Published content can be current; historical revisions remain records. |
| Dealer | profile draft, pending_review, active, suspended, archived; verification pending, verified, rejected, suspended | Public storefront directory requires active dealer status. |
| Payment provider | disabled, unconfigured, configured, verification_failed, verified, suspended | Readiness depends on configuration and gates; no default activation. |
| Payment webhook | received, processing, processed, ignored, failed | Signature and provider correlation precede state mutation. |
| Consent | decision recorded with policy version and expiry | A new choice/version is a new receipt; it is not legal certification. |
Lifecycle review rules
Entry conditions, allowed exits, and recovery behavior are owned by the relevant service or guard. Admin actions are audited where the source supports it. Worker involvement applies only to processing paths that are enabled; registered queue names alone do not prove active scheduling.
Related articles
Installation ConceptLearn how an AutoCore installation defines identity, initialization, configuration scope, and operational isolation.Listing LifecycleFollow the source-verified listing states, actions, ownership rules, and public-visibility consequences.Media DomainUnderstand AutoCore media assets, processing states, variants, ownership, storage, and failure boundaries.Legal Policy LifecycleUnderstand AutoCore legal policy types, revisions, publication, acceptance, and configuration boundaries.Payment Provider and ReadinessUnderstand AutoCore provider adapters, configuration states, readiness checks, and payment boundaries.