...

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. Draft requirements
4. Convergence of diagrams
5. Next steps
   
   1. Meeting schedule leading up to Jan 29th
      
      1. Jan 24th @noon ET
   2. Provide "required reading" materials before Jan 24th meeting
      1. ..such as: Architecture

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

Notes 

Audio recording

• 2018-01-22-vivo-fly-in-planning.mp4

...