SPEC-PWF-COM · v0.1 28 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 (platform SAL-9 and Pipeline PIP-15), its events & services in the domain set, its entities (Conversation · Message) in the ERD and their lifecycle in the data-workflow set. 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. The unified communications inbox is the front of the relationship — it feeds lead to opportunity and stays distinct from customer↔support messaging.
RiverSync Co., Ltd. · BangkokSPEC-PWF-COM · 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.
Communications — swimlane. Each step traces to a requirement in the table overleaf.SPEC-PWF-COM · flow
RiverSync Co., Ltd. · BangkokSPEC-PWF-COM · 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-COM · 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
28 Jun 2026
First draft — the unified communications inbox process: an inbound message on any channel (web form · email · LINE · Instagram · Facebook · LinkedIn · phone) is matched to a contact, threaded into a Conversation, triaged, replied on its own channel and logged as an activity, or filed to junk / archived / deleted. Cascades from SPEC-PRD SAL-9 / SPEC-APP-PIP PIP-15 / SPEC-ERD DM-53 · DM-54 / SPEC-DWF-SAL (Conversation lifecycle). Prototype: apps/pipeline/Inbox.html.
RiverSync Co., Ltd. · BangkokSPEC-PWF-COM · 4 of 4
