1.0.0-rc.1 ยท Release Candidate3 min read
Terminology
Shared definitions for AutoCore installation, edition, market, applications, listings, policy, payment, and release terms.
Use these definitions consistently across AutoCore documentation. When a later page introduces a narrower domain term, it must preserve the meaning here or record the change in the governance plan.
| Term | Definition |
|---|---|
| Installation | One AutoCore product/data boundary with persisted initialization state, edition identity, configuration, and a primary market. |
| Edition | A governed branding and configuration profile materialized from the shared AutoCore platform. |
| Primary market | The installation's country, region, city, locale, currency, timezone, distance unit, and enabled vehicle capabilities. |
| Marketplace | The public and administrative product workflows used to discover, create, review, publish, and maintain vehicle listings. |
| Admin | The authenticated administration application and the administrative API capabilities behind it. |
| API | The versioned server-side HTTP boundary where validation, authorization, business logic, and persistence are owned. |
| Worker | The background application that consumes queues and performs asynchronous or scheduled processing. |
| Dealer | A seller organization or managed commercial participant represented in marketplace workflows. |
| Seller | The person or account that owns or manages a listing within the supported seller model. |
| Listing | A marketplace record describing an available vehicle and its publication, moderation, seller, media, and catalog relationships. |
| Vehicle | A catalog-validated passenger-car record or the vehicle data associated with a listing. Additional categories remain gated scope. |
| Media asset | A stored image or other supported media record associated with a vehicle, listing, dealer, or content surface. |
| Media variant | A derived representation of a media asset, such as a resized or optimized image used for a particular delivery context. |
| Policy revision | A versioned legal or informational policy record that can move through draft and publication states. |
| Acceptance record | A durable record that a user accepted a particular policy revision or consent purpose at a point in time. |
| Payment readiness | The configuration and state that indicate whether a provider is prepared for a payment flow; it is not proof that live charges are enabled. |
| Provider | An external or internal adapter that supplies a service such as storage, email, SMS, or payments. |
| Installer | The controlled installation package and command flow that performs preflight, setup, verification, and supported operational actions. |
| Installation manifest | A release or installation record describing the selected edition, version, artifacts, services, and verification metadata without secret values. |
| Rollback plan | A reviewed sequence for returning application artifacts and, only when compatible and authorized, data state to a prior known-good boundary. |
| Release Candidate | A release version that has passed its defined technical verification boundary but is not represented as a stable release or a completed commercial contract. |
Terms that must not be conflated
- An edition is not a market; a market is not a deployment host.
- Payment readiness is not payment activation, and a provider adapter is not a business approval.
- A policy revision is not legal advice or a jurisdictional approval.
- A rollback of application images is not automatically a database restore.
- A demo preset is not a product restriction or a commercial support guarantee.
Related articles
Documentation MapChoose the right AutoCore documentation path for installation, administration, operations, development, or security review.Installation ConceptLearn how an AutoCore installation defines identity, initialization, configuration scope, and operational isolation.Edition ConceptUnderstand AutoCore editions, shared platform behavior, explicit identity, and safe branding boundaries.Primary Market ConceptUnderstand the country, region, city, locale, currency, timezone, units, and capabilities that define an AutoCore primary market.Application SurfacesSee how AutoCore Web, Admin, API, Worker, data stores, search, and reverse proxy fit together.