SDL PROJECTSoftware Defined Laundromat Discuss SDL ↗
Home/Roadmap
PUBLIC ROADMAP · DIRECTIONAL

Build credibility in layers: explain, validate, implement and open the ecosystem.

The roadmap is intentionally organized by outcomes rather than aggressive dates.

Status: DraftVersion: 0.1Updated: July 25, 2026
01
CURRENT · PUBLIC FOUNDATION

Introduce the SDL idea

Publish a coherent public narrative and invite architectural discussion.

  • What is SDL?
  • Why SDL?
  • Architecture Overview
  • Design Principles
  • Project Charter
  • Terminology and public roadmap
  • Phase-one website and GitHub repository
Outcome: readers can understand, explain and evaluate SDL.
02
NEXT · TECHNICAL FOUNDATION

Define the shared model

Convert concepts into reviewable technical drafts.

  • Core domain model
  • Identifiers and capability model
  • Machine state model
  • Command lifecycle and event envelope
  • Device manifest
  • Initial machine-readable schemas
Outcome: partners can review semantics before code is treated as standard.
03
LATER · REFERENCE IMPLEMENTATION

Prove the architecture works

Build the minimum stack required to validate local execution and hardware independence.

  • SDL Edge Runtime
  • Simulator
  • Generic Modbus adapter
  • Legacy SkyWash compatibility adapter
  • Offline event storage
  • Example POS workflow
Outcome: applications can operate different hardware through one model.
04
FUTURE · PARTNER ECOSYSTEM

Enable independent participation

Provide tooling, profiles and tests after the core behavior is proven.

  • Adapter SDK
  • Conformance Test Kit
  • Compatibility profiles
  • Partner examples and sandbox
  • Hardware and adapter registry
  • SDL 1.0 candidate process
Outcome: third parties can implement and verify SDL components independently.
PHASE 1 RELEASE CHECKLIST

Ready-to-publish means more than uploading HTML.

  • Confirm public project name and domain
  • Create GitHub organization or repository
  • Select documentation and software licenses
  • Publish contact and security addresses
  • Review every “open” and “compatible” claim
  • Mark all documents Draft 0.1
  • Add canonical links between website and GitHub
  • Enable basic analytics without collecting sensitive data
  • Announce the project with a clear request for feedback
  • Track feedback as public issues or proposals