Business Process & Journey Modeling
The architecture overlay's demand side: the actors who use the product and the flows they walk. A business_process is one goal-directed flow; a journey composes whole processes into a per-actor arc. Each step states the capability it requires; the realizing system is derived, and gaps reconcile as a backlog in both directions. Every example is a real construct from the Chowk marketplace.
Overview
- The flow lensEvery other lens in Vishwakarma describes what the system is — its data, its rules, the systems it composes into. The flow lens describes what people do with it: the personas who use the product and…
- ActorsAn actor is a persona — the "who" a flow is walked by. Before you can describe a business process or a journey, you name the actors that travel them. An actor is a first-class, project-global node:…
Processes & control flow
- Business processesA businessprocess models one goal-directed flow: the ordered steps an actor walks to reach a single outcome. It is the leaf of the flow lens — where the actual steps live. The smallest one is a title,…
- Steps & control flowA step is a node in a business process. Beyond the plain task step (does work, requires a capability, may present a ui), a step can take a control-flow type that shapes how the flow moves through it.…
Journeys & reconciliation
- JourneysA journey is the composition tier of the flow lens: a persona's end-to-end arc, assembled from whole business processes. Where a business process is one goal-directed flow, a journey is the sequence…
- Reconciliation & the backlogThe flow lens is a plan, the code is the build, and the two are almost never in perfect step. Reconciliation is how Vishwakarma keeps them honest — not by refusing a plan that runs ahead of the build,…