Domain Relationships

The following relationship map uses only source-verified conceptual language:

Installation ── selects ──> Edition
Installation ── has one ──> Primary Market
Installation ── owns ──> Legal Policies / Acceptance Records / Provider Configurations
User ── has ──> Roles and Permissions
User ── belongs to ──> Dealer Memberships ──> Dealer Profile
User ── owns ──> Listing ── references ──> Catalog hierarchy
Listing ── has ──> Media Assets ── derives ──> Media Variants
Listing ── projects to ──> Search Document
Policy Revision ── receives ──> Policy Acceptance
Consent Receipt ── references ──> Policy Version
Payment Provider Configuration ── supports ──> Payment Attempts / Webhooks

Cardinality notes

• The database has one singleton installation record per database in the current model and an optional one-to-one primary-market link.
• A listing has one seller user, an optional dealer profile, required category, brand, model, and city, and optional deeper catalog links.
• A dealer has one owner user and many membership rows; a user can have dealer memberships in the model, subject to service authorization.
• A listing can have many media assets, price-history records, favorites, conversations, reports, and equipment links.
• Search documents and media variants are derived projections, not replacements for the transactional or metadata records.

Database identifiers, production counts, and real records are intentionally not part of this public reference.