Every word Qlerify uses, defined once. The first half covers how a workspace is organised and how the diagram works. The second half covers the domain model, which is what a developer or a coding agent builds from.
Workspace and diagram
Organisation
The top level. An organisation owns projects, and you need one before you can create anything. It also decides who can turn on public access, that permission belongs to the organisation owner, not the project owner.
Project
A container for workflows, belonging to one organisation. Project membership is the unit of access: inviting someone to a project gives them every workflow in it.
Workflow
A sequence of events arranged on a timeline. This is the board you work on, and it is where Event Storming, Event Modeling, process mapping, User Story Mapping and Domain-Driven Design all happen.
Event
Something important that happened, named with a past-tense verb and a noun, “Order created”, “Broken equipment detected”. Events can be triggered by people, systems or time. Capture only state-changing events: “Guest viewed the calendar” is not an event unless it changes something. Depending on the method you are using, you might call these steps, tasks or epics.
Lane
A horizontal row naming the primary actor for the events in it, the user, role or system that initiates the command leading to the event. In “Customer created order”, the lane is Customer. A lane must be empty before you can delete it.
Group
A vertical division of the board into phases or milestones., Order Processing, Payment, Fulfilment. Groups are purely visual: unlike lanes, they carry no ownership or architectural meaning and never appear in the domain model.
Decision
A branching shape. Where an event moves the process along one path, a decision splits it into labelled conditions, each of which corresponds to a policy in Event Storming. Note that role cards attached to a decision are left out of the domain model and the spec export.
Connection
An arrow from one event or decision to another, added by dragging or with the Add connection tool. A target can have several incoming connections; the first parent stays the main one and controls horizontal position.
Card
Detail attached to an event: a user story, a business rule, a test case, a problem, an opportunity. An event can hold many cards, and card types are configurable per workflow. Card types marked “Show in backlog” appear in the backlog where you can reorder them by priority.
Release
An iteration or delivery milestone. Assign one to a card from the Release column in the backlog, or by dragging in the User Story Map, then filter the whole board by release to see the scope of one iteration.
