...

1. Logistics

   1. 2019 Architectural Fly-in Travel Plans
2. Defining the outputs of the fly-in
   1. Top-level architectural diagrams
   2. Component diagrams
   3. Inputs/Outputs for each component
   4. Draft HTTP API
3. What are the salient features that will drive the architecture?
4. What are the current bottlenecks, pain-points?
   1. Product Direction for 2019
5. Working documents
   
   1. Architectural diagrams
      1. Top-level and Detailed, component-level
      2. APIs and services, specified
   2. Features spreadsheet
      1. Questions to answer:
         1. What will the product will do/support?
         2. What additional business value-add can the re-architecture offer?
         3. What are core? and why?
         4. Which features are in/out/optional?
         5. What audiences are specific features for?
         6. What are the logical groupings for features into modules?
         7. Will we offer multiple product distributions, analogous to VIVO/Vitro?
            1. Perhaps an "enterprise VIVO" vs. a "small-shop VIVO" vs. Vitro
6. Meeting schedule leading up to Jan 29th
   1. Jan 10th @noon ET
   2. Jan 22nd @noon ET
   3. Jan 24th @noon ET

Notes 

Audio recording

• 2018-01-10-vivo-fly-in-planning.mp3mp4

Questions / Observations for Straw-chitectures

...