Flow

A flow diagram represents an ordered list of labeled items. The view field determines how the flow is interpreted and rendered.

Fields

FieldRequiredTypeDescription
kindyes"flow"Must be exactly "flow"
viewnostringRendering intent. Default: process
titlenostringTitle rendered above the diagram
itemsyesarray of ItemAt least one item required

Item fields

FieldRequiredTypeDescription
labelyesstringText displayed in the item
emphasisnostring"primary" or "secondary". See schema.

View values

valueMeaningMin itemsMax items
processLinear left-to-right steps (default)1
cycleClosed loop — last item connects to first2
funnelTapering stages (conversion/filtering)210
swimlaneSteps grouped into horizontal actor lanes, top→down2

When view is omitted, the engine uses process.

For ranked/layered visuals (pyramid), use kind = "tier" instead.

Swimlane item fields

When view = "swimlane", each item gains one additional required field:

FieldRequiredTypeDescription
actoryesstringLane owner of this step

actor is ignored by all other views. At least 2 distinct actor values are required.

Swimlane example

주문 처리 프로세스 고객 시스템 결제 게이트웨이 주문 요청 재고 확인 결제 처리 주문 확정 확인 수신

Example

PDCA Plan Do Check Act