SPEC-PWF-ACS · v0.1 13 June 2026 Owner: Platform team
Drill-down of the master workflow map (SPEC-PWF). This process is a view over the spec — its requirements live in the PRD set, its events & services in the domain set, its entities in the ERD. Lanes, steps and events render from workflow/workflow-catalog.js — nothing is defined twice. See §4 for the per-step links.
1Trigger, outcome & lanes
What starts this process, where it ends, who acts and on which surfaces.
RiverSync Co., Ltd. · BangkokSPEC-PWF-ACS · 1 of 4
2The flow
Top to bottom in sequence; lanes are the actors. Node shape follows the master conventions — pills start and end the process, grey nodes are backbone events, diamonds are decisions.
Users, roles & partner access — swimlane. Each step traces to a requirement in the table overleaf.SPEC-PWF-ACS · flow
RiverSync Co., Ltd. · BangkokSPEC-PWF-ACS · 2 of 4
3Steps
Each row is one node on the swimlane: who acts, what happens, the domain event it emits, and the requirement or rule it traces to.
RiverSync Co., Ltd. · BangkokSPEC-PWF-ACS · 3 of 4
4Related documentation
Every id, event, service and entity this process touches — each linked to the document that owns it. This is how you hop from a step back to the requirement, the service or the data model behind it.
5Rules in play
The WF-rules that bind this workflow — the master holds the full set; the DM-rules (ERD) and SVC-rules (Domain) they extend stay with those documents.
6Revision history
Version
Date
Changes
0.1
13 Jun 2026
First draft — composed with the workflow set (SPEC-PWF v0.1).
RiverSync Co., Ltd. · BangkokSPEC-PWF-ACS · 4 of 4
