Genesis Auto Service CMS — Automotive Service Intelligence Edition

Genesis Auto Service CMS v1.0.0 — Automotive Service Intelligence Edition — is a self-hosted PHP/MySQL CMS for automotive workshops and service centers. It unifies service requests, appointments, clients, vehicles, service catalog, articles, promotions, reviews, portfolio/gallery, brand & theme, partners, marketing widgets, SEO, analytics, Users & Security, Marketplace Pairing, Update Center, and IuVe AI content drafts. Documentation map | Category | Documents | |---|---| | General | README, PRODUCT_VISION, FAQ, CHANGELOG, ROADMAP, LICENSE, SUPPORT | | Installation | INSTALLATION_GUIDE | | Administration | ADMIN_GUIDE, USER_GUIDE, FRONTEND_GUIDE, LOCALIZATION, IUVE_AI | | Development | see docs/developer/ | | Security | SECURITY | | Marketplace | MARKETPLACE, UPDATE_CENTER | | API | API_REFERENCE, DATABASE_SCHEMA | | Cursor | see docs/cursor/ | Origins Marketplace STABLE 1.0.0 is promoted from the RC clean-install package Genesis-Auto-Service-CMS-v1.0.0-RC1-Functional-Preview.2 (Functional Preview.2: optional managed demo content with content_origin=demo). Product slug: genesis-auto-service. Languages EN (canonical), RO, RU, DE, FR, UA. Marketplace also exposes uk as an alias of Ukrainian (ua).

Purpose Give automotive service businesses a production-ready website and operations console: capture service requests from the public site, manage clients and vehicles, schedule appointments, publish services and marketing content, and stay connected to IuVe Marketplace for licensing, identity and signed updates. Principles 1. Self-hosted — runs on the buyer’s server; Marketplace remains the license source of truth. 2. Honest capability — v1.0.0 is the first commercial STABLE from Functional Preview.2; automatic unattended booking without staff confirmation is not promised. 3. Genesis Core frozen — auth, RBAC, CSRF, audit, Identity, Pairing, Update Center, widgets, translations and system health must remain. 4. Domain clarity — Auto Service tables (auto_*) own workshop data; core tables own platform state. Success outcomes - Workshop goes live with brand, hero, services and request form. - Advisors process requests → appointments → client/vehicle history. - Content and promotions publish with SEO fields. - License, AI and updates work via IuVe Control Center.

Requirements - PHP 8.1+ (8.2/8.3 supported) with PDO/PDO_MySQL, JSON, cURL, mbstring, OpenSSL, fileinfo (Sodium recommended) - MySQL 8.0+ or MariaDB 10.6+ (UTF8MB4) - Apache 2.4+ or Nginx 1.18+; HTTPS required - Writable: config/, storage/ (cache, logs, uploads, backups, rate_limits) Install steps 1. Create an empty MySQL/MariaDB database. 2. Extract the package so the root contains install.php, admin/, config/, includes/. 3. Open /install.php, choose language, pass environment checks. 4. Enter DB credentials and test the connection. 5. Enter the Marketplace purchase / license key when prompted. 6. Create the first Owner administrator. 7. Optionally enable managed demo content (content_origin=demo) or install clean. 8. Finish — creates config/database.php and storage/installed.lock. Post-install - Sign in to /admin. - Configure Brand, Hero and colors; upload logos and Open Graph images. - IuVe Control Center → mp_live_*, activate domain, validate entitlement. - Save kai_live_* in IuVeAI Center (capability auto.service.content). - Review Users & Security, widgets/consent, cron (cron-health.php, cron-telegram-service-requests.php). - Backup database and storage/uploads/. Never redistribute generated config/database.php, secrets or installed.lock.

Admin navigation Dashboard · Service requests · Service calendar · Clients · Vehicles · Service catalog · Site content · IuVe AI Content · Analytics · Contacts · Translations · Quality Center · Widgets & codes · Brand, Hero & colors · Partners · IuVe Control Center · Users & Security · System · About. Related screens: service editor, IuVeAI Center, Marketplace Pairing, IuVe Identity, Update Center. Daily operations 1. Triage requests (auto_service_requests) — status, assignment, internal notes, attachments. 2. Create/confirm appointments (auto_appointments) linked to request/client/vehicle/service. 3. Maintain clients and vehicles (auto_clients, auto_vehicles). 4. Publish services and categories with SEO, FAQ JSON, price_from, duration. 5. Manage articles, promotions, reviews, portfolio (gallery before/after). 6. Configure brand CSS variables, hero, partners, widgets and cookie consent. 7. Monitor analytics events and system health; keep Pairing and Update Center healthy. Roles: owner, admin, manager, service_advisor, editor, marketing, viewer.

Public visitor flow 1. Browse homepage hero, services, promotions, reviews and portfolio. 2. Open a service page (service.php) for description, symptoms, FAQ and price_from. 3. Submit a service request with name, phone, preferred date/time, problem description and privacy acceptance. 4. Wait for workshop confirmation — automatic unattended booking is not promised in v1.0.0. 5. Optional customer account area under account/ for IuVe Identity login flows. What staff see Requests appear in admin with status (new and further workflow states), source (default website), optional client/vehicle/service links, and attachments (auto_request_attachments).

Public pages - index.php — homepage (hero, featured services, promotions, reviews, portfolio blocks) - services.php / service.php — catalog and detail - article.php — article detail - sitemap.php, robots.txt, manifest.webmanifest Theme colors and logos come from settings / Brand admin and CSS variables — not hard-coded product branding for the customer site. Assets assets/css, assets/js, assets/img, favicons. Widget slots: head, body_start, before_footer, footer with consent categories (necessary/functional/analytics/marketing).

Core / platform settings, users, partners, partner_types, license_events, audit_log, pairing_state, analytics_events, content_translations, cookie_consents, page_blocks, content_revisions, iuve_identity_config, iuve_identity_links, production_events, update_history, schema_migrations. Auto Service domain (`install/schema.sql`) | Table | Purpose | |---|---| | auto_clients | Customers (name, phone, email, language, consent) | | auto_vehicles | Vehicles (make/model/year/plate/VIN/mileage/fuel) | | auto_service_categories | Service categories | | auto_services | Services (SEO, FAQ JSON, price_from, duration, image) | | auto_service_requests | Inbound requests + assignment + fingerprint | | auto_appointments | Scheduled slots linked to request/client/vehicle/service | | auto_articles | Blog/content articles | | auto_promotions | Promotions with date window | | auto_reviews | Reviews with rating | | auto_portfolio | Before/after gallery | | auto_ai_generations | AI draft history | | auto_notification_deliveries | Notification delivery log | | auto_business_hours | Opening hours | | auto_reminders | Reminders | | auto_request_attachments | Request file attachments | Demo records use content_origin=demo where applicable.

Endpoints | Path | Auth | Purpose | |---|---|---| | POST /api/ai-chat.php | Admin session + CSRF | IuVe AI chat/drafts (auto.service.content) | | POST /api/analytics-track.php | Public (rate-limited) | Analytics event intake | | POST /api/consent.php | Public | Cookie consent storage | | GET /api/health.php | Public | Production readiness JSON | | api/system/* | System | System helpers / about | Notes - AI requires configured kai_live_* / IuVe config; failures return controlled errors (no fabricated drafts). - Marketplace license APIs are remote on https://www.iuve.eu/api/marketplace/licenses/* (validate, activate, entitlement, iuve-config). - Cron: cron-health.php, cron-telegram-service-requests.php (secured tokens).

Capability Product config (config/iuve.php) uses capability auto.service.content, product slug genesis-auto-service, and IuVe API base https://www.iuve.eu/api. Keys - mp_live_* — Marketplace license / domain / entitlement only. - kai_live_* — separate AI API key saved in IuVeAI Center. Behaviour Admin AI chat (/api/ai-chat.php) requires authentication and CSRF. Draft generations are stored in auto_ai_generations. When the provider is unavailable and fallback is disabled, the API returns a controlled error — it does not invent service content.

Runtime languages Default language is ro. Packaged UI languages include ro, ru, en (admin login also offers de/fr/uk for chrome). Content entities (services, articles, promotions, portfolio, pages) store translations via content_translations and the Translations admin. Practices - Keep customer-facing copy in the workshop’s primary language first. - Use SEO title/description fields per service and article. - Do not hard-code brand strings into templates when settings exist.

Built-in controls CSRF protection, password hashing (min 12 chars on create/update), secure sessions, RBAC roles, upload MIME validation, protected storage/ paths, audit logging, rate limits, update signature trust (marketplace-release-key-2026-01, ed25519), Marketplace domain activation, emergency recovery login. Production checklist - Enforce HTTPS and secure cookies. - Restrict DB user to the application database. - Do not expose config/, storage/ or backups via the web server. - Rotate Owner and emergency credentials. - Keep update trust keys unchanged unless authorized rotation. - Backup DB + uploads and test restore.

Product identity - Slug: genesis-auto-service - Code: genesis_auto_service - Edition: Automotive Service Intelligence Edition - Channel: stable v1.0.0 (promoted from RC1 Functional Preview.2) Pairing In IuVe Control Center → Marketplace enter mp_live_*, normalized production domain, then Activate / Validate / Entitlement. Pairing state is stored in pairing_state. Documentation tab Marketplace documentation is mirrored under docs/marketplace/genesis-auto-service/ and releases/marketplace/genesis-auto-service/.

Signed updates Update Center verifies ed25519 manifests with trusted key marketplace-release-key-2026-01 (see config/update_trust.php / config/app.php). Channels: stable, preview, security. Operator flow 1. Check for updates in IuVe Control Center → Updates. 2. Review changelog and preflight. 3. Confirm signed install when required. 4. History is recorded in update_history. Do not replace trust keys casually — unauthorized rotation breaks verification.

Commercial Marketplace license Genesis Auto Service CMS is distributed as a paid, one-time IuVe Marketplace purchase for self-hosted use on licensed domains. Copyright © Reclama Verejan II. Author: Iurie Verejan. You may install on domains activated for your mp_live_* license. Redistribution of the package, keys, or generated install state to third parties is not permitted. Source access and derivative works follow the Marketplace commercial terms shown at purchase.

Channels - Marketplace purchase / license: My Purchases on https://www.iuve.eu/marketplace - Product page: /marketplace/app/genesis-auto-service - Technical issues: include VERSION.txt, PHP version, web server, and steps to reproduce - Security issues: report privately via the publisher support channel (do not open public exploits) Developer: Iurie Verejan · Rights holder: Reclama Verejan II

Is this a full product or an update overlay? Full clean-install package. STABLE 1.0.0 is promoted from RC1 Functional Preview.2. Does it auto-book appointments? No. Visitors submit requests; staff confirm appointments. Auto-booking without confirmation is not promised. What is demo content? Optional installer demo marked content_origin=demo. Contacts, clients, vehicles, requests and secrets are never seeded. Admin can remove, restore or convert demo records. Travel/SMM/Recruit conflict? Separate Marketplace products with separate licenses. This package must not contain travel-domain tables as the product identity.

1.0.0 (STABLE) — 2026-07-20 - First commercial Marketplace STABLE release of Genesis Auto Service CMS — Automotive Service Intelligence Edition. - Promoted from 1.0.0-RC1-FUNCTIONAL-PREVIEW.2 clean-install package; VERSION.txt set to 1.0.0. - Auto Service domain: clients, vehicles, requests, appointments, services/categories, articles, promotions, reviews, portfolio, AI generations, business hours, reminders, attachments. - Genesis admin + IuVe Control Center: Pairing, Identity, Update Center, Brand/Hero/colors, partners, widgets, translations, analytics, Users & Security, system health. - Optional managed demo content (content_origin=demo); company contacts/clients/vehicles/requests/secrets never seeded. - Multilingual product documentation (EN/RO/RU/DE/FR/UA) packaged under docs/.

Near term - Deeper appointment conflict detection and advisor workload views - Richer Telegram/notification templates for request status changes - Expanded public account self-service (without promising unattended booking) Later - Dealer multi-location support - Deeper OEM parts integrations (explicitly roadmap — not in v1.0.0) - Additional UI languages beyond ro/ru/en for the public site chrome