Talking with Steve and Dustin about options on black box...

- They were talking about using settings saying use custom, use core, use x, y, or z... we may have to wrap pure black box code with dynamic populating options (which option to use).

- We could really use a way to help show if the corps have black box options. Maybe even a flag (under the covers or in the hidden HTML) that says whether or not it using black box and/or core functionality.

- It may also be helpful if we could allow users to pick and choose if they want the black box option (full custom), the core adilas option (non custom defaults), or an industry specific option (build these options specific per industry).

Wayne popped in and was reporting on some AWS stuff.

- As we start moving over to AWS, a lot of the switching between test and live (URL stuff), is kinda going away and things are becoming more dynamic. Mostly dealing with URL, web addresses, domains, and path stuff.

- We talked about files and media/content storage and what to make publically available and what not to. We also talked about settings and adding in public and/or private boxes per corps (places to store things). We also talked about allowing users to put timelines (expiration dates) on sharing files and such. Say something like, I'll share this file with you for two days or I'll share this file for a couple of hours, etc. Once the expiration date of the URL or file happened, they would be denied unless they opened it back up. Kinda like opening and closing windows and doors for specific time periods.

- Wayne was talking about non language specific functions that we could run at any time. He was calling them Lambda functions. Very similar to an API socket connection or API call. Basically allowing the code and the response to be run using different code languages (mixing and blending coding languages).

- Wayne was also talking about off loading certain API socket calls and groups of calls to certain sub processes. Splitting up the flow and traffic based on needs and like functionality. Basically specializing code to be more effective and grouped.

- File versioning and auto file versioning - comes automatic with certain boxes out on AWS.

- Designing a life cycle process of sorts (putting things deeper and deeper into storage). Maybe use the access time (when was it last asked for or used) as the key indicator. This could be done if we need to mange active vs passive storage. We talked briefly about the analogy of water turning into snow and then going clear to ice. This may also come in to play with compliance, storage, active/inactive accounts, and long term cold storage.

- We spent quite a bit of time going over how the transition between our existing model and where things are headed and how to help with that transition. It got us into some discussions about master corporation lists, master user lists, and what permissions where set per section. Steve joined in and gave us some good ideas while we were talking about breaking out user/payee/employees off into their own entity.

- We ended with some conversations about world building, universe level, cluster and galaxy levels, world levels, etc. Fun conversation and lots of upcoming options.