Recording some notes from this morning. Then looking into the adilas core concepts overview and world building document. Trying to envision how to explain all of these interconnected pieces and how they help with business world building or industry specific recipe mapping. These pieces are somewhat interconnected.

I reread a few entries in the developer's notebook. They are elements of time #'s 12999, 13045, and 13059.

Also, I scribbled down some notes on a post-it note for some reverse engineering ideas... start small, expand forever...

Here are some of those ideas (expanded):

- Make up some starting rules and guidelines for the independent rep model. Create a starting spot. They can be tweaked more later.

- Maybe a base salary plus commissions to start out with. We could even start it higher on the base portion while they are learning. Then, once they know what they are doing, taper that back and have them rely more on actual finder fees and commissions.

- For developers, we could do the same thing... as the independent rep model, but for our developers. Instead of commissions, we could flip it to project or hourly variables to help offset learning vs productive development stuff. There is always a learning curve. Help them get started and then lead them to paying work. As a note, if we charge $100/hour, we could split it with them based on their level of experience and expertise. Just for fun, I was thinking a max of 75% for them and 25% for the company. If we have a super star, it could even go up to a 90% (them) and 10% (retain for us or for adilas or adilas shop).

- We have done this stuff before - independent rep model stuff - what have we learned? This is not a blind experiment.

- For me, make a mini "me" budget - what do I owe and where would I go with funding (personally)? This just helps me look at needs and wants, but from my personal angle vs a company angle. I think this would be good for me to do.

- As a I was reading the adilas core concepts document... There are 12 main concepts that I am trying to cover. If you boil that down (compress it), you could potentially make it into three interconnected concepts. Then the other main 12 concepts could be a sub of the main three. I was thinking about these... 1. Digital storytelling, 2. World building, and 3. Data assembly line. All of the other 12 main concepts could fit underneath those main concepts. Those ones sound more fun and might make a fun and general (yet deep and cool) introduction. I'm leaning in that direction.

- For everything... start at the highest level and then go deeper - start small, expand forever... - This could even be things like... Money coming in or money going out - accounting can be as simple as putting things in the right bucket or can (virtually create buckets for things). Then the accounting could be figured out after the fact. Everything has a lifecycle (states, statuses, phases, etc.). Help keep it simple. Explain operations and accounting without getting into anything technical, unless the user wants to keep going in deeper and deeper. As part of the this idea... I had drawn a triangle or pyramid type drawing. The top is super simple and it gets deeper and bigger as it goes down. Kinda like the iceberg analogy. Small top but mountains of functionality below.