> For the complete documentation index, see [llms.txt](https://webuildssoftwaresolutions.gitbook.io/24carwash-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://webuildssoftwaresolutions.gitbook.io/24carwash-documentation/dudewash-documentation.md).

# DudeWash Documentation

**DudeWash** is a multi-tenant SaaS and service marketplace for fixed-location and mobile car-wash businesses.

This public documentation explains the product model, major user journeys and selected architecture decisions without exposing internal delivery plans, detailed security controls or proprietary implementation material.

## Product actors

* **Organization / Provider** — the business operating one or more car-wash locations or mobile service areas.
* **Washer / Technician** — the person performing the service.
* **Customer / Driver** — the person booking and paying for a wash.
* **Platform Operations** — the administrative team operating DudeWash.
* **Location / Branch** — a physical car-wash site.
* **Mobile Service Area** — a geographic area where service can be delivered at the customer's location.

## What DudeWash covers

DudeWash connects provider operations and customer booking in one platform:

* organizations, locations and mobile coverage;
* service catalog, pricing and availability;
* workforce and washer profiles;
* customer bookings and service lifecycle;
* subscriptions and provider SaaS operations;
* ratings, quality and customer communication;
* multi-platform web and native client applications.

## Architecture direction

The target platform uses the modern .NET ecosystem:

* .NET 10 / ASP.NET Core;
* Modular Monolith architecture;
* DDD + CQRS + MediatR where business complexity justifies it;
* Carter endpoints;
* FluentValidation;
* Mapster;
* SQL Server + EF Core;
* Polly / .NET resilience;
* Result Pattern + centralized ProblemDetails handling;
* Blazor Web App;
* .NET MAUI Blazor Hybrid with Razor/HTML/CSS for business UI;
* .NET Aspire and OpenTelemetry for local orchestration and observability.

## Public documentation boundary

This site intentionally excludes detailed SuperAdmin specifications, screen-completion audits, internal roadmaps, open commercial/product decisions, detailed payment and payout controls, implementation traceability, and security-hardening internals. Those materials are maintained separately in private engineering documentation.

## Design

The product uses a canonical Screen ID system across documentation and UI design so features can be traced from product intent to implementation.

Public documentation focuses on stable product concepts. Detailed implementation work is tracked privately until it is suitable for disclosure.