Working with Shannon. Going over things, things are constantly moving and shifting. Part of the game. Reviewing the end of last week. Going over phone call with Josh, new stuff from Abby, and the limited SWOT analysis document. We then spent the rest of the time working on the help file for the interactive map.

Going over the simple stuff from Abby. She took some of the AI chats and pulled out little pieces. We then spent the rest of the time talking about the sixth layer of the value add-on core model. We ended up starting a new ChatGPT chat session. Shannon and I only got part way. I then ran with it later in the day for a number of other hours. Here is the link to that chat session.

https://chatgpt.com/share/69d87170-9440-832d-b17f-987bf78d69ad

As I got new stuff back from ChatGPT, I was adding it to the value add-on core plan. The new stuff is at the bottom or on the layer six section.

Here is a little snippet:

The sixth layer of the value add-on core is the AI level (artificial intelligence). While the earlier layers focus on structure, data, workflows, and scalability, this layer focuses on interaction, intelligence, and automation.

You could say that AI is both a layer and a cross-layer capability. Instead of thinking of AI as a separate layer, consider it an integral part that enhances all other layers. AI builds value by using the system's existing data, structure, and workflows to deliver smarter, faster, and more intuitive outcomes.

It represents a shift:

• from clicks and navigation to conversations
• from steps and tasks to outcomes
• from manual work and processes to assisted execution and automation
• In a nutshell, good data --> solid structure --> action and intelligence --> outcomes and results

"Instead of focusing on how to use the system, users can focus on what they want to accomplish."

Working with Shannon and doing some editing and content creation. I showed her my session with ChatGPT on the interactive map for adilas. We then spent the rest of the time working and reading over that help file, for the interactive map. Making progress. I really appreciate her help.

Working with Shannon on help files and defining parts of the interactive map. We put in a whole new intro section and started moving some of the numbered sections around. Overall, a good session. Here are a few notes for me...

- Go back to October 2010. I was planning things out and trying to figure out where things fit together. There are a bunch of brainstorming documents that deal with what are the topics, what is the scope of each topic, how does it play into operations, how does it play into accounting, and who are it's buddies. That brainstorming session, over days and days, was the initial catalysis for the adilas interactive map. Specifically, we were planning and mapping out how the balance sheet fully works. Here is a link to that info: October 2010 in the developer's notebook.

- It feels like we are slowly coming up the chain... This is an analogy with food and baking/cooking, but it has similar things that have happened with how we pitch and promote adilas. We started out talking about the ingredients, then moving up to the functions of things that you can do, and finally getting to the results and/or what you can create. So, in food, ingredients are things like milk, sugar, flour, butter, salt, eggs, etc. Functions are things like baking, cooking, boiling, mixing, frying, roasting, chilling, freezing, thawing, etc. The outcomes and/or results are things like pies, cakes, cookies, brownies, cinnamon rolls, ice cream, smoothies, etc. This is what people really want.

- In the adilas world, the ingredients are things like invoices, quotes, inventory items, customers, vendors, PO's, expense/receipts, banks, deposits, etc. The functions are thing like POS (point of sale) systems, CRM (customer relationship management), CMS (content management systems), ERP (enterprise resource planning), accounting, inventory management, etc. The outcomes and/or results are peace of mind, clarity, trust in your numbers and the story that you are getting, being able to make decisions, gaining visibility, accountability, business intelligence (BI), digital storytelling, confidence, etc. We are wanting to get there... to the outcomes and/or results. We are only now seeing that we have been spending all of our time telling people that we have invoices and customers or we can do POS mixed with CRM stuff. We haven't quite gotten to the part that people really want. That's where we are heading.

- This little analogy about cooking and baking as compared to adilas business platform and system tools (see above) could be a super fun graphic. We are learning and we need to show what is really possible. In Steve's words, we need to sell the sizzle, not the steak.

Emails. Then jumped back into reformatting the user guide entries from Shannon back in 2019. Started working on old entries from 4.18 to 4.24. Also, reviewed some key help files for the interactive map and the adilas GPS core.

Here are a few links to what I was working on:

Old user guide entries - You may have to scroll a bit - Web link - user guide entries 4.18 to 4.24

Interactive map help file - Web link - help.cfm?id=393&pwd=map

GPS core layout help file - Web link - help.cfm?id=479&pwd=core

Working with Shannon. Looking at tons of things that need to be done (projects, documents, content, websites, etc.). We have a bunch of half-finished projects. We jumped back into a document called the adilas core concepts overview document. We had to totally rework the first part of the document. We are trying to help show the concepts of world building and how they play out and into the business world building mentality. Fun session. See attached for our current progress on the document.

I was scheduled for a podcast interview, but the interviewer contacted me and had a family emergency. I spent the day reviewing a bunch of older records and entries. Reviewing notes from other people on the team. Looking over my to do list items. Working on formatting old user guide info on the meet the players section. This is old, unharnessed, work that was done by Shannon back in the day (2019). Lots of good stuff. Went from 4.1 to 4.17, meet the players, inside of adilas university.

Web link - old user guide entries in the developer's notebook

Working with Shannon. We spent the whole time bouncing between older entries and reviewing recorded chat sessions. Here are some of my notes.

1. The Why (concept layer)
2. The What (structural layer)
3. The How (applied layer)
4. The Mechanics (deep dive layer)

- The timelines help to show what was happening when. That also shows the why, who, how, etc. Time helps tie things together.

- Pulling it all together over time

- Tools that we use - we read over this entry - Web link - time_web_gallery.cfm?corp=371&id=4029

- We tend to talk about features - very feature heavy. What about the other parts such as features, advantages, and benefits. We are only coving part of the deal.

- Maybe circle around and look at the database documentation and UML diagrams. Lots of info and story there.

- Move the vocabulary around so that you can see it more and be able to search it. Maybe even put it into the help files.

- Shannon and I were talking about how originally, I was planning on working on getting some investment monies. That process has slightly changed, and it is getting more of an education type feel to it. Both are still important, I am really enjoying the education part of the puzzle.

- Being "lost" - both virtually and figuratively - how do you find yourself or what do you do when you are lost - maybe pause - maybe try to get to high ground - look around.

- Review

- After meeting with Shannon, I had a few minutes before my next meeting. I went outside and ended up walking (hiking) in the mountains behind my parent's house. They are really steep.

- I am kinda like a digital explorer.

- Deer trail traction - on a steep side hill, you take what you can get and you are so grateful for that game trail or deer trail traction. You may not want to take another person on it, but it helps and works for you as you explore and look for better options.

- I want to smooth out the way for others. That is important to me.

- Educating

- Combining and Mixing

Working with Shannon. We jumped into some older documentation for the adilas user guide. We were in the financials and accounting section, section 11. We read over the first few entries and then got to the section new school accounting. It was mostly done, but not fully done. We started working and Shannon was asking what do you really want here? We did some quick brainstorming and then I showed Shannon a small graphic from years back. See attached for a copy of that graphic. She then recommended that we use voice to text, explain what we wanted to, and then see if ChatGPT could interpret our babblings. It did a great job! Fun chat session with ChatGPT on some accounting concepts. There are some hidden gems in the comments, after it interpreted what I was saying. Good stuff. As a note, there is a web link to the chat session as well as PDF version attached to this element of time.

https://chatgpt.com/share/69bc3d35-4230-8007-a52d-e6b549493127

Research on the data assembly line, new school accounting, and 3D levels. Found a bunch of old entries that Shannon and I were working on for the user guide. See section 11, for concepts on financials and accounting. Here are a number of links to show where some of the information is.

General adilas notes from back in 2008. This is when Brandon and Steve were working on the balance sheet. This is when the concept of allowing the data to flex until everything is correct or back to a stable spot. Web link - developer's notebook - balance sheet stuff in 2008

Writing out the progression of what we have learned thus far. These entries go forward from 2008 to the end of 2014. These are some notes from Brandon while helping to train some new interns and developers who were helping on the adilas project. These notes will be shown in two sections. One is the general notes from October of 2014. They will show the general flavor of what is going on at this time in history. The other notes will be specifically 10/14/14 where the actual entries hit the developer's notebook. Here are those links:

Web link - October 2014 - General developer's notebook for the month of October 2014.

Web link - time_web_gallery.cfm?corp=371&id=2894 - Specific date in time when the concepts first hit the notebook as a single entry. Progression of operations and accounting.

The next major time period was in March of 2015. This was a different set of developers that had questions and wanted to see how operations and accounting played together. This will have two sections as well. This will have the month of March 2015 and then a specific time when the process was described in more detail, with a slightly different flow, which helped in presenting the ideas. Here are those links:

Web link - March 2015 - General developer's notebook for March 2015

Web link - time_web_gallery.cfm?corp=371&id=3618 - Specific date when the process was explained using a giant Whiteboard at Bridgerland Technical College.

Adilas Key Contributors:

Steve Berkenkotter - Main owner and business partner - original ideas, concepts, and training - sales, relationships, dreamer, visionary, custom code, coordinator, builder of the first industry specific skin, and the list goes on. Huge player in the adilas story and timeline. One of the original owners in Moring Star Automotive - where the system came from. There are three known Steve's in the system notes. Most of them are this Steve (99 out of 100 times). He won't admit it, but adilas was his brainchild.

David Berkenkotter - Steve's brother and business partner in Morning Star Automotive. David was a system user and helped us create the adilas quick search. He liked using that feature, the quick search, but it only existed on one page originally. He wanted us to put it on every page. That ended up being in the header. He was also one of the original partners in adilas. Power user in the system. Sadly, he passed away due to cancer.

Shari Olin - Commonly known as "Shari O.". She worked in the accounting department back in the Morning Star days. She has been somewhat of a mother hen to help all of us crazy chickens keep going. She helps with customer support, training, payroll, bill collection, and tons of backend office functions. Major power user. Just being silly, but she can have the mouth of a sailor but the heart of an angel. Part of the adilas admin team and a great friend.

Craig Leitner - Also part of the original Morning Star team. Craig was the automotive floorplan and bank guy. He is a power user in the system and does a lot of bank reconciliation and other tasks. He currently works with Steve and asks as the adilas controller (money flow guy).

Cory Warden - Originally an adilas rep and consultant. Cory become part of the team after being a rep for quite some time. She helps with customer care, client support, project management, and keeping the team on track. She also does all of the news and updates and other training material. Cory does tons of oversight type services for our clients. Power user and part of the admin team.

Sean Carlton - Sean was a manager at a Cannabis dispensary in Colorado that used adilas for years and years until they sold. Steve recruited Sean to help with sales, deployment, and training. Sean brings lots of usage experience. Often, he is one of the helpers if we need to send someone onsite to help with a deployment or training session. Power user.

Brandon Moore - I'm one of the guys that writes most of the developer's notebook entries. Originally, I was hired by Morning Star, the automotive dealership, to help with data entry, accounting, and website stuff. I ended up being one of the main adilas developers and architects. I build content, write code, help other developers and team members, and help with training. Helped start the project back in 2001 under the Morning Star name.

Chris Dunsey - One of the first adilas interns (developers). Helped with a number of projects. Ended up being somewhat of a consultant later on.

Shawn Curtis - Kinda a funny story. He was taking a developer's class at Bridgerland. He knew my brother Russell. He asked to join our developer class and became one of the first interns along with Chris Dunsey. Shawn ended up helping with payroll and other projects. Some of the photo galleries in the system came from Shawn's help. He also worked on the media/content (file upload) pieces. Later on, he did more payroll work and acted as a buddy to Brandon and did some consulting work. We worked together for years and years.

Russell Moore - Russell is my younger brother. Originally, he was added to the group because of his graphic skills. He ended up being a great backend developer and project manager. He has also acted as a trainer and mentor for Brandon along the way. Much of the current system came from projects and efforts that Russell was involved with. He has also been Brandon's AI tutor in recent years. Great help to the system. Huge contribution.

Chris Johnnie - He is an entrepreneur who teamed up with Russell to help create a company called "Adilas For Business" or "AFB". Eventually, both Russell and Chris sold their pieces back to adilas. They were honestly the first ones to really try to run as a white label of adilas. This was back in 2015 and 2016. Chris really helped to push the product to the next level along with Russell's help.

Danny Shuford - Longtime friend of Steve's. Danny helped with some website design, sales, and videos for adilas. He even got into creating custom PDF labels for clients. Light development work.

Marisa Shaw - She is Danny's daughter. Danny brought her to an adilas training event in Denver, CO. Marisa was the star student. She ended up helping with some graphics, flyers, marketing material, teaching, instruction, and planning. Power user. Very helpful.

Shannon Scoffield - Shannon is Brandon and Russell's sister. Her maiden name is Shannon Moore. Huge help and virtual assistant to Brandon. She has helped with training, project management, and content creation. Most of the major content sessions were or have been with Brandon and Shannon working together. When they, Brandon and Shannon, were traveling, Shannon was one of the primary adilas instructors. If she was teaching Brandon was taking notes. If Brandon was teaching, Shannon was taking notes. Power user.

Cheryl Moore - Cheryl is my mom. What an asset. She owns a small business and has owed a few different ones. When we were doing training sessions, she came to every one of them. She asked wonderful questions and was a great supporter. Sometime, I would use her as a test subject - can my mom do this? If yes, we are good. If not, we may need to keep tweaking it. Thanks mom!

Wayne Moore - Wayne is my dad. He was my hiking buddy and more than willing to talk about ideas and concepts on our walks and hikes. He helped out with video stuff and was a great coordinator for making other connections. He worked at Bridgerland (technical college) and helped us get setup with classrooms, computer labs, and other great connections. Huge cheerleader! There is another Wayne, Wayne Andersen, he is a backend developer, systems guy, and database guy.

Wayne Andersen - This Wayne lives in Portugal and helps with all of the backend security, server, and code testing. Major skills, writes code, helps push all of us to new technologies, partially retired but loves to play with tech stuff. If you search for Wayne and it deals with concepts and coordination stuff, that's my dad, Wayne Moore. If you search for Wayne and it sounds like a master backend guy, that's Wayne Andersen.

Alan Williams - One of the lead developer's at adilas.biz. Alan joined us in 2015 and quickly came up through the ranks. Trainer, CTO, team lead, master developer, prototyper, and system architect. Alan has helped with many projects and features over the years. He also helped Brandon with some of the prep work for the adilas lite (fracture) plans and project. Sometimes called "Dr. Alan" by the other developers. Example: This might be a project for Dr. Alan.

Bryan Dayton - Bryan has been one of the most versatile guys on our team. Originally, he joined a development class out of curiosity. He and Brandon live in the same town and know each other from church. Bryan has done more custom code or small system projects than almost any other developer. He also joined the team in 2015. He helps with sales, custom projects, pushing on projects that he thinks will yield a return. Lots of work on the adilas lite and fracture project. Very hard working and versatile.

Dustin Siegel - Developer who helped with numerous cannabis and cultivation type projects. He worked directly under Steve to help with that business vertical. Many of the original pages that Steve built were taken over and remade by Dustin.

Eric Tauer - Developer and custom code guy. Originally, Eric knew Steve and lived in Salida, CO. As a note, adilas is Salida spelled backwards. Eric has a background in database work and data warehousing. Eric has done tons of custom systems for clients. Often, Eric would pioneer certain features or logic, as custom code, and then we would bring those features into the main adilas application.

Garrett Kirschbaum - Adilas intern and then full developer back in 2015. Stressful time of building and expansion. He and others helped run the adilas shop with Brandon's help. Garrett was a great developer and helped us standardize a number of tools and features. He was the first developer to work on sub inventory, back in the day. He also did other projects and helped with some developer management stuff.

Charles or "Chuck" Swann - Charles was an instructor at Bridgerland for web development. He builds custom websites, does amazing mock-ups, prototypes, and is a CSS master (styling a website using code). Chuck worked with Russell to help with redesign work, projects, and vision. Chuck worked fulltime for a number of years and now works and coordinates work done by a small hand-picked design and development team. Anything that needs some design loving gets passed over the Chuck and his small team.

Steve McNew - Friend of Steve Berkenkotter's. This Steve helped prep some whitepaper documents to help with getting adilas standardized and some internal audit type stuff. Mostly white papers and putting things down on paper. He ended up getting hired by the local school district and wasn't able to finish the process, but he got it started. He asked some great questions, and we had some good conversations.

Abby Elkins - Abby is Brandon's daughter. Her maiden name was Abby Moore. Abby, when she was little (10-12 years old) helped with some of the original concept artwork for adilas. Later on, she helped with content for the presentation gallery and then the adilas lite plans (fracture). Currently, she is working graphic artwork for different adilas pages. She's now in her mid 20's and has some awesome art and content skills.

Aspen Moore - Aspen is Abby's younger sister and Brandon's daughter. Aspen helped Brandon with some planning and counseling (mental help). Aspen also did some general business consulting with her dad Brandon.

John Maestas - Developer, backend server guys, and designer. John came to us through Dustin. John was uses as a jack of all trades on the backend and frontend. He did numerous projects, documentation, payroll, and page redesign projects. John was also very help to Brandon in working on the notes and comments on the SWOT analysis document. Many other projects as well. Good vision of the future.

Kiva Berkenkotter - Steve's wife. She helped Steve with various projects and planning sessions. At one point, she was in charge of paying commissions and collecting monthly reoccurring payments. Huge supporter to Steve!

Heather Moore - Heather is Brandon's wife. What a trooper. Cheerleader, support, ideas, and consulting. Huge asset to Brandon (me). Thanks Heather!

Jonathan Wells - Designer and mock-up guy. He helped to map out the system and created a number of deep mock-ups for adilas lite (fracture) projects. Great job catching the vision and putting those pieces into a visual representation. We still refer to his work when talking about fracture (future project for adilas).

Jonathan Johnson - Business consultant from Epic Enterprises. Met with Brandon and Steve in end of 2019 into 2020. Really helped us see some needs and opportunities. Later, helped Brandon with some other consulting when trying to define the fracture plan.

Calvin Chipman - Windows software developer. Calvin also did a bunch of web-based work, database stuff, label printing, and API socket stuff. Calvin was the first developer to use the adilas API's to create a native mobile app for a client. He also built a number of special developer tools used by some of our team to speed things up. He's the tool guy!

Cody Apedaile - Bryan Dayton's cousin, Cody helped with a bunch of JavaScript code and changes. He also spent some time working on the UML diagram for the adilas database. We didn't get things finished, but he was working on a new build your own interface (custom to you) for adilas. We ran out of funding. We want to get back to that project at some point.

Dave Forbis - Dave was the official "high tech gofer". He did a bunch of things. Graphics, project management, brainstorming, planning, sales, and helped with managing developers for the adilas shop. He was another great student. He came to a number of training courses and brought so much to the courses. He was also a big support to Brandon during some rough times.

Josh - There are three Josh's. Josh Wheeler, Brandon's friend and developer. Josh Sagert, developer and adilas user (worked tons on the discount engine), and Josh White, Steve's friend from California. Josh White has brought us a number of bigger leads and bigger players, like franchises, and other higher-end clients. Anything recent is Josh White, from California. He helps with networking, sales, and dreaming of new things.

Suzi Distelberg - Sales, training, and deployment. She also worked with some custom projects and doing step-by-step user guides. She has helped with all kinds of projects and even gone onsite for setups and training. Great asset!

Kelly Whyman - Kelly is Dustin's wife. Kelly was single handedly the best independent sales rep that adilas had. She did training, consulting, and sponsored a number of custom projects. Kelly helped Steve and Brandon with reports, functionality, and other things. She got so good at things, state contracts snagged her up to work at state and multi-state level stuff.

Molly Hennessy - Molly was another independent sales rep and consultant. She had numerous clients and got into doing SOP's (standard operating procedures) and other high-end documentation and training. Molly was an entrepreneur and even started creating some of her own product and services. If you search adilas on google, some of the other results are from Molly. Super creative and a great consultant.

Hamid Karbasi - Developer - He has worked with Brandon doing small websites, training, and small tasks. He currently is a manager at a retail store and brings some managerial type skills to the table. Willing to talk about concepts and how they apply to retail and other environments. He is also lightly helping with some planning for fracture.

Gene Spaulding - Friend, entrepreneur, and businessman. Gene is an old college friend. We had a number of friends in common. He has been a small mentor to me over the years. Way back, before adilas, he helped me get my first business loan for a project that I was working on.

Sharik Peck - Friend, entrepreneur, public speaker, physical therapist, and businessman. Good influence and mentor in ways. Sharik and I used to exercise together back in the day. Many of fun walk, run, and weightlifting session. Learning some conference and training skills from him and his wife. They have done really well pushing their product lines and doing some marketing. Trying to get some ideas.

Bridgerland Technical College - Use to be Bridgerland Applied Technology College. Not a person, but a huge help. This is a local technical college in the Logan, UT, area. Brandon's dad, Wayne, worked there. Tons of assets. They provided classrooms, training options, computers, and even an small incubation spot (starter office space) for the adilas shop during the startup phase. Huge asset!

McCorvey's Pro Shop - Also known as Bowling World. Client that had multiple locations. The started out with around 30 and grew up to the 90+ location level, all using adilas. Long time client.

Emerald Fields - They were the first client that wanted their own fully dedicated box and server. They had multiple locations and requested some custom code, reports, and features.

Beaver Mountain Ski School - Client that we helped them track their ski school (snow sport) lessons. Students, instructors, classes, and schedules. Custom interface dealing with elements of time and flex grid.

Bear 100 - This was the first event or annual event client that we did. They used the system for about a week each year. They had 350+ runners and their families that would be on the site for multiple days straight. It was a 100 mile running race with 13 aid stations and a small social portal for the family and friends to watch their runners. This one was special as it had custom input options to upload CSV files to populate the database vs normal HTML form field entries. Records were sent in batches from remote places to adilas for storage and race progress.

High Valley Bike Shuttle - Online ecommerce and scheduling client. They also have a cafe and small retail store. Fun online scheduling and bulk flex grid projects.

Herbo - Mike Roundtree, owner of Herbo, was the first company to do a small white label of adilas. Mike has been a great asset to Steve and the two of them have worked on projects, plans, and dreams. Herbo also has a custom payment solution that they are trying to market and get rolling. Mike has been a great supporter for years. He is also a certified CPA and that credential helps us and him. We would like to get other CPA's on board as well. Thanks Mike!

Nxtlinq AI - AI assistant. These guys really pushed us to get an AI agent inside of adilas. Tons of development took place and lots of prep stuff. We wanted to do a 3-part plan for integrating AI. 1. Teach it how to navigate using the AI quick search (check - done), 2. Teach it all things adilas. and 3. Teach it how to be clear up at the consultant type level. We only got the first phase done. Lots of other plans and such, but we ran out of funding.

Grok AI - Steve loves using Grok. He has built a number of image generation options inside of adilas. He is also working with Grok to feed it data to help with analytics and AI insight. This is not finished yet, but we may end up using Grok as an AI assistant inside of adilas. We have simple and emerging connections available right now but need to really polish things up before going live with the AI assistant options.

ChatGPT AI - We have started using ChatGPT to help with code, explanations, explore resources, planning, and help with training and flow for people and other AI bots. Currently, Brandon, Steve, Bryan, Alan, Josh, Russell, Chuck, and Wayne are using AI in either ChatGPT chat sessions or some other form of AI. We have some using Copilot, Gemini, Claude, etc. AI is actually helping in many ways. ChatGPT is a big one for use. Anyways, they are earning their place in the adilas key contributors list.

There are so many more that I can't list. Developers, users, power users, reps, consultants, trainers, clients, accountants, friends, family, and even critics. They have all helped out the idea farming process and progression. Good stuff! We couldn't have done this alone. It takes a community to do what we are doing.

Working with Shannon. We were talking about how much there is to do. She was saying, maybe doing things lightly vs jumping in full tilt and trying to do everything. We spent most of our time working on some master menu items with ChatGPT. Reviewing the chat document and then pushing it to the next level. Some great new progress and ways of showing things.

We worked quite a bit on results and desired outcomes today. The new chat session covered some new topics like the adilas knowledge tree or knowledge map, the adilas universe map, multiple engines (people engine, business engine, data engine, AI engine, knowledge engine, AI engine, and results engine), the adilas value flow model (1. People, 2. Actions, 3. Data, 4. Insight, 5. Results, and 6. Learning), the adilas universe model, adilas galaxy map, and my favorite part - business function to result indexing or result mapping. Great session.

Here is the ChatGPT chat session link: https://chatgpt.com/share/69b8cb40-042c-8007-bd59-9631c92d2137 - As a note, the first request contains a list of HTML menu list items, if that looks scary, skip that part, the rest is in plain English and has some great information. See attached for a PDF version of the chat log.

Emails and then meeting with Shannon. Rereading some of the content that we are working on. Shannon was saying that due to AI, some people are lamenting the "loss of effort" by using AI too much. Shannon and I were talking about asking AI to help me summarize certain topics. I have a ton to do. Help break it into chunks. Small not on marketing - it is presenting things in a way that solves their problems (our clients). We also talked about helping AI to catch the vision so that we can share that vision with others. Fun session.

Working with Shannon. Talking to Shannon about coding with AI, just a different process. Start general, build functionality, commit and iterate between things, test first - then read code. We also talked about high-level precision bug fixes and changes. Multiple different processes. We briefly looked at the presentation gallery and where we are hoping for things to head. We talked about budgets and how we could blow through $100K in a month, without even blinking. Switched over to working on the content for the other business plans. We worked with ChatGPT on doing a SWOT analysis stuff. We are not yet finished, but making great progress. Super fun session. Here is the link to the chat session.

https://chatgpt.com/share/69a9d788-a288-8007-949a-58d1ed5ccde2

Jumped on the meeting with Shannon. Only had time for just a quick hello and how are you doing. I got a phone call from Steve. I told Shannon that we would need to reschedule. Then working with the banks to reverse a draw on the line of credit. Multiple phone calls, emails, etc.

Multiple sessions working with ChatGPT on adilas pricing structures and such. Getting help with prices, plans, add-on's, and other options. Shannon and I started the session earlier this morning. I then did multiple other sessions throughout the evening to finish up. We had left out activations, setups, 3rd party solutions, and other industry specific stuff. We also added in some notes to help us account for upcoming changes to the adilas value add-on core model, adilas marketplace, and the adilas cafe. All part of the new future and where we are headed.

Steve challenged me to work with ChatGPT to actually build out small samples and pages. We went through three different versions. Once we finished, I sent an email out to Chuck (designer) with the temp files and instructions. ChatGPT was very helpful. Recording some notes from the day.

Here is the full chat link of our session - 5-6 hours in total - https://chatgpt.com/share/69a0a070-3778-8007-a998-ebf29c864809

Working with Shannon. We looked around at what is happening and then jumped into some of the stuff. Lots of moving pieces, all over. I explained what I did with Abby yesterday and we looked at some graphics. We then jumped in and talked about what we did with Russell and how we used AI to help build out a basic teaching and documentation project. Supper cool. I didn't have anything really to show, so I drew what it did. I will get files from Russell later on.

We talked about what else we have in front of us, project wise, and where we need to focus. We then spent the rest of the session going over pricing stuff with ChatGPT. Super fun session and we really tried to give it some good information and ideas. Here is what we came up with.

https://chatgpt.com/share/69a0a070-3778-8007-a998-ebf29c864809 - ChatGPT chat link on adilas pricing structure (prices).

Working with Shannon. We started out by reading over an email from Wayne (backend server technician for adilas). He is proposing some tech changes and code restructure stuff. Pretty in-depth changes and plans. It all plays into our adilas lite and fracture plans. I really want to help and support him in his decisions. We spent the whole time going over his plans and documents. If Shannon didn't understand something, I would draw or explain what I could. The plan had priorities, phases, cautions, and even pages that needed attention, based off of usage and page stats from one of the servers over a 3-day period. That doesn't show the whole story, but it give us a good idea. Pretty cool!

Meeting with Shannon. We are trying to help people catch the vision and see the potential of what we are doing. We started out and reread a number of entries from last week. Things are going so fast, we have to review and go over them again and again. Currently, we are just making sure that we at least record what is going on. We will work on it, meaning actually doing it, as we can. We reread these entries for 2/10/26 to 2/12/26. I enjoyed going back over things and looking at the progression.

- We have been using the stone soup analogy for what we are doing. This was an observation that Shannon made - stone soup is something novel or new... - no one knows what stone soup is. It is something different. It wouldn't have worked if you just say... we are making vegetable beef soup. Everybody already knows what that is. It was stone soup, with that small unknown mixed in. How do you attract people to come and see and come and participate?

- Shannon was talking about personal revelation, leading you towards the next step, whatever that is.

- Taking the time to review what is happening and deverbalizing it and going through the plan. The process of talking through it actually helps you see the next steps.

- Towards the end, we talked about helping and training the AI agent. Eventually, we will need a database level training tool to hold and control all of the education and pieces. That becomes the content. Especially, if you can search it and break it into smaller pieces.

Working with Shannon. We were talking about building up a community - how do you do that? What makes people want to come or show enough potential that they are willing to come and be a pioneer and/or adventurer? We are looking for those people. Pitch it like - open land and I can do what I want. Helping them see that they are starting something new or pioneering something new. We briefly talked about the railroad analogy. How do you find those people?

These are some other notes from our meeting:

- Marketing the dream and the freedom of choice - would that work? We are looking for someone who is already discontent (unsatisfied) and seeking something new or different.

- Helping people see the vision and potential of what is possible.

- We were talking about putting videos on the presentation gallery and letting them get deeper and deeper into the system.

- Helping people with pain and solving real life needs.

- If someone really, really, cares about something, they will spend the time and money to get more into it.

- Telling the story and letting people pick and choose their investment levels (even their investment of time and energy to hear the story).

- Making templates and one-to-many relationships (videos and pitching the vision).

- Shannon's term - vision videos - using vision videos vs laser focused training videos. They are different.

- Stone soup (fable or analogy) is not about the food, it is more about the draw or the community. Maybe adilas is not about the software, it is more about the options and what it offers.

- After talking about this stuff, we spent some time working on some of the other business plans. Still pretty rough, but here is the link to that page (adilas plans).

Working with Shannon on some planning. Reading over our entry from earlier this week (eot # 12662). Started reading over the adilas investment opportunities and making small changes. Pushed up the new changes. Part of this was adding some new general rules and guidelines for the adilas white label section. That section is towards the bottom of the page. Click to view the new investment options.

Meeting with Alan and Steve. He, Steve, is having the AI agents write code and he is managing it. He is working on phone notifications. He is using multiple AI bots to compare notes and check direction stuff. As part of the process, he was getting Wayne, our server guy, to install some different things on the servers. Steve was showing us some things that he is working on, some new reports, and new homepages.

We switched gears and I was showing some stuff from what Shannon and I were working on this morning (eot # 12662). Alan is doing some other research to help with things. We talked about using AI for input data options. Quick, snap a picture, and have the AI do the look-up and prep the input. Having it help with predictions and trending and some sort of analytics.

Steve was showing the different AI models. Looking at pricing per millions of tokens and the context window sizes. Things are changing quickly. We want to keep using natural language processes and asking it for help. Talking about future buildouts and white label options. Steve was talking about robots and what is coming (stuff from the news). Talking about data in and data out. I mentioned that Bryan was working with a potential client that wants a simple POS systems and automating things behind the scenes (eot # 12656). Steve was saying that he sees that kind of thing happening over and over again.

Alan and Steve were saying that our dreams can be realized so much more quickly now. In some ways, you can take the code writing hurtle out of the picture. You still have to know what you know and be willing to mix things together, but things can happen much quicker now. Interesting times.

Recording notes from this morning's meeting with Shannon. See element of time # 12662 in the shop. Planning for the future with AI being part of the plan.

Working with Shannon. Talks about AI cannibalism and what is happening to the SaaS (software as a service) model. This came from an article on X - twitter (link). Steve sent it over to Alan and I to read. Anyways, I was reading it and Shannon was taking some notes. I was then drawing about how people are using AI and where things are going. I was showing 2 main things... companies need to use AI or be left behind. If they do use AI, especially SaaS companies, they are basically cannibalizing their own products and services.

Notes from Shannon - summary of the article on X:

- Biggest irony in tech history... earnings are up and stock is down

- Huge companies invested tons in AI and ironically it is hurting them

- No AI, you are left behind. Yes AI, and it will start to cannibalize your company

- AI doesn't make software companies stronger, it makes them obsolete

- AI is replacing the software that these companies are selling

- If AI can write code, automate flow, do X, Y, and Z - all for pennies - why would you pay for software?

- One AI agent replaces 10 seats, One prompt replaces months of custom development, One LLM call replaces entire software categories

- Companies that invested most in AI are hurting the most

- Companies enabling AI (hardware) made money

- Hardware up and software down

- The AI world needs GPU's (graphical processing unit)

- Don't need software subscriptions when AI can build it for you

- Investors question - will your business survive the next five years?

- Software earnings were up, but stocks were down. How do you compete with free?

- AI is getting more reliable - you don't have to rely on these older SaaS software packages

- One of the biggest market shifts in history - $500 Billion gone in market value in one day

Shannon and I were talking about what the models are going to look like - drawings... molecule (mash-ups) vs a systemized approach. with AI, it will take the mash-up and really make it even more complicated. Little microservices - more than just a mash-up, it will become soup... just being silly - see attached for a small drawing. In the drawing, I was showing Shannon that we have to use it, meaning AI. Most people and/or companies fall into one of three models. The do it yourselfers (pen, paper, spreadsheets), the mash-ups (molecule type model - trying to mix and blend together), and the systems and platform models. Adilas is a platform model. We would love people to add in AI over the top of what we are already doing. It will just make it richer and better and better. Once again, see the drawing for more info.

Building on a platform that supports AI add-on's - we have the engine to build on top of - the platform - really pushing the platform and how it can service the user needs and requests.

Some of our plans... for helping AI do things... see element of time # 12392 - this entry covers user defined prompts, chaining prompts (multiple prompts in a row or sequence), and how to use AI to help do even more

- Switched to reading over the investment options and opportunities for adilas. Read over some new rules from element of time # 12645

As Shannon and I were talking - I was saying that hyperlinks are my way of gathering things... I can interconnect almost anything using a hyperlink. That is awesome.

We read over the entry on 12645 (see link above) and worked on redefining certain pieces. We aren't trying to get perfect verbiage at this point, more along the general flavor lines. Great session.

Working with Shannon. We reread time id # 12645. Tons of talking, side tangents, drawing, using calculators, and trying to refine things. Working on the overall picture. Where are we headed and what are the rules that we want to setup to get there.

Work session with Shannon. Going over tons of notes from last week. That was fun and insightful. We reread a bunch of the elements of time (entries) from 1/19/26 to 1/24/26. As we were reading the entries, we made a few small fixes and added some more information. Just trying to refine things. Lots of moving pieces, daily. It's crazy how fast things can change.

We talked about some new concepts and topics. Shannon was talking about "lean" and "just in time" options. Everything seems like it is getting into super scaled down versions. We know that many of the adilas users would love something like that. We are trying to get there. It feels like we have to break it down into a few smaller pieces, so that it can dynamically conform to what we want it to be. In English, we have to make it more technical in the background (splitting or fracturing into smaller pieces) to make the interface seem simpler. Everything needs to be configurable (permissions, settings, and templates).

Some other topics were simple step-by-steps, easy SOP's (standard operating procedures), and quick focused training. Another topic was helping people to participate in something great. If they want to buy in, they have to feel like it is something of worth and something great. Shannon and I were talking about showing them, any interested party, what we have and how and why things work. We talked about setting up a time to be available, once a week, for questions, demos, and touching base. Leaning towards one night a week, over the GoToMeeting session (reoccurring meeting).

As a note, we left off, reading through element of time # 12645 - we only got halfway through it.

Yesterday we met with Steve, see element of time # 12620 for details. Today we were working on where can we go and what can we do. I was showing Shannon some options for outside control of the funding. Lots of drawing and showing flow and possible flow and control. Here are some of our other notes.

- From yesterday's chat, Shannon was talking about Steve not wanting to declare bankruptcy (closing things down) and me not wanting to go back to being alone. Both of us were trying to protect ourselves from super painful past experiences. Very interesting.

- Current ROI vs future ROI. We actually need both.

- Lots of talk about repeating patterns

- Avoiding pain, this seems to be a trend and natural reaction.

- Shannon and I reread over some notes from a business consultant meeting from back in the end of 2019. We called it "our rejecting of things" discussion (EOT # 5295).

- Our people are wanting more structure - see this PDF for an internal adilas survey.

- Helping to frame the pitch to build on top of an existing engine vs building something from the ground up - riding on top of our existing software and team - white labeling a custom skin on top of what we have... fund that... you could get a fully funded and finished system so much quicker - tapping into existing infrastructure.

- Play the game with the massive tools that we have... quick add-ons

- We really enjoyed rereading that full element of time from the business consultant (see link for # 5295).

- What makes a mom-and-pop shop... vs a bigger business? It is mostly about what they choose to do.

- We then flipped over to the element of time # 5296 - this one was a few days later from the previous one. Another business consulting meeting.

- We may need some interplay between the jellyfish model and the value add-on core model (either way - they are tied together)

- Reading over the adilas value add-on core model (see link above) - reading section by section

- Focusing on the industry-specific skins angle - getting investments here at this level.

- We become the underlying engine and let the other companies push and sell things.

Shannon and I were going to jump on and do a work session. Steve was on the meeting. He and I ended up chatting for the whole time. After the meeting, Shannon and I went over some of the topics. I didn't take notes during the actual meeting. Most of these are from Shannon and I talking after the main meeting. Here are some of my notes.

- Steve was saying that he is planning on shutting down adilas or at least start tightening things down. He only wants to work on ROI type projects (return on investment). We tend to get pulled in many directions and don't always get paid by people who we do things for.

- Shannon was listening and showing compassion - I thought that was awesome. I was trying to follow her lead on both the listening and showing compassion. Steve is feeling pretty alone and beat-up by clients, outside parties, and even from internal sources. Software development is and can be a tough gig.

- Only funded products and projects. We have to make a switch.

- There is gold (tons of potential) but we have to remove the overburden (what is covering the gold)

- Cash flow and paying bills - even non people bills - like servers and other tech stuff and loan repayments. Steve hates debt with good reason. Back before the 2008/09 economic crash, they were quite extended for an automotive dealership floorplan. The debt became a crushing reality after sales dropped by well over half. This was back in the Morning Star days.

- Reoccurring monthly fees or revenue is the main thing that investors are looking for. We have some one-off stuff (custom code), and they don't count storage or other reoccurring fees. Especially if they go away or may go away (decreasing) - Investors are looking for monthly reoccurring revenue.

- We took some time and went over some history. We have been doing this for years and we really have been trying to do our best. It's been super tough.

- Repeat patterns - we have seen certain things over and over again. It has to be a different approach forward.

- We talked about options to scale back and then build up

- There is value in what we are doing (but we need to stop)

- The home base (golden goose) is going down... what do we need to do to save that? Steve was saying, it (adilas) is in the ER (emergency room), on life support, how do we tend to that?

- No fun to do what he did (Steve - talking to us and bringing us the bad news)

- Having skin in the game (who is invested)

- Steve said, the gun is pointed in my direction, meaning if things go south, he is the primary percentage holder.

- Staying up late, losing sleep, working weekends, etc. It has been crazy!

- SBA loans and other debt... crushing - long term - we are in a hole

- He really wants things to switch to hourly work and monitoring how much is being paid and who is doing what.

- Supporting each other

- Looking for a future vs saving what is there right now (saving the patient)

- Both Steve and I have had to chat with each other over the years - talking each other off the cliff (wanting to bail out)

- Tons of pressure for paying non-negotiable bills - everything is on auto withdrawal.

- He already went through this... meaning shutting down a company. It hurts.

- Shannon and I were talking about roots and branches and how those need to be graphed in at times to help save the whole.

- I was saying or telling Steve that I make decisions based more on gut feelings, promptings, and impressions vs straight logic. That's who I am.

- We talked about being led - spiritual stuff - getting divine help and trying to listen to what the spirt is saying.

- We want to mix things up. Talking about existing pieces vs following what feels right.

- Fundamentally different ways of looking at the situation (logic vs feelings)

- Compromise and bending but still pushing forward - mixing things together.

All in all, a good but hard meeting. I really want to keep pushing forward, even when pure logic says no. I do feel driven to help, let's see what happens. After Steve left, Shannon and I chatted and will try to mix and blend the different pieces where we can. We have to keep pushing.

Working with Shannon. We reviewed the jellyfish model page, made some small edits, and then jumped into the adilas questionnaire summary page. Reading over those documents really helps us see where we are heading. This has been years in the coming... As an observation, Shannon was saying that us not having reps (independent salespeople) has cut off some of our sales stuff. Not only sales, but we have cut off the education and support arms as well. Those reps used to provide that supporting service as they worked with our clients. We are trying to get things under control, but it has stopped the inflow of new leads.

As we were reading, it was just making more and more sense. We need to stabilize the main adilas team and provide some more structure while still keeping the adilas culture and flavor. That could be interesting - lots of work to get there. We are getting there, but it still needs some love and dedicated action. It was fun seeing some of the ideas and concepts connecting and basically seeing the dots come together (connecting the dots).

Emails and recording some notes. Then jumping on a meeting with Shannon. We spent a little while going over new changes. Lots of moving pieces. Then did some work on the glossary. Finished up the D's in the glossary of terms. We finished up with going over some plans and then rehearsing some of the possible actions that are needed (small practice session).

Joke from Shannon - She said that an accountant was giving a talk. He was talking about some crazy stuff that they have to do. He then asked the audience, what is 1+1? Of course, it is 2. If you ask an engineer what is 1+1, you may get some technical information, but it still ends up being 2. If you ask an accountant, what is 1+1? They look and around and then ask you, what do you need that to be? I thought that it was kinda funny.

Joke - I heard this one on my hike this morning with my buddy. These cannibals wanted to join the corporate life. The corporation wanted to diversify and fast tracked them in for an interview. At the end of the interview, the HR person asked them directly about being cannibals. They promised that they wouldn't eat anybody. All went well for about six months. Then a janitor went missing. There was a big investigation and what not. They pulled the cannibals in and asked them about it. They said that they didn't do it. After the meeting, the head cannibal asked his people, did one you guys eat the janitor? One of the guys sheepishly raised his hand. The leader then said, you fool, we have been feasting on middle managers, team leads, and project managers for months. Why did you have to eat someone that they noticed? Anyways, it was kinda funny and helped the hike go along better.

Good meeting with Steve. We went over tons of different things. Here are some of my notes.

- Fixing the Grok AI Agent. It is available but not yet trained. We have it hooked up, but hidden... Just us can play with it right now. It will be an ongoing project. We made it so that we could push it up live but, once again, no one knows about it and we don't want them to know about it yet. Steve wanted it to show some people that there is some potential (seeding the discussion).

- Lots of talk about sales and generating revenue. Steve wants to work with people who are willing to talk to anyone and then when they want a demo, he and Sean can step in. He doesn't want to train them on everything, just a simple salesperson who can generate leads. He wants our team to do the demos.

- Steve was asking about Alan. We jumped in and looked around at both the system (timecards) and bit bucket. I reported that I had met with him and it was a great meeting.

- We talked about adilas and expectations. There are a lot of undefined rules and assumptions. We are planning on refining some of that as we go. It just is what it is right now.

- Steve is doing tons of small mini projects for Cory. He is really busy doing all of the little things. I would say he is getting buried. I have been there so many time. I feel for him.

- We talked about a couple of possible partners and outside businesses that have expressed interest in what we are doing. Currently, there seems to be lots of demands and not much show of support so far. It is just starting out, and we aren't sure where it is going. We want the leads, the customers, and the work, but so far, it hasn't really produced.

- We are trying not to waste time and energy, but we really don't know where to go. We are basically, trying to follow the money. Picking up the pieces.

- Steve and I talked about options in sales and also trimming down our current team. We have to cut some costs. It is rough sometimes.

- We spent some time talking about payment processing and how they do their billing. They, the payment processors, usually do a percentage of the monthly credit card sales. We would like to do something similar but instead of doing just the credit card processing, we would like to do a small percentage of the total sales per month. We are thinking from 1% to 1/2 of a percent. Somewhere in there. Trying to figure that out.

- Steve was talking about robots and even payment processing is becoming more automated and even mobile. He was talking about advancements in robots and other technologies. He reads a lot and likes to keep up on that stuff.

- We would like to get our Grok AI agent up and working. We feel that we may be able to control that better than having an outside party program and control it. That is still a lot of work. Steve really feels like if we don't embrace the full AI wave, we will be left behind.

- Bryan popped in for a minute. I told him that I would text him when we were done. We were spoused to meet but Steve and I got started late.

- Bryan is working with some CPA's and trying to get them to see the vision of what we are doing. Long ago, that was Steve's vision. He wanted to fly around in his plane (he's a pilot) and go see all of the CPA's and show them how adilas works. Funny but cool, old memory. Still a possibility.

- Steve has been around a lot of salespeople. He was sharing some of his experiences. We need people in places where there are a lot of other people (businesses). We don't have anything right now, as far as a salesperson or a sales team.

- Sales is just a game of numbers. You also have to be willing to be told no. Not all personality types can do that. Steve was mentioning that we have started a bunch of people but they haven't worked out. This may not go here, but I'm going to add it in anyways. Steve and I were talking on Monday, 1/12/26. I had a meeting later on Thursday, 1/15/26, with Shannon. She made an interesting observation. We used to have a rep type model, where the rep, an independent, would go pedal and push our product. They would then get a commission and also be able to get monies directly from the client to help with anything that the client needed. That was very successful. They, the reps, would max out and eventually stop, but each one could handle a certain number of clients. We had some reps that were making great money. Because it wasn't super organized, we decided to pull that back internally. Due to budgets, we have not been able to fill that same role that those reps were providing. We have way more control over what is being done, but we don't have anybody out there pushing on things. Interesting observation.

- Back to the meeting with Steve. After we talked about sales for the first little bit, I changed gears and did a mini pitch to Steve about focusing on people and trying to stabilize the team. That conversation always comes back to funding and where do you get the money from? This has been a common theme over the years.

- I was drawing and showing some ideas. We have focused on features and functionality so much. We keep building lists and slowly clicking through things. I really feel like we need to change the focus to people and the team vs the next cool thing. The sad part is, we have done this for years and years and years. We keep thinking, when we get such and such done, it will all get better. We get to that point and then there is always something more. I honestly can't even see the end of what is wanted (feature or functionality wise). It feels like a perpetual or ongoing list of wishes and demands.

- We jumped in the system and were looking at sales, numbers, trends, year over year totals, etc.

- We may want to allow the developers to go back and bid (put out estimates) on custom code projects. That's what they used to do, back in the day. We tried to pull that all under the main adilas roof as well. That was super expensive. We may need to figure out a hybrid and see if we can make that work. We don't want a full wild west again, but we may need to bring some of the independent pieces back in. It just costs too much for us to fully support a full staff of full time developers. We'll figure it out.

- Our costs are around 40% (roughly). So, if you had a system sell for $100. We would use $40 to pay for servers and other small things. The other $60 would be profit that could be split and/or divided to create some sort of incentive. Steve is trying to see if he can get anybody to play that way. We just have to get more clients. He was pitching a 50/50 split of the profit. So, for a $100 deal, that would be $40 overhead (costs), then split $60/2 or $30 per entity that is helping with the sale.

- We were talking about setup, activation, and selling systems. We are seeing a growing demand for enterprise level functionality. They, our clients, just expect us to have it all built. They really want it, but it is only partially done, not all the way yet. We end up getting stuck in the middle, footing the bill, and not being able to just sell what they want. We already have vendors, customers, and items on the enterprise level. We just need so much more. Well, you have to start somewhere.

- Steve was talking about 10 free hours of training and then rolling into $65 per hour after that. We can help with anything that is needed, whether that be training, data entry, bank reconciliation, inventory help, balance sheet and accounting work, etc. We offer a lot of services. Basically, what do you need? We can help.

- Steve wants to find some power users and see if they would like to work for us. We have had great success by hiring people who were once adilas users and then bringing them in and onto our team. They already know and love adilas. They tend to find a good home with us. It just comes down to budgets again.

- As we were talking... I was pitching things and it kept getting met by something like... We've tried that... We need to do something different. I don't feel like that. If we did try things, the timing may have been off, the wrong person, or it wasn't really tried. I don't want to just keep randomly trying things. I think we need to focus on people, talents, skills, and personalities. If we can get the right people in the right places, and get them trained and supported, it will work. I know it!

- We may need to try things again! Lots of things are changing and been changing over the years. We have been doing this since 2001. Adilas became a real entity in 2008. We need to circle back around and focus on people.

- The topic switched to AI. Steve wants us to use AI to build code for us. He thinks that we can reduce our tech needs by 60%. He uses it tons and tons. I use it as well. We want to get our other developers up and going on it. It's not that they aren't... we just need to keep going. We need to look at it as a tool, not the only answer. It does have pros and cons. It definitely has its place. Certain things still need the human touch.

- We ended our meeting by him telling me that I could look around and work on a plan and then bring it back to him. We have to make some changes. That is for sure. I just don't want to randomly do things that may hurt us in the long run. It takes me so long to train new people. I hate to see them just go away. We have a team, but yes, they are kinda tired. We have been running hard for years and years, almost without any breaks. That is rough. We will figure it out. That's the new goal. Figure out how to make this work and stabilize the team.

There are notes from this morning... 1/12/26 - these notes may seem personal - they are what happened on Sunday 1/11/26 - I recorded them on Monday. They play into the mix as this is the backing for us trying to do what we are doing. It is personal, but still super important (to me at least).

- I was fasting yesterday - good session - had a great "download" (term from my mother) session and filled out some post-it note pages. See EOT # 12616 for details.

- I spoke in church on Sunday - I had fun - hopefully it went okay - I tried to follow the spirit.

- I also enjoyed some of the other meetings at church - Lee Lower gave a fun thought in Bishopric meeting about a guy and some healing and mending relationships - really good message.

- In the next meeting, young men and young women leader training, Reese Hulbert gave a great thought on Satan and how he tries to make us run and hide - then talking about overcoming that fear and following the Lord - how can we dispel that encroaching darkness, shame, fear, and negative thoughts - super good message.

- I was praying - as I finished, I was looking at a quilt on my bed - the diversity is awesome - all of it fits and lays together to make the whole - so fun.

- During sacrament meeting, Lilly Atkinson spoke on cheering each other along - she ended with a challenge - "take one more step" and "bear your testimony" - I really liked the take one more step challenge. Sometimes, that is all we can do.

- Heather gave a great talk in church as well. I took a bunch of notes in my church notebook - great message - moving forward with joy - becoming - "be" & "coming" - breaking things apart - we all get to be part of His work.

- Plan as if for year - act as if for years - D&C 51:17

- In priesthood meeting, Ed Herrmann, was giving the lesson on new beginnings from Elder Kearon from the October 2025 general conference. Jesus went about doing good - At the end of the lesson - Ed was talking about an action strategy that they use in the military - It was...

1. Intel (info or gather info)
2. Plan
3. Rehearse
4. Execute
5. AAR - Pause (after action report)

- Small note... I was typing these notes and got to the note above this about the military action plan or action strategy. I was able to use that little piece in a meeting that I had with Shannon on 1/13/26. That is awesome. The timing was perfect. I just finished typing it before the meeting and then I had to use it. Small mini miracle and blessing. My notes were able to tie into another piece that I was looking at on Monday night (1/12/26). We were helping our daughter do some goal planning for the new year. In the pamphlet, it kept prompting for putting your goals into this format: Discover, Plan, Act, Review - As I was working with Shannon, I was drawing a parallel between the child goal setting strategy vs the military based strategy. They are very similar. They use different words and the military one has a whole section for rehearsing or practicing before doing the actual event or action. I thought that it was very interesting. I was telling Shannon that she was technically helping me do some planning and rehearsing for where we are heading. Good stuff.

Back to my notes from Sunday, 1/11/26 that I wrote on Monday, 1/12/26... I got side tracked

- After church (on 1/11/26), I spoke with Bryan Dayton and told him that I was planning to talk to Steve tomorrow (Monday) about pushing forward - gave him a few small insights into my plan from my shaving session on Sunday morning - see other notes.

- Came home, played a game with Brooklyn

- Super yummy meal after breaking my fast - potato soup and corn bread

- Made chocolate mousse

- Played a game with Heather and Brooklyn - Heather won

- I got a blessing from my dad - we talked and chatted for a bit and then I got a blessing (father's blessing) - I have had many of these - Lots of great love, advice, inspiration, and remembering my worth - I doubt myself sometimes - Here is some advice that he gave me: Take care of yourself, your family, your church calling, and then your profession. Even though profession is forth on the list, that doesn't mean that you give it a forth rate job. He also felt that I should go and meet with Steve - face to face - really try to help - even help repair the relationship. It has been super stressful. He also recommended that I read a few poems (motivational poems) - I have those in a different notebook.

- On the going out to Salida to meet with Steve, I was thinking, maybe we have a team meeting - in person - to go over plans and such - going back to what Ed said (military strategy - intel, plan, rehearse, execute, AAR (pause - after action report) - focus on the plan and rehears sections.

- I have been in so many meetings... tons of training - that is an asset (meaning church and business meetings)

- Quick 1-pagers - Bishop Shawn Smith loves the quick - at a glance - what is going on

- I saw Reese Hulbert use a few quick - at a glance - one pagers for a training meeting. They really seemed to help.

- Contact Gene to see about getting some funding for a big push. Sent him a text on 1/12/26.

- Graphical homepages

- Finish up the MVP list - Estimating somewhere between $500-$750K to finish up that push and those pieces.

- Work as if for years

Emails, paying bills, reviewing notes from over the weekend. Planning for a meeting with Steve. Reread some great poems that have a great message. Click this link to see the poems (on a different entry from a couple of years ago). Pushing up videos to a new folder inside of google drive.

Translating from post-it notes on 1/11/26

- Sunday morning - I was shaving, getting ready for church. I had a flood of ideas come into my head.

- We go for it on 4th down (football analogy)

- Reinforce the team - goal 1

- Goal 2 - We make sure that keeps working (meaning goal 1)

- Morning meeting at 9:30 am (get some communication stuff going on)

- Let people (our team) run... minimal on the micromanagement

- We focus on people... there will always be more projects and features

- CSS on forms for classic looking forms in the snow owl theme

- Look and feel to snow owl - help fix internal and existing pages look good

- Training - could be internal training, AI training, or external training

- Presentation Gallery - Keep pushing on that project

- Images for the adilas lite plan and the investment opportunities

- Abby - Talk to Steve about getting her involved

- Work with the design team - Chuck, Piper, Sarah

- Move key videos to Google Drive vs on the content server. It just can't serve them up quick enough.

- On the AI Agent - Use what we have - Set it up so that it tells people "I'm good at nav" - Polish the 350 existing prompts and tools.

- Suzi - Step-by-steps - small documents with information and instructions. She is really good at that.

- Sean and Cory - General Training

- Prepare for 100+ new accounts - What would that take?

- Open things up!!!

- If needed, we have others who can help - Dustin, Eric, and John. There are others as well.

- Shannon - She has been such a great helper to me

- Let Alan lead out - Help him succeed. He can do so much more than code.

- Get out of the way

- Leverage debt - put all of the adilas shop or adilas lite stuff into adilas as real payables - bring it out of hiding - true costs and costing

- Co-owner Advocate - possible new title, if needed

- Mini bank accounts for each person and/or department - help the team feel safe, supported, and funded

- Be in someone's corner - believe in them

- Overcoming fear - Satan wants us to run and hide

- Simple 1-pagers (one-pagers) - at a glance

Working with Shannon. We spent more time on the glossary of terms. Most of our work today was in the D section. We also spent some time at the beginning talking about changes and how AI is affecting our worlds, in both good and bad ways. Very interesting. It is just a tool and has both pros and cons.

Working with Shannon. Going over glossary terms. Finished up C's and started into the D's. Good session.

Working with Shannon on doing some definitions and glossary terms. Started working in the B's section. Finished up that section and got part way through the C's. Good session.

Work session with Shannon. Working on the adilas glossary of terms (element of time # 4030 in the adilas university site). Finished up the A's and started into the B's. We have a long way yet to go. Fun session today.

Working with Shannon on glossary terms. We were in the "A" section. Going over some the verbiage and doing some light clean-up. It may be a while, to get through all of them.

Towards the end of the meeting with Shannon, Shari O. jumped on. I was helping Shari O. out with some changes for a client (corp-wide settings and custom invoice stuff). I showed her how to do some light HTML to add some bolded items and some line breaks to a disclaimer. We chatted about other stuff that is going along as well. Good catch-up session.

Working with Shannon. I was showing Shannon my notes from the past week. One of the entries had some notes and my spiritual experience (planning and brainstorming on training the AI agent). See element of time # 12527 in the shop for more details. Going over the power of the plan - reinforce, recruit, and then share it. It feels like a mini parallel to God's master plan. Another part of it deals with helping adilas get ready to go out to the world and be a tool that could be used.

We spent some time going over concepts and showing her what the context window was (concept) and how to help make it function at the appropriate level. She then helped me as we talked about using the CMS tables on adilas university (the corp inside of the adilas application called adilas university - corp id # 371) to create and make the global context records. CMS stands for content management systems. All of adilas is basically a giant CMS type application. We will use our media/content database table for those global context pieces to help train the AI agent and our users. It is perfect, it already exists, and has been being used since 2013. We will just repurpose a small portion and use it more heavily from within the adilas university site and corporation.

Switched over to working on the white label section on the fracture (deeper development and system code) build out. We finished up that section. Yeah! After the meeting, I sent Steve a text about using the media/content database table as a CMS system for adilas university and global context stuff. That will be super cool, and it is already done and functional. What a blessing.

Working with Shannon. Showing her the progress with the AI agent training. Then jumping into new changes like the add bulk po line items. She wanted to see some of the new features and such. We then switched over and worked on more content for the adilas lite or fracture buildout. We are getting close. We only have one more major section on the fracture page to finish up our first-round planning for that page. Today we finished up the lessons learned, the life cycles and maintenance section, and started working on the white labeling section of the plan. See the fracture page in the adilas section for details.

Working with Shannon. We spent the whole time working on the fracture plan about lessons learned from doing 20+ years of work on this project. Shannon and I were drawing a bunch, going over concepts, and brainstorming on what we want things to look like. After our meeting, I did a little bit of research and read some of the other content that we have been working on. On the lessons learned section, we didn't quite finish up, but this is what we were coming up with... content to this point.

One of our most encouraging lessons is that we are successfully creating an application that we've dreamed up and worked for. It is totally possible. We are systemizing business functions into an integrated platform that other companies have been separating into multiple different applications. We have been doing this on a garage budget, with limited resources, for 20+ years.

We have built up this application by prototyping features and functions to meet various needs. Many of these needs and wants have come directly from client input and requests. To summarize what we mean by prototyping, our process starts by determining a want or a need. Then we do research and brainstorming and figure out the plan. This could include trying to use new techniques or doing things that would further the product along. Where possible, we tend towards permissions, settings, and templates. Then we build it out and let others use it. They beat it up, and we make any revisions that are needed. Once it is being used and our clients are loving it, they often let us know what they want for the next steps. This pattern has occurred over and over again. This prototyping process has allowed us to build out the entire adilas application over the years. The result of this is a robust, revenue producing, and versatile system that is meeting the needs of our clients.

Our approach going forward is to continue following this pattern. If we do receive more funding, we will adjust our approach accordingly. This may include building out a more detailed master plan, using teams, hiring specialists, and other development techniques. If no additional funds are available, we will keep dreaming up new ideas, doing research, experimenting, prototyping, building, and moving on. This is what we do! If you want to see an overarching view of our master plan, please see the value add-on core section.

With 20+ years of experience, there is no way that we could fully put into words all of the lessons learned. However, we have documented the whole process through a section that we call the "developer's notebook". This notebook has been a running log of ideas, concepts, lessons learned, and other notes that we have collected over the years. It has been a great resource for us to refer back to as we continue to build and improve adilas. Just as a sample, if you go to that page and type in the word "fracture", you will see a number of notes and ideas that we have collected over the years that relate to this new buildout. There are over 200+ entries just on that subject alone. If you want to checkout the developer's notebook, you can find it here: Developer's Notebook by month and year or search the developer's notebook by any subject, use this link and associated form.

Working with Shannon. Going over new changes. Looking around in the Nxtlinq backend application (AI agent backend dashboard). It looks like we can edit things and upload documents now. That will be awesome. I haven't played with it yet, but good to see progress. That should help us with training it and helping certain pieces of global context to stick and be available to all users.

Shannon and I then went into our work on the fracture (adilas lite) plan. We were working on the section about lessons learned over time. We are wanting to show that we have listened to clients, done tons of prototyping, and are actively building out the master plan. We have captured tons of this process in the developer's notebook and are excited to really put the whole master plan together and go from there. We truly have experimented and prototyped numerous pieces of what we plan on doing for the whole fracture project. That is super cool.

Quick touch base with the AI agent to see if it was able to remember anything from the training session the day before. Sadly, still no long term data retention. Recording notes and formatting the stuff from the AI training session.

Got a text from Steve and we jumped on to the gotomeeting session. We were talking about the AI agent and where we are at. Steve had me check ChatGPT for something that he put in there just the other day. It was able to find it. We are thinking that we may need to train up the main or mother AI model or AI engine. We may need to look deeper on that. I also went over what Shannon and I were talking about this morning (see element of time # 12458). Good conversation.

Working with Shannon. Talking about the time it takes to use the AI agents. Talking with Shannon about the type of AI tool we are trying to use and setup. We spent some time talking about concerns and possible constraints, moving forward.

My constraints:

- I'm willing but should we do this? I really want it to work - I can see the potential - We need a master trainer that can help others

- We need to communicate - Steve and I

- My time

- Already put in a ton of time

- Questions on funding and budgets

- Train the mother AI engines and models or the mini model? Which one(s)?

- I need some direction - too many things on the plate and I don't know what to prioritize

- The training pieces are all over (on the web and in certain docs) also in my head - No one spot for all training currently

- Things keep changing

- I am saving my conversations with the AI agent, but it takes time to format them, and if it (the training) doesn't stick, then what?

- Putting in energy but not getting the output that is desired - we can only go fast for so long - we can keep chipping away at things, but that is it

- There are lots of parties involved, adilas, Nxtlinq, our users, and the actual AI agent

- We have a vision and we can build a number of things out... we have plans - those plans will take months and months - kinda feeling pressured

- Do we really want to have meetings every two days

- Tons of potential... how far are we willing to push it?

AI agent constraints:

- I've done x hours on the mini model, currently not retaining anything

- Storage at the database level - For them and for us - How can we help this process?

- How can we help with storage - Known needs - System level, corp level, and user level

- They are retaining the chat messages - At the Nxtlinq level - We are not

- Question - How do we really train this agent or entity?

- It, the agent, is giving bogus answers - For example - How do I get rid of an element of time - How can I tell how many elements of time I have (see stored chats from 11/25/25 - Some other user, not from me)

- Can it do what we need it to do

- Cut off from the mother, meaning the agent or mini model - Already over a year behind the data on the mother AI engine

- We don't know the model that it is based on... It really likes the security and blockchain stuff - Meaning what was the original purpose of the AI agent.

- We just need a simple bot that can translate natural language into adilas tools and prompts

- Not retaining information long term... Currently only per person, per session, and that's it

- How are they doing with the crawler to pick up content

- Demands - too much on us, build, train, market, deploy, and it doesn't even work all the way yet

- People aren't wanting it... what it currently is and can do... It take too long, it requires too many two-part authentication stuff, and it can't do advanced or multi step things...

- It is being used less and less - People want it, but if it gives them the wrong answer and isn't fast enough, they will move on

- Too slow, not helpful enough (wrong answers), too many auth steps, can't do complex actions, etc.

- Say you aren't using it... then you decide to use it... and it takes multiple steps to do the auth stuff... you have a quick question and you want an answer in a couple of seconds... you then have to do a multi-step 2-5 minute process to get your answer. Pretty soon, you say, no, not doing that... that is from our users.

At the end of the session with Shannon, we were talking about our simplified AI plan - 1. Teach it how to do some basic or system navigation, 2. Get it all trained up so that it can help with training and support, 3. The ideal is that it knows everything and can help with the higher consulting level and business level questions.

Shannon and I were also talking about the jellyfish model and helping to stabilize the team and their roles. There is a need there.

Working on new content for the adilas lite and fracture plan. Shannon and I were in the section dealing with desktop first, responsive design, and mobile ready options. We had a great little session. Here is what we came up with:

/////

We are focused on a desktop first design that is also responsive for tablets and phones. This means that the whole system will be built to work on desktop and laptop computers first. Mobile first design is great for simple apps, but we have built a complex app that needs a desktop first design. Most of our clients and users are physically at a computer while working on adilas. There is no way to get huge reports or data capture forms into a super small mobile view without losing functionality. Focusing on desktop first design allows us to create a full featured experience for our users.

Even though the focus will be on desktop first, we will be building out the entire fracture project with a responsive design. Responsive design means that the system will adapt to different screen sizes and devices. This allows us to create a seamless experience for users, regardless of the device they are using.

Full mobile ready design, and functionality, will be used in customer facing portals, ecommerce, and other specific use cases. We will also create certain admin and user interfaces that are more mobile friendly. Most of these smaller mobile friendly apps will help with specific tasks and functions. That will keep the mobile experience focused on the task at hand while still being able to fall back on the full desktop experience when needed.

One of the goals of fracture is to empower the users to customize their own user experience. That means that, based on the user and their device, they can toggle on/off any buttons, features, report columns, etc. That allows a desktop user to customize their workspace, while a more mobile type user could simplify their interface. This flexibility is key to ensuring that all users can work in a way that is most comfortable and efficient for them. Our users vary greatly, some like touch screen, others use their phones, while others are mouse and keyboard people with multiple monitors. Our goal is to create a dynamic application where each person feels in control of their own experience.

Our other hope is that outside users will catch the vision of the API and build out specialty mobile apps that connect to the adilas backend via the API. This would allow for more specialized mobile experiences that are tailored to specific industries or use cases. This could be simple native mobile apps, SPA's (single page apps), custom interfaces, or other types of mobile friendly apps. More information is available in the API section above (the real pages doesn't have a link here, but it refers to the fracture plan and the API section of that plan) or from the adilas marketplace.

Work session with Shannon. She really helps me carve out time to work on some of my long term goals. If it weren't for her, I would get sucked into the main mix and other demands inside of adilas. I love it that we get to work on these things (other projects and dreams). As far as work today, we spent most of our time working on new content for the fracture buildout section of the adilas lite plan. Today we were finishing up the stuff on front-end and backend validation processes. Here is what we came up with:

//////

This validation section deals with security of the data being passed around, and/or transferred, from client to server and back again. The term client-side validation deals with checks and balances before the webpage or form is submitted. This front end, or client-side, validation can really help with the user interface and user experience (UI/UX) parts of the system. This type of validation can help catch simple mistakes, typos, or missing information before the data is sent to the server. This helps speed up the process and reduces server load. If the data doesn't pass the client-side validation checks, then the user is prompted to correct the errors before submission. This is a great way to enhance the user experience and reduce unnecessary server requests.

Server-side, or backend validation, deals with what goes on once the webpage or form leaves the user's computer and hits the server. The server is the backend brains of the application. Backend validation is responsible for checking and making sure that anything submitted is viable and can be used in the requested action. This backend validation is very secure, it can exist in multiple levels, and may even be stacked if needed. If backend validation is used, and the data doesn't pass the validation checks, then the server throws an error. Depending on how deep it is, the errors will stop the process and the desired action is not completed. One or more error messages then get passed back to the client. Error messages are required for communication with the users. However, they may lightly detract from the user experience.

The best combination is a good mix of both client-side (front end) and server-side (backend) validation. We, as a company, are already doing a lot of this mixed validation. We are currently heavier on the server-side, but both options are being used. Moving forward in the fracture buildout, we will continue to keep the server-side tight. We also plan to enhance the client-side validation to make the whole experience even smoother for our users and clients.

Working with Shannon. Showing Shannon some of the work with AI that we are doing and some of my training plans (see attached scans). She had some great questions about my plans and what they mean. Talking about teaching the AI agent. We also spent some time talking about what is still needed... (more than I want to admit). It really does take a lot and there are a lot of unknowns along the way. The adventure begins... good thing that I like adventures. Shannon was talking about her own life and figuring things out and finding her (my) own way. I normally don't want to take the regular path... I want to take the adventurous route. Well... wish granted... No wonder that is so challenging sometimes. Shannon and I then chatted a bit about challenging tradition. That's a big task!

After our mini therapy session (just kidding, but real...), we jumped into working on the fracture buildout plan and did some work on the backend and front end validation section.

Work session with Shannon. We worked on content for the testing and integration plans for fracture. Going over what has worked and what are plans are going forward. We may tweak it a bit, but here is what we came up with (first round).

/////

We started the original adilas core back in 2001. At that time, testing was only something that you did as you built the different pages and functionality. Back in the day, we had one primary developer and he was in charge of the system. As new developers were added to the mix, and as time has gone on, the need for better, more structured testing has become evident. This combination of naturally growing the code base and meeting client needs, has helped us pioneer a successful web-based application and service our clients for over 20+ years.

Sometime between 2018-2020, more testing was generally added to our process. We have developers who are doing unit testing, mocking data, performing database connections, load testing, and running deeper integration tests. That has been a good shift for us as a company. Our plan it to continue along those lines, and even increase our testing focus.

The adilas user base has been a huge asset. We offer such a unique product and each company/user uses it in so many different ways. This has helped us get very unique testing coverage based on users and their system usage. We have actually added over half of our features based on user input, feedback, requests, and ideas. We love that. We plan on continuing in that path as well and will actively seek user feedback and input.

Additional testing, will help stabilize and improve ease of use as we keep building. Here are a few ways that we will continue with testing and integration plans:

• Functional and characterization testing - what does it currently do
• Unit testing - what are the individual parts and pieces - functions and methods
• Integration testing - how does it work with the other parts of the system
• Versioning and code repositories - historically tracking changes and auto deploying code to production servers
• Documentation, help files, and SOP's (standard operating procedures)
• Other testing and integration plans

Meeting with Shannon. We did some review and jumped into talking about API sockets and possible usage of the API's to add to the existing adilas transactional data core. See the API section of the fracture or adilas lite plan.

Working with Shannon. We stated out the session talking about building on what we have and filling in the gaps. We talked about building bridges vs building walls (one lets people in and the other keeps people out).

We talked about API's, sockets, endpoints, and how all these things play and flow together. I was drawing up a storm. We spent a bunch of time looking at some graphics in the teaching gallery and then drawing on top of those graphics. We then flipped over to work on content in the adilas lite and fracture plans. We were working in the API socket section of that page. So many potential benefits and ways to use it. One of my big takeaways was how this could tie-in to the value add-on core model. We, adilas, create the master road map for our product that is called the value add-on core. Adilas is going to build out the main transactional core (level 1 of 5). Any other level could be built out and/or added to with the API. We can't even fathom all of the possibilities. If you want more information about the value add-on core and all of the levels of the master plan, please see that section. Here is a quick overview of the adilas value add-on core model...

Level 1 - Adilas Transactional Data Core

Level 2 - Industry Specific Skins

Level 3 - Custom Code

Level 4 - Business Intelligence (BI)

Level 5 - Enterprise (multi world)

Working on back threading help files. Fixing 25 files that I did last night with some new verbiage. The new stuff flows better (thank you Shannon). Working on new back ties. Did a bunch of new ones. These back ties or back threading is where I go to the help file and put some navigation or nav help on the help file. Normally, a user will go to a page and then maybe look at a help file. We opened up the help quick search, so now, technically, someone may find the help file first and then want to go to that page. Basically, a mix of help files and AI quick search prompts to thread things back and forth.

Working with Shannon. We did some reviewing, lots of drawing, and working on some new content for the fracture (adilas lite) buildout. Shannon also helped me edit a number of new paragraphs in some of the help files. She was kinda like my editor today. Good work session today.

Good meeting with Shannon this morning. She was helping me through a small/big (not sure) paradigm shift. We were talking about adilas lite and fracture - proposed project to rewrite the adilas.biz code. It is super deep...

We were talking about instead of the old ship A and new ship B type model, what about ship A becoming or morphing into ship B. Most of our previous talks and content building sessions have been focused on ship A being the older or current model and ship B being the future model (something that was in the future or completely new). We have known about this... but most likely in denial of it... about the fact that already, whether we want it or not, we are starting to morph and change ship A into ship B (what we want). I still think that the ideal is ship A as the working prototype and ship B as the new buildout, but that is not the only way that it could happen. This was the paradigm shift that I was going through this morning...

- Ship A to ship B transformation...

- Going over ideas and what is happening... (all of the events and things that are happening inside of adilas right now)

- The writing is on the wall... It is changing, right in front of us. If this were the case (and it is), what can I do to help that along?

- Building within the context of what we have vs something that is completely in the future.

- Shannon was being a great sister (and counselor today). She was saying, ask God and see what He says. Figure out your direction based on what you know and where you hope to go.

- This little paradigm shift is a big load or big deal if we are looking for a rescue... (somebody to come in and fund this and/or take over and help to manage the progression). So, now what do I do?

- The book "The Horse and His Boy" (by C.S. Lewis) - The lion pushing the horses that last mile - helping to put some fear into them to make them go faster. Sometimes we feel like we are being pushed by a lion... Just having fun with it.

- Be open to a couple of different potential directions

- Story of the wrong roads... They went down the wrong road, then they figured that out. At that point, they knew that one of the roads was incorrect. They could then take the other road with more confidence. Shannon and I were talking about knowing that it is not the right way - Potentially, over and over again...

- We added some good humor in this little discussion and brainstorming session.

- We have been doing this (changing and putting layer upon layer upon layer), over and over again, for 20+ years... Even layouts like classic to snow owl and coding changes from ColdFusion tags to ColdFusion script. We have been dynamically changing for years and years. That is awesome!

- End goals are the same... It is just how we get there...

- Rereading some things in the developer's notebook... (rejecting and pirate ship)

- Recognition... This is one of the steps to moving forward.

Recording notes and getting a check for Shannon. She has been helping me build out content on the adilas lite (fracture) plan. Huge help and I enjoy working with her. Also, see attached, she takes some good notes. This is not a public viewable element of time (what she was working on) but I liked her notes.

Talking with Shannon about prep steps and being guided for future projects. How these AI quick search prompts are actually helping us as we keep moving forward with some of our other plans. We didn't even know that this was going to be a stepping stone, but not it looks more obvious that we needed this next piece in place before we can really charge forward. We have a number of plans that have felt way out there... pretty normal for us (hard to reach or know what to do to get there). With this new development and push (months and hundreds of hours), those pieces are within a touchable range now. Shannon and I went over an element of time (eot) in the shop... EOT # 12392 - it has a number of fun ideas of where we can go and how we can use these AI quick search prompts heading forward.

Switched over to the fracture plan - talking about frameworks, code, and server changes. Lots of opinions here. For the new content on that part of the plan, we kinda skated over it and left it kinda vague on purpose. Click here to see the adilas lite or fracture plan (as we are building it out and roughing in content).

Working with Shannon. Small recap on what we were working with last time. Talking about templates and going from static to dynamic templates. We briefly talked about when I started creating web pages, each one was a static page (copy and paste) from template of sorts. Then once we added database connections, we really were able to use a dynamic, data-driven template page. That was a huge building block.

We then switched over to adding new content for the fracture plans. Working on the modular architecture sections. At the end of our session, we were talking about old CSS and more modern CSS stuff. We even looked at some examples (some of our old stuff). Crazy how fast things are changing and what it takes to keep up in this high-paced world.

As a side note, we were working on some new documentation and using AI to help us refine some of the content. It started to joke around with us a bit. That was kinda fun. It added a couple of sarcastic prompts. It made me laugh and Shannon and I had a small discussion on "joke settings" and "changing levels" on those settings.

Working with Shannon. She and I were working on the adilas fracture and adilas lite content (planning). We kept bouncing between creating new content and what is going on inside of adilas. Fun to see how things are working together and we are making progress in leaps and bounds. It feels like we are sewing things up and bringing things together. Today we were working on sections for customize everything and setup wizards. Good session.

Working with Shannon. Looking around a bit on some of the existing pieces that we have pushed out recently (AI quick search stuff). Small tour and update for Shannon. That was fun. Looking at potential and current paradigm shifts (our way of thinking). We looked at some plans that we are making and also spent some time looking at some graphics (prep stuff and planning). We know that we will have some needs for more content (writing things up) and graphic design work coming up soon. Looking to see what we can have Abby (my daughter) do to help us out. She would like to start working with Shannon and I next week.

Switched over to planning and writing out content for adilas lite and fracture page (plans). We were on the customize everything section. As we were talking, we got into a conversation about the adilas transactional core and the strong foundation of permissions, settings, and templates (grouping things together for storage, speed, consistency, and organization). We haven't talked too much about templates yet. Templates help you group, organize, and setup a pattern of sorts - make it quick and repeatable. We talked about industry specific skins, bulk settings based on functionality, and other templates that exist right now. Technically, even the organization of the adilas database is a template of sorts (what goes where and how do things work together). We got into talking about organization within pages, dynamic content, what is static, what is dynamic, and what is alterable by a user, based on permissions and settings. We talked about different levels within the settings and how to group things together. We see at least four levels in the settings at this point. They are corporation level (world level), group level (main players), page level, and user level. Fun conversation.

Working with Shannon. Small recap of what we are working on. I showed her some of the new AI options, keywords, and prompts. That is going well. We then switched over to working on new content for the adilas cafe project and fracture (adilas lite). Good session. Next time we will be adding in more content to the fracture and adilas lite plans. Good stuff.

Working with Shannon. Working on adilas lite content and new content for the adilas cafe page and plan. We went over the overview, personal profile, ways to work, and ways to play.

My hiking buddy, Brian Stewart was recommending that we (at adilas) sign up for a Square and Shopify account. Then go in and see how easy they are to use. Our stuff tends to be more complex and complete vs super simple. There is some real value in super simple. This is my take on it... We are trying to make it more technical so that we can simplify. That may seem like a random way to simplify (making it deeper or able to be split into miniature pieces, but that is where we are heading. The same is true for the adilas lite or fracture project.

Showing Shannon how we can almost take it to a super simple Google type level - with our AI quick search interface. As we were talking, it came out that sometimes we tend to fall back to what you know when things get crazy or stressful. Good insight. Working on content for the adilas lite project - codename fracture. Also, spent some time roughing in the content for the adilas lite - other business plans.

Seeing the vision through the clutter. Sometimes you have to make a mess in order to really get things cleaned up. We spent some time talking about the value of documentation. Just for fun, Shannon and I were talking about recording notes and ideas. We were making fun of "my post-it note garden..." :) I have them planted and growing around my office (not really, but it was kinda funny to call it a post-it note garden).

Working with Shannon and Suzi. Started out with Shannon. We were reviewing some progress on the AI quick search. We did some testing and made a few small changes. Talking about the need for documentation. Suzi popped in and we went over some instructions and direction for a project she will be helping with. She is going to be making some screenshots and documentation on how to run simple POS (point of sale) functions inside of adilas. After Suzi left, Shannon and I went back to working on rough content for adilas lite - fracture plans.

Suzi jumped on with Shannon and I around 12:30 pm vs 11:30 am. I probably wrote it wrong in the email. We got it all figured out.

Working with Shannon. I was showing her the expanded AI quick search options. That was kinda fun. So much potential there. Talking about what we can harness..., quickly and efficiently. We then read over the overview of the adilas lite - Fracture project - this was what Steve got back from Grok. Shannon took some notes.

These are notes from Shannon: Brandon reading the AI summary of Adilas Lite:

- Project overview hub - Adilas ecosystem

- Ambitious roadmap for next generation SaaS map

- Clean, modular, teaser, further explanation

- Solid, forward thinking, scaling Adilas from ERP to community

- Flexible, customizable, modularity, user centric - following SaaS trends

- Technical depth and community

- A vibrant hub for

- Teaser heavy - would like to see more visuals, demos, things to make it more engaging

- Grow into a dynamic dashboard overtime

- Jellyfish model and jellyfish analogy - adaptable and fluid, recurring revenue with add-ons - monetize ecosystems, rapid scaling if the core offering hooks users

- Value Add-On Core model - technical meat, starting at transactional data to unlimited, scalable at a level people can understand

- Adilas University - essential for adoption, helping growing community, build loyalty, include gamification/certification it could be even better

- Adilas Marketplace - huge potential for revenue drive and ecosystem builder, success depend on curation to avoid quality issues

- Adilas Cafe & Communities - slack-like portal, one-stop shop, broaden the appeal beyond users, social features - a community first brand

- Adilas Lite - Fracture - the crown jewel, rebuilding with new code, toggle on/off - this screams user empowerment... a lot of other great things!!!! - could separate Adilas from other more rigid Sap and Oracle

- Other Business Plans - lots of other great things that I didn’t get recorded - got caught up in listening to these last two - lite and other plans

- Adilas Videos & Research - transparency, keep community invested, ties things together, road maps could be invaluable for developers eyeing integration

- Vision - building a sustainable interconnected world around it

- Improve - more interactive elements, make it live and searchable,

After doing this, we then switched over to building new content for the adilas cafe page. Working on sub content. Good session.

Work session with Shannon. Going over some plans and what is going on in the adilas world. We then jumped in and finished up the last three sections on the adilas marketplace.

Working with Shannon. Light overview of what is going on and new changes that are playing through. Things are always changing. We got into some plans, changes, and some vision for the future. That was fun. We also talked about how to teach an AI agent and how to help it know how to play with our stuff (do work inside the system). That turned into a small discussion on machine learning. We went over some security things and what we are doing to help secure things. You have to think of all kinds of options.

We then switched over and worked more on the content for the adilas marketplace plan. We are making good progress there.

Working with Shannon - new content for the adilas marketplace plan. Most of the session was listing out professional services.

Working with Shannon. Talking about the translation layer and how the AI bot will interpret and then translate to the correct prompt. Started working on content for the adilas marketplace. Trying to show how the adilas application creates needs and wants that can be supported and serviced by other outside professional and businesses. We call it byproducts, but basically, as people use the system, they will have wants and needs. It becomes a full system once things get intermixing together.

Here is an analogy that we did for a ski resort and comparing it to adilas.

To illustrate how byproducts fit into the adilas business model, think of a ski resort. The main goal is to get people up and down the ski hill. However, people coming for skiing may also need things like rentals, lodging, a ski school, food services, ski patrol, retail shops, etc. You get the idea. The ski resort doesn't have to own or run all of those other entities. However, the main service offered by the ski resort creates a host of other opportunities and services that can readily be paired with the original product. Inside of adilas, we play the role of the ski resort and facilitate opportunities for other entities to provide the additional services.

Working with Shannon... showing her some of the new stuff. We went over options for using cookies and URL's... potential for letting AI agents use adilas. Talking about AI agents and how that could really help with education and training. We also spent some time talking about inspiration and how we each get help in different ways. Shannon and I dipped into this subject for a good little while. That's how we get our answers and direction. Switched over to working on content for the adilas university page and plan.

Working on content with Shannon for the adilas university project. We were talking about resource coordination, and I was telling her some of my dreams and visions. Here are some small notes:

- We want other people to come in and help with the training - adilas marketplace and adilas university

- These new parties (adilas marketplace) will have or help provide active and living training pieces

- Not a specific idea or plan, very open right now

- Adilas will do some training

- We will also open it up and let other people do their own training

- Resource coordination, putting together whatever combination that is needed

- Training is a resource

Working with Shannon on content for the adilas university plan. We went through and read through some sections dealing with a video libraries, tracking education and progress, SOP's (standard operating procedures), internal & external needs, and online & in-person training events. Slowly working on new content and plans.

Working with Shannon on content for the adilas university project in the adilas lite master plan. We spent some time on the value of education and then into some information on the proposed video library that we will be creating. Good session.

Working with Shannon. We were talking about adilas university stuff and the value of training and education. Here are a few of my notes:

- Recircling back around, even after 10 years, to older projects and plans. Part of life.

- I was telling Shannon about how Steve is trying to use the adilas API's and provide documentation to folks. That's exciting!

- Spent some time talking about finishing up projects and doing the training portion (last part of the project). Sometimes that last part is the hardest.

- We looked at Udemy (online learning portal). Looking at the general flow, prices, how things are categorized, etc.

- We reread element of time # 12145 and talking about those points... lots of topics there that talk about the value of education.

- People want mostly intuitive features, quick training, and easy to use applications.

- Looking for expert knowledge. Reps and consultants. We have used these (reps) a lot in times past.

- Possible disconnect between pricing and learning curve. How much buy in, value, ease of use, and will this be a good experience? What are our clients looking for? Are we trying to be the cheapest or the best? There is a difference.

- Talking about value-based upgrades and user perceptions.

- Using the adilas API as a 3rd party white label - tons of potential there. Play at the wall.

- We spent the rest of the time working on content for the adilas university page in the adilas lite plan (fracture stuff).

Working with Shannon. Going over pioneer background. Then working on new content for adilas university stuff. Spent some time on the intro and then started on the section for the value of education and training.

Shannon and I were working on new content for the adilas university page. We were talking about education, training, and support. They are subjects that are dear to my heart. Here are some of my notes. They are somewhat random but part of what we were talking about and going over.

- Flat line - What if you could kill an application or system (flat line it) by not providing enough support and training? Can that and does that happen? Looking at adilas financials... Where are we at?

- Filling the gap - If we are missing the training, education, and support pieces... then what? What happens if we are missing those pieces? We have them, they are just small ish... who is filling that gap? Talking about how adilas used outside or independent reps for years and years. That really helped fill the gap. Who is doing that now? Internally or internal teams?

- Talking about a 3-way stool or a 3-legged stool (sys, $, edu) - One of the three legs is the system or the features within the system. Another leg is the clients or the money that they bring to the table by using the system (users). The last leg of the 3-legged stool is education and training. Without a robust third leg, your growth may be limited. Ideally, you balance things out, so that all legs or pieces are equally stable.

- Another 3-way relationship is between maintenance, education, and new. We keep chasing the new features, but we may be missing the education and the maintenance. We were talking about levels of satisfaction. These satisfaction levels usually come from things that are well maintained, users have adequate education and/or knowledge, and things are steady. Or sometimes, people find a level of satisfaction through a constant inflow of new (unlimited needs or lust for new features). I was telling Shannon, that for a job I have with a ski school (snow sports), we often get questions about the terrain park, at the local ski resort. People tend to be happiest with well-maintained features and educated skiers and riders who then use the features in the correct way. Some people only like it if there is something new. This demand is super hard to keep up with. However, if you don't maintain it or educate riders (public users), the new features quickly fall into disrepair and can't be used, thus requiring either more new ones or maintenance and education.

- MVP levels... minimal viable product, minimal viable plan, minimal viable person.

- Structural failure (at what point)?

- New features are exciting but they can become tiresome and non-fulfilling - too much chaos. I would rather have more stability over time.

- We know that there is a need for education and support. We had some of our reps that were making more money than we were making (filling that gap). There is value there.

- I have been in demos and meetings, and the question has been brought up, what about education and support? We do have an answer, but it is not super strong. Support is huge (we were talking about two potential bigger clients). That education and support piece is a huge checkbox that is not being filled. Question, could this be a bigger checkbox than all of the features (feeling the security of being able to get help)?

- See a need, fill a need.

- Fear and how much time it takes to do and learn something. What is an ERP system? We did some light research (see below).

Shannon and I looked up ERP software. Here is the definition that they provided:

ERP software, or Enterprise Resource Planning software, is a comprehensive business management solution that integrates and streamlines core business processes across an organization. It helps manage various functions such as finance, HR, manufacturing, supply chain, sales, and procurement, providing a unified view of activities and a single source of truth for decision-making. By automating processes and offering insights, ERP systems enable efficient management and real-time data access, ultimately enhancing organizational performance.

Working with Shannon on content for the adilas master plan. Finished up the enterprise level content (see below). We then reread the whole value add-on core model page.

Here is the content we came up with for the Enterprise level:

Level five of the value add-on core is what we are calling enterprise, or the enterprise level. Not every client or corporation needs this level of interaction and functionality. That is why this level is the top most level of the value add-on core model. For those who do need it, it becomes the unlimited top end and allows for all kinds of functionality between multiple locations or multiple corporations. Enterprise could be a number of different things, but essentially you start getting into a scenario where you have one master corporation that controls smaller entities. Think Sci-Fi (science fiction), top level control or dominance. You always have the aliens with a master ship that controls all of the sub ships and sub armies attacking the planet. Below we will paint a small picture of how this may look. Once again, this is not required but has huge potential for those who want and need it.

Back to the business Sci-Fi levels... In a world building analogy, imagine a universe level. You have multiple planets, solar systems, clusters, all kinds of things that are interacting together. Normally, most of your transactions that happen inside of adilas are on a single world, or on a single planet type level. That is what we would call a corporation or business entity. In the enterprise realm, you are starting to mix and blend worlds and/or corporations. This is great for all kinds of businesses where you have either franchises, mother/daughter type corporations, vendor/distributor, or entities that are somewhat connected and have either shared financials or shared ownership.

Inside of the enterprise level, we have already defined a number of pieces with data flow going both up and down the chain, big to small or small to big. Data flow is really important and helps with communications and reporting. The real value of that communication channel is too broad for this discussion, but it is essential for enterprise level transactions. You could also add any amount of custom code to create rules, automations, functionality, special relationships, or define any other need for the flow of data. Custom code at this enterprise level is how you fine tune your processes and cater the software application to your business needs.

One of the goals of an enterprise level system is normalization, meaning normalizing or standardizing your data. You can have multiple different businesses, all running on adilas, and they can all use the same terminology and the same type of accounts or landing places for your data. This allows data to flow up and down and in between worlds to help with reporting and business intelligence. It then allows you to pull standardized reports so much easier than pulling individual reports and trying to blend them together with spreadsheets or other methods. Depending on the size of the company, some of this normalization can be very cost intensive and even painful. Sometimes there are even teams setup specifically for the purpose of extracting and normalizing data from multiple software systems. The adilas enterprise level has incredible value and helps to overcome some big pain points for traditional companies. Think business intelligence on an enterprise or universe type level.

Here are some other benefits of the enterprise level:
- Master lists or libraries of data - items, vendors, customers, photo galleries, etc.
- Shared loyalty points and gift cards
- Multi-locational or multi-corporational
- Bulk tools, rules, processes, and scheduled tasks
- Consolidated banking and financials
- Consolidated reporting and business intelligence
- Permission levels and security
- Automated routines and processes
- Options for custom code

Amazing potential in the enterprise level! This is the top most level of the value add-on core. You get to mix, blend, and use any of these sub pieces to create your perfect dream business, track and record your story, ease your pain, and have the necessary pieces to help your business thrive!

Working on content for the enterprise level of the value add-on core model. Smaller session today. I have some other things that have been promised. As Shannon and I were talking, we decided that adilas has a big appeal because it is so open... there are also a number of problems and challenges because it is so open. It's all part of the game we are playing. Part of the environment and real estate of the adilas application.

Finishing up some content on the BI - business intelligence level for the adilas value add-on core model.

Here is some of the new content, just for fun.

The fourth layer is the BI or business intelligence level. This is where you start seeing trends, patterns, and even identifying possible problems. Often people tend to think of the BI level like a giant dashboard that shows charts, graphs, quick counts and totals, however business intelligence is far more than graphs and charts. In this section we want to discuss what creates business intelligence and why it is so valuable to companies.

The first thing you have to do to get business intelligence is catch and centralize all of the data. This creates your pool of possible information. We call this pool of information transactional data. These individual transactions hold the details for what is happening in every level of your business operations. Everything starts here at this point. Then, similar to a cook with a pot of stew, you have to start boiling things down. The technical term for this is called aggregated data. This produces things like sums, averages, counts, maxes, mins, etc. These aggregates also become part of the available data pool for quick access and usage later on in your reporting.

Once you have your data pool you can start creating business intelligence through a process called "E.T.L". This ETL process is an acronym for extract, transform, and load. That may sound pretty simple but in real life, it is a pretty involved process. Extract means, let's look at the full data pool, decide what pieces are needed, and at what intervals. Then you pull that desired data out of the system. This usually comes from multiple places within the database. At this point, the data is somewhat raw but ready to be used. Next, we need to transform it.

The transform process takes data, which often has unnecessary pieces with it, and trims it down to just the needed pieces. This process is making the data into what you want and may take multiple steps in the transformation. Along the way, the load process involves taking the new pieces or sub products and putting them into a new holding container. For business data, that may be categorizing things by location, by date, by category or sub category. You label things, you place them in known areas within your database, and you pull certain values for certain reports. This is making business intelligence available for use both now and in the future (looking back).

The whole reason that we do this ETL process, and try to automate it, is because viewing transactional data breaks down when there are too many transactional pieces or when you are trying to span too long of a time interval. Automating your collection of business intelligence becomes a continual background process that we do for you as you continue to run your normal operations.

Without getting super technical, we'd like to introduce the rule of 0's here. This is just to help you see why aggregates and the BI level are needed. If you are looking at one piece of something, say an invoice, it's not a big deal. If you are looking at 10 invoices, it's not a big deal. When you start looking at 100 invoices that starts becoming a little bit more of a chore. You can see as you keep adding zeros it becomes harder and harder. If you went to 1,000 invoices that would become a major chore. What if you went to 10 thousand, 100 thousand, millions of invoices? You can get lost in the details and the time it takes to look at each one. Anyway, you can see how aggregated data or business intelligence becomes essential for seeing the patterns, trends, and summary of what is happening in your business.

One of the end goals of this BI level is called digital storytelling, being able to see and know your company's story as it unfolds over time. Imagine if you could see your entire business, almost flowing as if it were on a video screen or a miniature movie of sorts. You could see things as they go up and down and change. If you have questions, you could stop and you could drill in and see all of the underlying transactional data. That is where we are headed. The business intelligence that you could get from this would be amazing. Whether it is graphs, charts, targets, trends, or details, you could quickly see the business data to help you make decisions in running your business.

There could also be some excellent industry specific options here for 3rd party solutions that work with BI technologies. They may specialize in doing data analytics, predictive models, just in time reporting, trending, or other BI technologies. They could harness the transactional data from the adilas core to produce great BI results. Along those same lines, current AI, artificial intelligence or large language models, are becoming an increasingly valuable tool in working with large data sets. Lots of possible options are rising to the surface as technology continues to improve.

Often, companies pay big money and go to great lengths to get this business intelligence. This BI data adds great value for individuals and companies. They may pay for BI in many ways. Some examples could be: paying for extra people to help gather data from different software packages, business consultants, spreadsheet teams, people who do data analytics, and so on. This manual process of extra people and consultants happens over and over again. Companies want to know what is going on, how to plan ahead, and what decisions to make right now that will affect and/or help them in the future. Think of the value of having all of those processes automated and right at your fingertips in real time. That is invaluable and becomes a huge business asset to help your company. The adilas BI level will fill these business intelligence needs. As we continue building, more exciting possibilities will become realities.

Work session with Shannon. Working on the BI (business intelligence) level content. Part of the adilas master plan. We spent time today defining the ETL (extract, transform, and load) process and how that works. We also spent some time on the content for why that is valuable and important. Lastly, we spent some time going over how transactional data begins to break down (too many smaller entries or too big of a time span). Talking about solutions and how we will be helping our clients with the bigger BI master plan.

Small work session with Shannon. We were working on the business intelligence (BI) level of the adilas value add-on core model. That section is kind tricky. Some people think that business intelligence is just graphs and charts. You have to do a lot of boiling things down and refinement and re-refinement in order to get to the real BI level. Going over the process and what it really takes.

This may be somewhat on the side, but I feel like we have to do some teaching and training vs just using buzz words. I feel driven to help with that.

To start out our conversation for today, we re-read the notes from our meeting on 7/1/25. That got us going in the right direction. It is somewhat crazy to see all of the parts and pieces mixing together. All part of the master plan for adilas and what is possible. Good stuff.

Good work session with Shannon. We started out talking about stress and how that effects the brain. See attached for a copy of some notes from a guy by the name of Paul Finnlay (spelling?). He was teaching a class yesterday at church about mental health and coping skills. We were talking about how if your stress levels get too high, your entire frontal lobe of your brain shuts down. You end up falling back into the mid-brain (animal) type behaviors. Anyways, some fun conversations.

We then jumped into working on some new content for the level 4 BI - business intelligence level of the value add-on core model. Most of the session was me showing Shannon why we need this and where normal transactional data starts breaking down. I did a lot of drawing and showing her what we currently have and where it could go. I was having tons of fun and we had some great talks. Here are some of my notes:

- Looking under the covers... how many database queries it really takes to show the correct transactional data with all of it's relationships and one-to-many parts and pieces.

- What does it take to extract that data? What do we do with it to transform it into something usable? How and where do we store the new transformed information?

- How much value BI (business intelligence) is worth. For example: Say you have a company that is using a number of different products to run their entire business. They have data all over the place, in multiple different systems. Say that same company employees 20 people to pull all of the data together and build spreadsheets to show the company financials. These numbers are from a real company, just using them for fun. Say you take 20 people and pay them at least $5,000 a month. That's $100,000 a month. You then take that number times 12 months for a single year. That is $1.2 million, just for your data extract and transform people who are doing your spreadsheets. What would that BI be worth if it was in a single place (adilas database) and you could search and query it as needed vs going to tons of different spreadsheets? It would be worth a ton... :)

- Dealing with the value of BI - people already pay for this - business consulting and data analytics - they go through very painful steps and processes to get it - we could help there.

- Clients want BI stuff - what changes would we need to make and build to get there - fully?

- There are so many things going on... sometimes it feels like the dream is getting lost - we are focusing on surviving vs inventing and thriving.

- What excuses am I leaning on? Ask yourself that question.

- From Disney/Pixar's "A Bug's Life" - The ant "Flik" was an inventor. The other ants just wanted him to help gather food like normal. He kept trying to help. That was both good and bad. Eventually, some of his inventions helped to make things better. Invention can be good! Sometimes it takes a while.

- There is a constant flow between chaos and order - how maintenance plays into this mix - back to talking about stress levels and going into survival modes.

Work session with Shannon. Working on BI level verbiage and content. This is part of the Adilas value add-on core model stuff. We didn't get all the way through it and will have to pick it back up next Tuesday. Making progress.

Working with Shannon. Spent time working on describing the industry specific skin section of the adilas value add-on core model. See below for some of the content that we came up with.

Industry Specific Skins Level - White Labeling

The next, or second, layer above the core is what we call the industry specific skins. Imagine taking the generic adilas business tool, the adilas core, and then building software specifically for a business vertical. The new software package has exactly what they need, looks like what they want, and caters to their specific business practices or processes.

All of the other pieces are hidden and/or behind the scenes. With an industry specific skin, you can toggle on and off almost anything that you want. Change any of the verbiage, language, steps, and even the flow process. It becomes fully custom.

Every business has such diverse needs, wants, and even flow. For example: Say you were a car or trailer dealership. You would be dealing with stock/units (serialized inventory), floorplans, commissions, paperwork, etc. If you were simple retail, you would be dealing with barcodes, touchscreens, tons of different widget inventory, quick counter sales, and different payment options. A service industry may need scheduling, reoccurring billing, and a focus on customer care or support. You get the idea.

Building industry specific skins help us, as a company, cater to the exact needs of those business verticals. This also helps our clients feel like they have industry specific software that was built just for them. The true secret is the powerful underlying core. That's what allows all of this to really take place per business vertical and allow unlimited possibilities.

The white label option deals with a company wanting to brand and sell one or more of these custom industry specific skins. Each white label will, or could, have a completely different brand, feel, or flavor. For example: Say a specific skin for bowling pro shops, ice cream shops, pet grooming, quick retail, health and wellness, hobby shops, etc. Lots of potential! If you want to learn more about our plans for the white label options, see this page that has some adilas investment opportunities. The white label content is number 4 in the last section, ways to invest in adilas.

Working with Shannon. Going over content for the transactional core. Showing that the current core is basically a fully integrated system with all of the pieces working together in harmony. See the content on the adilas value add-on core model page for details. Specifically, look for the section titled "Define The Current Core - Transactional Core Level" (the third accordion section).

Meeting with Shannon and working on content for the adilas value add-on core model. This is somewhat of the master plan and where we are heading. Today we were working on content for defining the core. Here is some of what we came up with... we may still edit some things but it's a start.

New content... - part of the value add-on core

Before defining the current adilas core, we thought that it would be helpful to show what is common or somewhat industry standard as far as matching software to needs.

The current approach that most businesses use is to look around and try to find the best in class pieces of software. Then they try to marry those software pieces together to get a semi-workable system. This commonly ends up being a solution that includes anywhere from 4-10 (or more) different software packages to run their business. Imagine something like this: Best in class inventory tracking, best in class POS (point of sale), best in class ecommerce package, accounting, payroll, timecards, CRM (customer relationship management), project management, scheduling, etc. You get the idea... Does this sound familiar?

This ends up being what is called a "mashup", or mix, of different software packages all trying to be pulled into one workable solution. The pain comes in as each piece dead ends and doesn't fully fit with the other pieces. You end up in somewhat of a time sink as you have to duplicate data or search for data details in or from one software package to the other. Not to mention that you have different accounts, contracts, logins, and are paying for multiple pieces of software.

Inside of adilas, we are demonstrating that it is possible to do all of these critical business functions in a single integrated system. This is what we do at adilas. Imagine being able to do full inventory tracking, fully configurable POS functionality, CRM functionality, scheduling, accounting, payroll, ecommerce, full financials, reporting, exports, and having a virtual paperless office (CMS - content management system). This is just the surface of what is available with adilas, one system, all working together in an integrated solution.

Some of the benefits of having a fully integrated solution are things like: Having everything in one place and it all interconnects (no dead ends). Being able to search and find underlying details of amounts, sums, and counts. Not having to buy all of the other software packages. You are no longer limited to strictly linear processes. You are able to have a virtual three-dimensional (3D) system that allows you to enter data at any level and it will interconnect. Another huge advantage is that you get to use what features you want and don't have to use other features that you don't need. It's all there, if you need or want it.

To describe the adilas transactional core, what already exists, we will start with the word "transactional". This means - details or individual transactions. If you catch every penny in and every penny out, every invoice, every PO, item usage, expenses, deposits, etc., you start getting transactions and data history. This creates multi-relational data stored over time. All of these underlying details and histories become the transactional core. Everyone who uses adilas will need a transactional core. This is what people will purchase as the base model for how they run their business.

If you want more, here is a 50 slide pitch of what we do... have fun... we call this the presentation gallery.

Work session with Shannon. We spent the entire time working on new content for describing the value add-on core model and what that really means. We really tied to explain that each business, that uses adilas, needs a transactional core. That is where you start. That core is where they capture and record all of the daily transactions and subsequent accounting pieces. We then offer upgrades or value add-on's, to that core, as additional layers or levels that help the core product of what we offer.

Work session with Shannon. We were finishing up some content and verbiage for the adilas jellyfish model page (company structure). We were mostly working on the payment and compensation section. Good session and some good conversations. Somewhat off topic, but we also talked about saying yes, saying no, setting boundaries, abusive and positive relationships, and how certain things - if taken too far - actually hurt others around you, unintentionally.

Anyways, I had done some prep work on this section. I had a printed page and half worth of content, and we got it paired down to less than a half a page. Shannon really helps me talk through things and helps keep the content on track and concise.

Working with Shannon. We got in and started working on the content for the adilas jellyfish model (company structure). Our goal was to work on the payment and compensation section. We kept getting pulled off into side tangents. Not fully related, but somewhat related to the topic at hand. We ended up talking about a shift from focusing on the next projects (tick list or features) to more of a person and talent type approach. We have been somewhat focused on following the money or following the dollar.

This shift, from features to people, I would love to see that play out. The current focus has always been on the next project or feature. It seems like it was always something like this... if we could just get such and such done, then we could work on this or that, or our customers wouldn't ask for anything else. Sadly, that is not true. The requests and demands just keep going. We have hundreds and thousands of features... We really need a bomber team!

Recording notes from yesterday. Meeting with Shannon to go over text, verbiage, and content on the adilas master plan stuff. Working on talent and personality types. As we are writing these sections, we are trying to shoot for the ideal, show what is current, and then show where we are heading for our future plans.

Working with Shannon on refining content for the adilas jellyfish model - pages within the adilas lite (fracture) plan. We didn't quite finish everything up but making good progress. Here is the link to that page - https://data0.adilas.biz/lite/jellyfish_model.cfm

Working with Shannon. We did a bunch of editing and read through the investment page for adilas. Trying to make it a final edit so that we can move on. Here is the link to the page. Most of the edits were on the bottom section, dealing with ways to invest in adilas. Towards the end of our time, we were planning on what we will tackle next.

Working with Shannon on verbiage for the adilas investment options page. We were working on the last few options. Just an observation, it is so interesting to see how the process goes for smoothing things out (making good content). You almost have to rough cut it, refine, refine, maybe even give it some time, and then circle back around again. It is fun to be part of the process. Good work session today.

Working with Shannon this morning. We spent the whole time talking about white label options and the five main adilas business entities (main adilas.biz llc, adilas shop, adilas university, adilas marketplace, and the adilas cafe). We were working on new verbiage and content for the investment options page for adilas. Lots of talk about byproducts and how to help service those needs and wants. We also talked about ways of catering to our needs (as humans) and how certain things really make us shine and come alive while other things can drain us and have an emotional cost to them.

We briefly talked about the working genius - a company that helps you know where your working geniuses, working competencies, and working frustrations lie - (WorkingGenius.com). We talked about how things look and behave and how we deal with those things. Talking about pressures, length of time, and demands on our time and energy.

Great session working with Shannon. We spent the whole time working on verbiage and content for the white label options for investors and what that might look like. As part of our meeting, we came up with this nice statement that involves our business functions and what we call our application players. Here is the statement:

"Adilas has the essential business functions and needed pieces to create any digital software system. Your white label mix will become a fully viable and marketable solution. We can help you mix and blend any of these pieces, based on your needs, designs, and input. Let's dream it up and make it!"

Working with Shannon. Spent time writing and reading over our verbiage for the investing in adilas page. We have had multiple sessions working on this page. It has been a good exercise to help us define what we really want. Today we were working on new stuff for investing in adilas lite, sponsors, focused funding, and white label options. It was really fun. Part of the fun today was dreaming about where we want things to go and how that could play out. I'm excited to get things done and get the new stuff live and online. It still may be a few days, but it is coming. Good stuff!

Meeting with Shannon. Reading over verbiage and copy for the ways to invest in adilas. We finished up the section on buying a percentage of the main adilas, llc entity. We then rolled into the section on investing into adilas lite and fracture (new product buildout and deeper product development). Good work session. We will push up the whole page, investing in adilas, once it is ready and done.

Working with Shannon to redefine the investment options page. We created an outline and then started to add content under the different sections. Great work session. We felt like things are coming and playing into the mix better. We felt like some good traction was made today.

Working with Steve over a GoToMeeting session. We added in a new flag option on the advanced PO searches. It checks for still outstanding PO's and disconnects between the main and the sum of the line items. We went through and added some more code to make it happen. We did some testing and cascaded those pieces to other pages. 

We switched gears and talked about investors and what we are looking for in an investor. I took some notes and will work with Shannon to update the correct verbiage on the investment page for purchasing an adilas percentage. Good meeting!

Working with Shannon on the verbiage for the investment options for adilas. trying to really figure out what we are really wanting. We ended up going back and looking at some entries from 5/31/23 to 6/14/23. Busy couple of weeks back when ship A and ship B were going in different directions. It was fun to review some of that stuff and remember why we are trying to get this thing funded correctly.

Meeting and working with Shannon. We spent the whole time trying to define what we want from investors and what they want and what we are willing to give to them. Good session. Eventually, this new verbiage will be on the investment options page for adilas.

Working with Shannon. We were refining the investment opportunities page and the copy and verbiage (text). We were talking about levels of desperation. If you are desperate, you tend to be more open to whatever. If you are more stable, you may be more picky. As Shannon and I were talking, I was saying that I failed over and over again on certain things. She was saying... failing can be reclassified as learning - depends on how you look at it.

Different subject, so many judgements... sometimes we pass judgement so quickly... people do it to us (as a company) and we do it others, both on purpose and subconsciously. The other thing that we were talking about was finishing things up. It seems like the final 10% of every project seems to be really tough.

Quick barcode fix for Sean. He sent me an email last night asking us to open things up a bit more. I ended up making a small change and opened up the size limit from 15 characters (on the old barcode generator page) to 50 characters (what the database will actually hold).

Working with Shannon. We had a good session and spent some time going over the adilas investment options page. We redid some of the sections with some changes to help with flow and wording. She is really good at helping me come up with good content.

These are some random notes that I had written down on 3/26/25. Just recording them.

- We may want to setup a webinar to help with some demos. Basically, demo once, use many (have multiple parties be on the meeting). It could be pretty cool! I'd like to explore some options there. Maybe even a set reoccurring webinar or something like that. Shannon and I used to do that back in 2014. It's been a while.

- Different subject, as we get new member owners (co-owners) in the adilas, llc (MMLLC - multi member LLC) entity, we may want to schedule some general meetings. Put those meetings on the calendar and then let all member (co-owners) know about those meetings.

- Small note about buying and selling shares (percentages) of adilas. Create a rule that deals with ability to sell based on permission from holders who are 20% or higher (something like that). Maybe look into this and setup some checks and balances. We don't want to create a monopoly within our company. It might be cool if there is a standard way of doing things but also an option to do it differently, based on agreed upon rules and processes. Just some thoughts.

Working with Shannon. Spent the whole session going over the efficiency and productivity section. Tons of new ideas and notes (brainstorming session). We are working on content for the presentation gallery. See attached for our new notes. The efficiency and productivity section is section 3 in the document.

Going over some of the AI results for the desired outcomes section (we did this last week). We started out in the achieve your dreams section. We had numerous conversation junctions about all kinds of topics... They are all related and deal with systems (generally speaking or systems thinking). We talked a little bit about MCP's - model context protocol (like hands and feet for AI models - whereas AI by itself is just like a big brain). We talked about how the web hyperlink really opened up the worldwide web and allowed for resources to be connected based on links, clicks, and buttons.

According to what we are seeing, it looks like the MCP's (model context protocol) could be similar and allow vast LLM (large language models - aka AI models) to be interconnected. Similar to the hyperlink but on a bigger model or database or API driven data level. It could be big. Anyways, small talks about data, systems, and how everything needs to work together.

As we were talking, we got into world building and how getting into the know (next level in our outline) plays in. We talked a ton about the value of the concepts and how everyone somewhat needs to flow through that area. Regardless of your tooling and code set, everyone tends to follow some of the same underlying concepts and principles. That is really cool. We have spent a ton of time looking into and pioneering some of those concepts. That makes it kinda fun. We used the teaching photo gallery and talked about a bunch of the concepts and images in the gallery.

As we keep building and pushing on things, it seems like the flavor starts to come out (over time). Shannon was saying, it seems slow at the start and then it starts to take on a flavor of its own and starts to speed up. Another fun topic of the day was - why we keep and shoot for ideals, yet we know that things get crazy and most people aren't at or can't hit the perfect ideals. Lots of good fun conversations about that and other life lessons and topics.

See attached for our working document. Still in brainstorming mode and we've only worked on the first 2 out of 12 main desired outcome topics. More to come later, next session.

Working with Shannon on refining sub categories for the desired outcomes of the presentation gallery. We did some prep work, ran things through AI, and then read through those notes. We added a bunch of our own notes and will circle back around next week to keep working on it. We are somewhere between 30-40% done (based off of what AI gave us back). Still quite a bit yet to do and finish up. We really want to put our own flavor on it.

Working with Shannon. Boiling down the main headings and going over options and stacking for the desired outcomes section of the presentation gallery. We got a pretty good list of the top 12 main topics for the desired outcomes. Shannon attached the working document. Here is a quick list.

DESIRED OUTCOMES

1 - Achieving Your Dreams
2 - Be In The Know
3 - Efficiency & Productivity
4 - Save Money & Make Money
5 - Organize & Manage Your Data
6 - Expand Your Possibilities
7 - Customization & Flexibility
8 - Innovation & Pioneering
9 - Ongoing Growth & Relationships
10 - World Building - Beyond the Acronyms
11 - Training & Resources
12 - Got Questions?

Anyways, those will most likely be our main 12 points under the desired outcomes section. Currently, the section that we are going to be redoing is called "Attributes". Our goal is to change it out with the above topics and then add more subs under each of the above topics or main sections.

Quick phone call with Shannon. She is busy today. We will pick it up again next week. Recording notes. Also spent a little bit of time doing some light research. Lots of good stuff.

Here were a couple of fun entries that I enjoyed reading about:

Adilas - What brings value? - See element of time # 8904

Game changer - Adilas as a video recorder -  See element of time # 8095

Being desperate and turning to God with real intent. That can be really good. Talking with Shannon about life and what not. Stories about people and relationships, some of those are timeless. We were talking about the value of the story behind things. Going over categories for the desired outcomes section of the presentation gallery. Brainstorming and talking about options.

Working with Shannon on some planning. I made a document last night and used some AI to help me organize it. We then took some of Shannon's notes and ran them through AI. We filtered it down and then did some more brainstorming. At the end, we ran that through AI as well. See attached for our results. Our plan for next week is to go over the results and boil things down again and again. We are making progress. Kinda fun to use AI stuff as well.

Quick chat with Wayne about queueing up server-side processing. Talking about a quick need for simple ecommerce. This (simple ecommerce) seems to be a reoccurring theme.

Switched over to working with Shannon. Working on the formatting of presentation gallery. We spent some time talking about the attributes and results - showing some of the cool things that people are doing with adilas. Marketing, showcasing, samples, & mixing different kinds of results. We really want to cover the who, what, when, where, why, how, how many, etc. - all in the presentation gallery.

Back to an original thought, about mixing business functions, application players, and core concepts to get some cool results or desired outcomes (leaning this way - changing the attributes section to be called desired outcomes). Design your own systems. Help people... that's what we do. We have a ton to offer, and we keep building and refining it every day. This change, from attributes to desired outcomes, may be a little gift (comment from Shannon).

Meeting with Shannon. Talking about being overwhelmed and how to manage that. She recommended that doing some exercising of self-compassion can really help. Often, we beat ourselves up, quite a bit. She also likes to think, I'm not alone, we all have to go through this. Talking about life and lessons being learned, as we go.

For our main work session, we went over the bullet points on both the business functions and the core concepts, in the presentation gallery. Trying to make sure that we are pitching and selling what we really have (sales stuff - prep work).

Emails, light tech support, and meeting with Shannon. Also working with Wayne (briefly) and looking over some automatic email code. He jumped on the GoToMeeting session with Shannon and I for a bit. Once we were done, Shannon and I went back to working on things. We made a plan for Thursday. Light tech support and changing some settings for Suzi.

Light plan for working on the presentation gallery. We have 4 main topics, about 50 slides (pages), and we want to work on each section, one thing at a time to make sure that the site seems cohesive and works as a group.

Presentation Gallery
link - https://news.adilas.biz/sales-gallery/adilas-advert-index.html

Business Functions
- Solid bullets - Make sure that the bullet points are good and solid
- Top Level Modals - Make sure that every page has a top level popup modal description
- Sub Level Modals - When ready, make sure that each bullet point has its own popup modal description and images (or videos)
- Images and Refine - Go back through things and make it look really nice, tight, and fine-tooth combing of the data and content.

Application Players
- Solid bullets - See above
- Top Level Modals
- Sub Level Modals
- Images and Refine

Attributes
- Solid bullets - See above
- Top Level Modals
- Sub Level Modals
- Images and Refine

Core Concepts
- Solid bullets - See above
- Top Level Modals
- Sub Level Modals
- Images and Refine

Starting on Thursday we want to go back through each one at the top level. Review the bullets we have done (business functions and core concepts) and look to what needs to happen for the Attributes and Application Players.

Work session with Hamid. He finished up the 12 business functions and the see more features modals and bulleted lists. See below for a list of link (see the section titled see more features per page). We also checked and pushed up a bunch of the smaller PDF's that show the business functions in a printable format. Good work session.

Sales, Inventory & POS System
Customer Relationship Management (CRM)
Calendaring & Scheduling
eCommerce
Accounting & Backend Office
Expense Tracking
Payroll & Time Cards
Reports & Histories
Business Intelligence (BI)
Data Relationships
Content Management System (CMS)
Big Data

Going forward, he is going to be working on some training in CSS and JavaScript until Shannon and I can get him some new content for the presentation gallery site.

Meeting with Shannon. Doing some light catch-up. It has been a while since I have worked with Shannon. Talking about patience and waiting on the Lord (His timing). I reported on my trip up to Canada and how things went up there. We talked about working on the presentation gallery, chipping away, at that big project. We talked about other content needs and how we can push the ball forward. I would like Shannon's help on plans, outlines, and helping me to make new content. She has been great on those levels. Super excited to get back to work with her. We also talked about letting go and not trying to micro control everything to a super tight level (obsessed with details or perfectionism). Let's just get it out there.

Work session with Abby and Shannon. We worked on two pages in the presentation gallery this morning. We worked on some sub pop-ups (modals) for the maintenance page and some new information on the vision and future page. Our plans are to circle back around and fill in more plans for the vision and future stuff. That will be fun. Anyways, that's where we are headed.

Phone call with Steve. We covered a lot of topics. We talked about people, ideas, plans, and where we are heading. We talked about payables, who we owe, who owes us, funding, revenue, etc. We were throwing ideas back and forth. I pitched a few ideas to Steve that Shannon and I were talking about earlier this morning (see EOT # 11405).

We may end up trying some things including investing in peoples (strategic personalities and skills) and also allowing our developers to do some side work or subcontract work (to keep them going). We tried bringing them fully under the adilas umbrella but that is a huge financial burden. They all used to be independent contractors. We are thinking of going back (in some ways) to that type of model. It's that or we have to let some of them go.

We talked about sales, projects, features, education, marketing, communications, etc. We may look at trying to get some more on the SBA loan and use it all (ish) to fund people filling specific roles. The list of projects is unending... we may have to leave that as is right now. That ball will keep rolling. In the mean time, we need to let the developers pick up the paid client work and setup some rules to help us all play along.

Working with Shannon. Showing her the new deli style barcode stuff. Small demo. Talking about debt and plans. That lead to a discussion on a number of topics. Here are some random notes... (not all tied together but what we were talking about):

- What if we set limits on how much we do for a new client. We can still invest in them but there are limits. Finding a good middle ground. We get in trouble with "it should" (expectations). We can't really fully stop this - meaning investing in our clients.

- Coding actually takes a lot of both time and money. Awareness is a great place to start.

- It might be hard for the builders to be the sellers (all we see is what needs to be done - meaning the developers). Possible disconnects.

- Still do what we do but put some boundaries on it. Say, spend $10K and show them what we are doing for that vs just an open ticket.

- Setting up checkpoints... to help us and the clients to move along. Healthier steps vs just plunging in.

- We have done a great job with what we have to work with.

- We were talking about different personalities and roles.

- Some transitions are coming. Along those lines, transitions take time.

- Our guys have been very willing to try to play into different roles (code vs sales).

- Sometimes there are painful talks and meetings.

- Some of our solutions come from our experiences... that is both good and bad.

- Our greatest weaknesses are overused strengths. There is more overlap in our strengths and weaknesses than we know. Sometimes we get so good at things we don't mix and blend, we just push on what we are good at. Flipsides - gains and losses. Patterns and phases.

- We totally switched gears and talked about plugging money into people vs code or sales. We've tried those other things before. Just a thought, maybe focus on people and key positions (stable pieces or needed pieces of the puzzle).

- Back to limits and checkpoints - communication and expectations and requirements.

- Talking about the working genius and how each of us plays into that mix.

- Hiring to our needs vs forcing in people who are already on the team.

- In some ways, okay, a lot of ways, we like the random... Random vs super strict order and organization. We need someone or something that will allow for some randomness and still provide structure. Setting up light boundaries. We have created some awesome things from the chaos... We can also see that full chaos will drive people insane.

- This is a question - Are we helpable? - Are we doing things a different way (like a welfare situation - helping people and they just go back to what they were doing). We don't want someone to come in and put us in a straitjacket... What can we do to help ourselves to create new mixed processes. We might need to find good matches (personalities and traits and skills and costs).

- If we invested in people, we would have to help them define their roles and help them in their pieces and processes. It could help us develop our underlying structure. That would be awesome!

Working with Shannon and Abby on the presentation gallery. Shannon had a few new definitions and Abby showed us a graphic that she is working on for the 12 main player groups. Pretty short meeting today. We will hit it again next Tuesday. Shannon is getting close to having her baby (any time).

Meeting with Shannon and Abby. Touching base. Abby had some new popup modal descriptions for the core concept on the maintenance page. We did those new descriptions and then jumped off to work independently. After that, I did some emails and small to do list stuff.

Meeting with Abby and Shannon. Talking about removing friction out of processes and sub processes. Constant work of refinement. We were commenting on how we are trending and creating new settings so that people can configure their own tools that they use. They are not required, but if used, they may be customized. I gave them a small demo on the deli style barcodes and how that works.

We then switched over and started doing a small work session on verbiage and new icons for the business functions in the presentation gallery.

Quick meeting with Shannon. We touched base and then jumped off to work on our own projects. We will hit it again on Thursday. Emails and paying bills. Phone call with Bryan. Quick code merge for Cory - restoring quotes to cart and helping flip the invoice type. Yesterday was a holiday. Today felt like a Monday, even though it was a Tuesday. Random odds and ends.

Meeting with Shannon. Abby joined us part way through. We were talking about risks and costs and how they correlate and run together. I can't tell you how many times we see repeating patterns. What do you do about that? Great question. We were talking about personalities and strengths and weaknesses. Question - what you value? What you end up getting out of a relationship and/or a business is somewhat of a reflection of you and what and who you are. I really enjoy some of our talks. It's therapeutic for me and hopefully for the girls as well.

Setting up a new schedule for some meeting times. We are going to be changing it up a bit in September. We got into a small work session. Shannon has some new text and verbiage for new modal messages and Abby had a bunch of new icons to add to the pages. Pushed up the new changes.

Meeting with Shannon. Talking about personalities and styles and some of the variables that go along with that. People can be very interesting and yet also challenging at times. After the meeting with Shannon, we decided to break off and work on our own. I jumped into emails and recording notes. Quick phone call with Sean to explain the new functionality on auto open next sub settings for sub inventory.

Quick meeting with Shannon and Abby. We talked about where we are heading and decided to break off and do some work on our own. I mentioned to them about the need for the presentation gallery, if we ended up having a bigger team. Our goal would be to share the core concepts and the vision of where we are heading. We also spent a little bit of time going over the four phases of team building and how each new team goes through these phases. They are: forming, storming, norming, and performing.

Meeting with Abby and Shannon. Went over some client meetings (from the past couple of days) and what is being requested and learned. Good review. Just being silly, our clients are almost saying "I want the Death Star for 100/month" (Star Wars reference).  We then rolled into a good work session on the presentation gallery pages, verbiage, and bullet points.

Meeting with Shannon and Abby. Checking in and making some plans. We are all going to do our own thing today and then meet up again on Thursday for a work session. Shannon is working on verbiage for modal popups. Abby is going over some graphic tutorials and I'm splitting up a huge 50 page document into smaller pieces. I also downloaded the Affinity Designer tool and did a little bit of playing with it. Ended up playing with the graphics tool for the rest of the time.

Work session with Shannon. We did new bullet points for the last three business functions (data relationships, content management systems - CMS, and big data). Then did some prep work on graphics and breaking a huge document into smaller pdf docs. Each of the business function slides (12 of them) all have a line saying see more features. Trying to prep so that we can fill in that gap with actual real content and such.

Working with Shannon. We spent our session working on the business functions for the presentation gallery. We won't push up the new changes until we get all of the sections done. We still have a few more left. Today we worked on the calendar & scheduling, ecommerce, accounting & backend options, expense tracking, payroll & timecards, reports & histories, and business intelligence (BI). As we were working, we were talking about the importance of boiling things down. That sounds so easy. It's not that easy but it is fun, however, it takes some major time and effort.

Working with Shannon. Going over new developments and some reminders. When we talk with other people, it sometimes drives home some of the concepts that we are trying to catch and use in our development and marketing. That is exciting to see validation and people asking for the same things that we are working on. Shannon sent me a 4-page document and then she bailed out to work on the other business functions that still needed some help. Just for fun, check the media/content for Shannon's new 5-page document with the other 3 business functions finished. See attached.

I added in a new graphic that Abby made dealing with how adilas bridges the gap between operations and accounting (see attached). I then switched over to working on the slides for the 12 business functions in the presentation gallery. With the information that I got from Shannon, I started doing some coding for the other 9 out of 12 that have content. Only got through two of them (sales & inventory and CRM - customer relationship management). I'll push them up as a group, when I get the other ones done. Otherwise, it will look a little weird or different (layouts and style).

Quick meeting with Shannon and Abby. We decided to just do a work session today. We split up and each worked on different projects. I added a new image of different worlds to the photo gallery page. Abby made the new graphic and it has some fun colors. Ended up spending an hour or so working on the photo and teaching gallery. Replaced a few images and took some new screenshots. See attached.

Meeting with Shannon. Going over some of the latest happenings. Doing some catching up and deciding that today would be a good work session day (individually). We jumped off the meeting to keep working on our sub projects. Shannon is working on the business functions section of the presentation gallery (new bullet points). She is basing her efforts off of a 50-page document that we did awhile back - presentation gallery - outline.

Recording notes from yesterday (7/15/24).

Got a call from Abby and we jumped on the GoToMeeting session. Working with Abby to show her some concepts of object carrying their own luggage (their own data, relationships, sub details, and history). Lots of drawings and demos. She showed me a new graphic that she was working on of some worlds and such.

Meeting with Shannon. Talking about happenings (catching up on things) and making some plans.

Got a phone call from Wayne. We were talking about what we know dealing with the hack attempts on data 0. One of our plans is going to be moving to a new version of ColdFusion (2023). Trying to close every door possible. Wayne has some outbound logs from the server that we need to review. We may need to get a lawyer involved, if needed. I told Wayne that I would give Steve a call and figure out a plan on that side. We talked about maintenance and how we have to put out fires and grease the squeaky wheels. Some of the other stuff stays undone. There is too much to keep it all up. All part of the game. We also noted that Hostek (the hosting company) is being a little slower on their responses. Looking ahead, we know that we need to fix and work on some labels stuff, need to fix older barcode and QR code libraries, Wayne has a new solution in mind, replace the older BBQ and iText (java libraries). When ready, we will be pulling reports with dates/times, corps, customers that may have been affected by the hack attempt on the data 0 server.

Phone call with Steve. Going over hack attempts and course of action. Steve was telling me about hacks on huge companies like Netflix, Target, Apple, etc - everybody is being compromised. Dealing with credit card transactions, we are heading more and more towards a tokenization approach of data transmissions vs real data being passed back and forth. Steve said that a bank person (person in charge of fraud at a bank he goes to) said that they, the bank, re-issue 90-150 new credit cards a month, due to fraud. This was a small local bank. It's happening all over the place (hack attempts). We will work with Wayne and see what the window of time is that is in question. It's only on data 0. Our plan is to only notify those people/clients that may have been compromised (data stuff). I will get with Shari O. and get her involved to help send a note out. I'm also supposed to get some info from Wayne (tech stuff) about what we know and what that window looks like.

For me - Shannon and I were talking about a book called "Rhinoceros Success" by Scott Alexander. Taking small bits of wisdom from the rhino book - keep charging - damn the torpedoes! As a side note, one of the chapters in the book is called "Damn The Torpedoes" meaning that people are going to be shooting torpedoes at you all the time. Grow some thick skin and keep charging!

Work session with Shannon and Abby. I showed them the new touchscreen quantity modifier piece (new code for the mini scan cart). We worked on the attributes section inside the presentation gallery. Shannon bailed out and just Abby and I finished out the session. We added worked on the data over time page - new icons and sub text.

At the end, we, Abby and I, stopped our timecards and spent some time talking about life and the journey that we are all on. We talked about being in the present and finding success along the journey. We talked about dreams and ways that we either want to help others or ways that we are being helped. Fun stuff. See attached for a cute Family Circus about gaining small victories. Good stuff.

Meeting with Shannon and Abby. Made a number of changes on the presentation gallery - working on the core concepts. We also modified the main sub menu for navigation within the presentation. Left off copying and pasting sub menus.

Meeting with Shannon and Abby. We did some new icons, new sub text, and some new bullet points on the presentation gallery pages. We worked on the following pages in the core concepts: systems, vision & future, maintenance, and data over time.

Meeting with Shannon. Going over current projects and challenges (helping people, maintenance, security, etc.). Easy to see solutions, tricky to solve... tons of requests, minimal time, lots of needs, helping with training and planning. Overcoming barriers and implementing solutions really takes a lot of time and effort. Shannon and I worked on the permissions and settings page in the presentation gallery today.

Meeting with Shannon and Abby. Going over what it takes to code things... small overview (5 languages - HTML, CSS, JavaScript, Adobe ColdFusion, and SQL for database interactions). Shannon bailed out to do some work on her own. Abby and I spent the rest of the time doing sub text and new icons in the presentation gallery. We made changes on 10 different pages in the presentation gallery. Pushed up files.

General stuff. 20 minute phone call with Bryan going over direction on marking parts as main items for auto numbering and grouping. That is his current project. 5 minute call with Eric to talk about USAePay transactions and automated payments. Printing out a check for Shannon. See EOT # 11048 in the shop.

Meeting with Shannon and Abby. We did some work on the icons on some pages. Working on goals, cause and effects, and accountability pages. These are all pages on the presentation gallery.

Meeting with Shannon and Abby. We spent the first hour or so going over where we are at and how we got there. It's helping the girls get some perspective on the timelines and history of what has already gone on and where we want to go. We talked about rejecting certain business principles and how those actions trickle down and affects the team. We also talked about seeing patterns and how to achieve an MVP (minimal viable product, plan, or person).

We then jumped into a work session and spent the rest of the time working on the presentation gallery. We worked on the relationships page and challenges (trouble or problems) page. We also did some icon work.

Meeting with Shannon and Abby. Catching up and showing each other what we are working on. Abby was showing us some of her graphic ideas and sketches. She is hoping to use images to really show how each thing (concept) relates to real life. She had a number of images to show us. I'd like to get copies of them from her. She is catching the vision.

Shannon is working on summing things up (summaries) and working on flow and flavor for the presentation gallery. We then jumped into a small work session and fixed a couple of pages based off of Shannon's notes. We were working on core concepts and did some work on characters and relationships pages.

Working with Shannon and Abby. Review of where everybody is at on their individual projects. Setting up new meeting times for June. Started working on the presentation gallery. It turned into some training on some of the core concepts. We did push up a bunch of new files and changes (click to view).

Meeting with Shannon and Abby. Talking about alignment and how much that helps the whole process go smoother. Work session on the presentation gallery. We added a new graphic of Adi (the dog) daydreaming about world building. We started into the record your story page in the core concepts. We were prepping things and plan on making small little modal popups for each section. When it's done, it should look really good. That's the plan.

Working with Abby and Shannon. Abby was showing us some progress on her adilas history document. Small demo on what we are doing (new changes to the system). Light graphic demo and talking about graphic programs, tools, work flow, and layers. We did a small training session. After that, we did some more work on the presentation gallery - core concepts homepage. Lots of graphic type training today. Fun!

See attached for some of Shannon's notes.

Working with Shannon and Abby. Reworking the presentation gallery based off of some of our notes. Small work session. I got some good feedback and we were able to work on page layouts. Both Abby and Shannon were helping me and providing opinions as we made changes. It was fun. See attached for some small screenshots.

Meeting with Shannon and Abby. Small demo of where are at with the new cart stuff. We even logged in and looked around Suzi's demo site (super cool with all of the buttons). Good stuff. After that, Shannon was presenting on some of her research. We made some plans for next week. Next, Abby was showing us some of her progress on a history of adilas document. We talked about desktop publishing, typography, and making things consistent across a document or a project. I gave her an assignment to checkout some topics and then do a new version. The text is fine, the graphics and feel just need a little bit of help.

Working with Shannon. Small demo of where we are at on the cart and the line item grouping. Flipped over to Shannon sharing her progress on the presentation gallery. Summing up content and making review notes. Talking about the need for organized good content. See attached for some of Shannon's notes.

Working on saving the new line item level sorting and allowing edits to the sort numbers as needed.

Meeting with Suzi, Steve, Bryan and doing a small demo. Got a little bit of feedback and a few requests on changes that they need and want. It's looking good, just needs a little bit more and then to get it live. After the demo with Suzi, I talked with Steve a bit about some other things that are coming down the pipeline. After the meeting, I talked with Bryan and we did some light planning.

Small side notes...

Wish list stuff. Bryan had a request to get white papers on some of our accounting and how it all works. He has a person who wanted to read up on stuff. Basically, a request for documents and content. That's awesome. I'll try to work with Shannon to get some of that stuff going and done.

On the mini scan cart, we would like to add options for printable notes, non-printing notes, customer PO's, due dates, etc. All of that stuff already exists on the classic cart but not currently on the mini scan cart. We want to be able to change the cart type, the cart date, the salesperson(s), etc. Normal main cart edits.

Request from Suzi, if you click on start cart and the cart already exists... maybe just go to the view cart vs showing an error. not sure?

Meeting with Shannon and Abby. Showed them where we are at and making more plans. Next week we will do the full meeting with Shannon going first and then Abby after that. Both are going to keep harvesting resources and helping to get them organized. I did a bunch of drawings and explained some of what we are doing and planning. They both seemed really excited.