valueflows

commit 56add66ac7845dacab2969f5a108d7e99b6a9499
parent 57bd2379e1f95bc8f087d26cabd7810d69de234b
Author: Lynn Foster <foster.j.lynn@gmail.com>
Date:   Wed,  2 Jun 2021 11:51:10 +0000

Clarify deliver-service I/O
Diffstat:
M
docs/introduction/flows.md
 | 
4
++--

1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/introduction/flows.md b/docs/introduction/flows.md
@@ -75,7 +75,7 @@ pickup | No effect | No effect  | Input | No | dropoff |
 dropoff | No effect | No effect | Output | No | pickup |
 accept | No effect | Decrement  | Input | No | modify |
 modify | No effect | Increment  | Output | No | accept |
-deliver-service | No effect | No effect | Output | No | N/A |
+deliver-service | No effect | No effect | Output(3) | No | N/A |
 transfer-custody | No effect | Decr+Incr(2) | N/A | No | N/A |
 transfer-all-rights | Decr+Incr(2) | No effect | N/A | No | N/A |
 transfer | Decr+Incr(2) | Decr+Incr(2) | N/A | No | N/A |
@@ -89,7 +89,7 @@ We have defined a core set of actions, but expect that this will be extended wit
 
 (2) The actions `transfer` and `move` can optionally define a second identified resource on the receiver side.
 
-(3) Under discussion
+(3) The action `deliver-service` can sometimes also be an input to another process, at the same time as it is an output from a process.  This is because services imply delivery as they are created.
 
 ### Quantities and Times