From 23ab9fbcdb3950889dfcdd5debb5dcc3d12ffbfd Mon Sep 17 00:00:00 2001 From: John Andersen Date: Tue, 24 Aug 2021 18:38:35 -0700 Subject: [PATCH] docs: arch: Inventory Signed-off-by: John Andersen --- docs/arch/0000-Inventory.rst | 63 ++++++++++++++++++++++++++++++++++++ 1 file changed, 63 insertions(+) create mode 100644 docs/arch/0000-Inventory.rst diff --git a/docs/arch/0000-Inventory.rst b/docs/arch/0000-Inventory.rst new file mode 100644 index 0000000000..858a9b3fb6 --- /dev/null +++ b/docs/arch/0000-Inventory.rst @@ -0,0 +1,63 @@ +3. Inventory +============ + +Date: 2021-08-24 + +Status +------ + +Draft + +Context +------- + +This document defines the inventory. The inventory is a list of items and +actions. Their relationships are defined as well as usage constraints. + +Think about how you put together ideas in your head. You connect concepts +knowing resources and processes. For example, how do you make coffee? You know a +coffee machine gives you brewed coffee. (Need machine, grinder, store sells +coffee, other store sells machine, delivery, etc. or coffee shop). + +References: + +- Wardly Maps + + - Making strategic decisions + + - We're going to use these concepts to help us understand what the best flow + is. Our inventory + + - Create maps which have value chain (invisible to visible at top) with + genesis of a product (prototype phase) on the left to the product being a + readily available commodity (widely available). + + - https://medium.com/wardleymaps + + - https://www.youtube.com/watch?v=Gfq3ocmadZo&list=PLP0vnsXbJsRVkWG7pjboonlrbISxtSN9I&index=1 + +Decision +-------- + +Operations and definitions of data types or resources can be added to an +inventory. + +Consequences +------------ + +**TODO** + +Reduction of duplicated work. One team making black coffee, one with cream. They +both will see the obvious need for a coffee machine, or coffee brewing service. +They can contribute that block to the inventory as an unfinished solution so +that each team can see that is a missing piece they need to collaborate on. + +Notes +----- + +Interfaces will likely be important in conjunction with definitions. To see +which definitions can be used by operations. Inspecting primitive data types and +other usage characteristics might help here. These other usage characteristics +might be things like, is it a secret. We should allow for annotation of data +with these usage characteristics, and the characteristics themselves should be +able to be stored in the inventory.