GLOSSARY · EXPLANATORY

A shared vocabulary for discussing SDL.

Clear terminology prevents business concepts, technical devices and physical implementation details from being mixed together.

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

SDL

Software Defined Laundromat: the architecture, project or a compatible implementation, depending on context.

Organization

An administrative or ownership boundary containing one or more sites.

Site

A physical or operational laundromat location.

Edge Node

A local computing component that hosts SDL functions near the physical equipment.

SDL Edge Runtime

The software that performs local execution, state, safety, persistence and adapter management.

Device

A physical or logical technical component such as a controller, terminal or sensor.

Asset

A stable operational object exposed to applications, such as Washer W1 or Dryer D2.

Capability

A standardized description of what an asset can do or report.

Adapter

Software translating SDL concepts into device-specific behavior and back.

Command

A request to perform an action. It is not proof that the action occurred.

Event

An immutable record of a fact that occurred.

Cycle

One logical execution of a laundry service or controlled operation.

Reported state

State information reported by an edge, device or adapter.

Effective state

The state used after considering connectivity, staleness, policy and reported data.

Idempotency key

A key preventing repeated delivery from causing repeated physical effects.

Binding

A definition of how SDL concepts are transported using MQTT, HTTP or another technology.

Profile

A practical subset of SDL requirements for a specific implementation or use case.

Reference implementation

Working software that demonstrates one valid way to implement the specification.

Asset ≠ Device

An asset is the operational object used by applications. A device is the technical component implementing it.

Command ≠ Event

A command asks for an action. An event records a fact.

Accepted ≠ Confirmed

Acceptance means the command will be attempted. Confirmation means the expected physical state was observed.

Offline ≠ Idle

Offline means current state cannot be trusted. It must never be displayed as available by default.