PROJECT CHARTER · EXPLANATORY

An open technical initiative for a programmable and interoperable laundry industry.

The charter defines the mission, scope, non-goals, stakeholders and initial relationship between SDL and SkyWash.

Status: DraftVersion: 0.1Document: SDL-GOV-001

Mission

The mission of the SDL Project is to define, implement and validate a common technology foundation for connected laundromat systems.

Initial goals

  • Define a shared laundromat domain and vocabulary.
  • Separate application behavior from physical hardware mapping.
  • Standardize commands, events and operating states.
  • Support safe local operation during connectivity disruption.
  • Provide clear extension points for machines, payments and peripherals.
  • Publish reference implementations and development tools over time.
  • Validate the architecture through real sites and independent partner feedback.

Initial scope

SDL 0.x focuses on self-service and unattended laundromat environments involving washers, dryers, detergent pumps, lighting, payments, sensors, POS terminals and local edge controllers.

Non-goals for the first phase

  • Industrial laundry production planning
  • Pickup and delivery logistics
  • CRM, accounting or ERP standards
  • Dynamic pricing and AI forecasting
  • Robotic folding or chemistry formulation
  • A universal certification claim before test procedures exist

Relationship with SkyWash

SkyWash initiates and maintains the early SDL Project. Its real-world deployments provide implementation experience with commercial machines, wired controllers, embedded devices, payments, local POS systems, pumps and remote management.

The intended boundary is clear:

SDL
  Common architecture, vocabulary and future specifications

SkyWash
  First reference environment and a commercial platform built on SDL

SDL should not require SkyWash Cloud, SkyWash hardware or a SkyWash commercial agreement.

Stakeholders

Laundromat operatorsReliable operation and freedom to evolve components.
Machine manufacturersA consistent way to expose digital capabilities.
Hardware manufacturersClear roles for controllers, gateways and sensors.
Payment providersTraceable association between payment and physical service.
Software providersStable application-level interfaces.
System integratorsMixed deployments with explicit boundaries and diagnostics.

GitHub publication model

The phase-one public repository should contain:

sdl-project/
├── README.md
├── ROADMAP.md
├── CONTRIBUTING.md
├── docs/
│   ├── what-is-sdl.md
│   ├── why-sdl.md
│   ├── architecture-overview.md
│   ├── design-principles.md
│   ├── project-charter.md
│   ├── terminology.md
│   └── roadmap.md
└── website/
    └── static publication files

Detailed schemas, source code and conformance claims should be added only when they are ready for technical review.

Early governance

During SDL 0.x, SkyWash maintains the repositories and documents architectural decisions publicly. External technical feedback is encouraged. Governance should become more formal only when independent participation justifies it.