Good phone call with Andrew. After the phone call, he sent me an email with some good stuff in it. I also sent him an email with a couple of links about where we are heading.

These are the links that I sent him...

master plans going forward... https://data0.adilas.biz/lite/

the presentation gallery... https://news.adilas.biz/sales-gallery/adilas-advert-index.html

investment opportunities... https://data0.adilas.biz/lite/adilas_investment_opportunities.cfm

Here are a few of my notes from the phone call.

- Andrew just jumped into it. I got some of his full life story, right off the bat. We even talked about some recovery stuff and some tough spots.

- He has experience working with POS systems, retail, restaurant, hotel, frozen yogurt, franchising, beverages, etc. Pretty diverse.

- He likes to bring value where he can, in any way.

- He has some psychology training and loves people.

- He shared some stories about alcohol, drugs, ADHD, and God given gifts. Fun conversation.

- He was talking about his mission in life and how he wants to help people.

- Seems to be a big thinker. When asked, he said, "I don't live in problems - I figure out solutions and move on."

- He said that he likes to study.

- Create awareness and access - make it affordable.

- Lots of time learning AI - like ridiculous amounts of time...

- Building tools for himself, no code experience, able to verbalize what he sees.

- Trying to match up the right places with the right people - protecting people that he cares about.

- Controlling chaos and not getting stressed out - plans on it being crazy and when it is, he's already there... then just start bringing it back down until it is in control.

- Thinking about how he thinks and learning about himself or learning about yourself.

- He is always talking to vendors and knows how to talk and speak their language.

- Quick at catching the idea and then being able to virtually spitball ideas, based on what he knows.

- Being strategic with the bells and whistles.

- Building websites - a way to get ideas out of his head - almost mini presentations, but clickable, with some light content and concepts. Quick brain dumps using AI to help build the websites.

- There is some magic in seeing things visually. He just talks to ChatGPT and does a lot of copy and pasting things into a site builder app.

- He shared a couple of websites with me. One is called Logics420, another is called GCBuddy (general contractor buddy), and a small adilas demo site. He likes to build things, tinker, and then refine as he goes.

- If he can see it in his head, he tries to verbalize it, and then make it into something.

- Give lots of free feedback.

- Towards the end of the call, we were talking about adilas, AI, bots, and how to get that all put together. Fun conversation. He was saying something that I thought was really cool. Instead of having one bot that knew everything. He was saying, what about a bot per section or even per page, then connecting those bots together. Creative idea and I could see how it could help train the bots, just what was needed and nothing else. This may not be the final idea, but I thought that it was worth recording.

- Target the medium sized industries.

- He highly recommended that we, the adilas team, focus on the Grok AI integration. Steve has been heading that up, so far. I know that he wants help, we just get pulled off on other pieces or to different projects. Lots of moving parts and pieces.

- Anyways, great phone call. I enjoyed it and scribbled down a number of post-it notes, while we were talking and chatting. We'll talk again soon, I imagine.

Phone call with Josh. He wants some help doing developer work for potential clients. They, Josh, Cory, Steve, and Eric have been doing some fun projects. Lots of look and feel, email campaigns, and new ecommerce skins. He has some potential clients lined up, just needs to fix certain things. He was asking me where I'm at with things. I'm off the side of the bus (not with everybody else). He wants me to work with Steve and the crew on development projects that need to be done. I'm trying to do some planning and working with ChatGPT (AI) to help line out the master plan stuff. We have never had that, meaning a master plan. I'm not trying to get it, the master plan, too detailed, but we need it. I feel that it is very important. We will always have more projects and development work. To me, it's just another checkbox and/or request. We have tons of those, meaning checkboxes, done and pushed out. Just for fun, here is a link to a 50-page document, just with features inside of adilas.

It's not just planning, I'm circling back around, finishing things up, reinforcing the foundation, and refining things. I'm trying to simplify things, make it easier to understand, explore new avenues, use AI to help us get rid of the rub and/or friction. Tons of things. In sales we talk about features, advantages, and benefits. We have the feature part down... We need to circle back around and make sure that we can show the advantages and the benefits. Some of that is look and feel and some of that is flow and simplicity. Just as a sample, here is an element of time entry that shows some of what we are doing and how we can harvest these AI conversations to help show the simplicity of what we are really trying to do. See EOT # 12793 in the shop. This entry has four new documents that are super easy to read, yet tell a huge amount of what we do and offer. We are working on graphics, help files, documentation, etc. We tend to go so quickly, that we don't put the finish on it.

One of the biggest things that people complain about is what it looks like (look and feel of the UI). We have great tech and functionality. We need to circle around and put that finish on our product that people are looking for. I love it, and I totally see it. There is nothing wrong with what he, Josh, is asking. I also know that it takes major resources to do all of that. I really want to see if we can get some investors to help us with some gas money, help us along the path. We have put every extra cent into this project that we could and/or can. That is awesome, but it is also taxing.

Josh recommended that I call Steve and see what he needs help with. I just know if I do that, I'm back in the mix of going a million miles an hour without a plan. We joke about it, but there is some reality to the situation, we are hanging on the car or train as it is going down the road and/or train tracks. We are working on it while it is going, making corners, going up/down hills, etc. In real life, the plan is - just follow the money, but then it never ends and you don't know where you are going. It starts getting complicated. Everything has to keep going and connect to tell the story. I really feel like me not being on the train is important right now. I don't know the timing of everything. We'll get it all figured out.

After we got done talking, it took me a couple of hours to get back on level ground. I think that I have some mental anxiety about where things are at right now and where things are going. I've been in this battle (the adilas project) for 20+ years. I've been burned out and reanimated a number of times. It's a repeating cycle. It has been pretty stressful. I really want to see it succeed, but the current demands are saying, jump right back in at full speed. I need to be on the outside right now, if for nothing else, for my mental wellbeing. I'm working on other parts of the system. There will be great ROI (return on investment) of what I am doing, it just may not be super visible right now. I know that it is going to help.

Back working with ChatGPT on the sixth layer of the value add-on core. Adding in some references to compasses and GPS cores. Pushing on concepts to help explain things and processes. Mixing inputs, wants and desires, tools, funnels, and outputs. See attached for a PDF version of the chat session. The actual chat session will be listed below.

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

Quick phone call with Hamid. He jumped on the GoToMeeting session, but Bryan and I were still on the meeting. I gave him a call, and he said that he is working on the play at the wall website for adilas API socket stuff. He said that he is working with ChatGPT to get some ideas and how to make it both fun and informative (small pun off of "play" at the wall).

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 Abby. She is working on some new graphics for the GPS core and adilas value add-on core models. See attached for a few of the new images. She also gave me a number of super cool simplified docs (mini versions from my prior ChatGPT sessions). I've been going so fast, I haven't taken time to harvest anything. She totally inspired me to slow down and harvest some of what we are learning. Great and easy to read stuff. Along with those documents, she also said that she had some mini screenshots from other chat sessions that she thought were cool. She sent me 36 mini screenshots of key pieces in the chat sessions. That was awesome. I'm so glad that someone is reading them and also gathering up little tidbits of goodness. I love it.

See attached for some of the little gems and documents.

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.

Emails and then working on help files, refining content, and recording notes. Ended up spending the whole afternoon looking into the adilas interactive map layout and where it can go from here. Multi-hour session working with ChatGPT on the adilas interactive map. I fed in help files, older visuals, and newer visuals of where we are planning to go. Super fun session.

Here is the chat session with ChatGPT on the interactive map. The first part of the session was done months back. The rest of it was all done on 4/2/26. Towards the end, we started working on some code to help or hand off to other developers. The lead-up to that, before the code, is the gem part of the conversation. Good stuff.

https://chatgpt.com/share/69d1ebb7-0afc-8326-8ba7-9e96a351f816

See attached for a PDF version, if you would rather have it that way. There are also a small interactive map wireframe and some images to go along with this entry. See attached.

Recording notes from Thursday. Asking ChatGPT how to do more effective branching and knowledge sharing. See attached for a PDF copy of the chat results. This may not be super important for the full adilas story, but it helps me get some ideas and direction on how to link things together. Here is the full chat link, if needed:

https://chatgpt.com/share/69c1afc8-bd60-8007-b1b1-e0fc774ff9be - chat branching and sharing help

Working with Hamid. Showing him what I am doing with AI and how the flow goes. We started a new chat session with ChatGPT. Hamid and I worked on it together for the first two hours. He then had to leave. I then finished it up. This was a wonderful session going over the 3D data assembly line and how it ties into world building. Lots of great explanations, discovery stuff, and explaining "the gap" between operations and accounting. See attached for numerous resources. The full chat log, with ChatGPT will be listed below. This was an awesome session.

https://chatgpt.com/share/69bcdbd3-9560-8007-ad64-15d36d272a43

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

Training session with Abby. We were going over a number of the recent chat sessions with ChatGPT. She has been reading them to get ideas for graphics. I was drawing all over the screen, explaining things and how they work together. Spent some time working on the adilas formula and then into flex grid tie-ins and how everything works. I bounced into a few sites to show her how things play through in real life vs just talking theory. Good session.

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.

Working on a master menu outline. Printing out a number of pages of existing menus from different places. I want to combine them and make a better overall picture of adilas and what we have and what we offer. Also, including some of the why and how. After that, I went in and did a small session with ChatGPT to help get some ideas and help with stripping out some existing menu items from HTML into simple text. It also gave me some other good ideas.

Here is the chat session log with ChatGPT: https://chatgpt.com/share/69b8cb40-042c-8007-bd59-9631c92d2137

Emails and recording notes from 3/12/26 to 3/13/26.

Going through tons of emails and doing some follow-ups. I had sent an email to Abby, my daughter about the SWOT analysis that I was working on with ChatGPT. She sent me back an email with a couple of small highlights pulled out. Here is part of her response.

Adilas is really super cool and people just have to be able to see how much it's capable of! I think paired with Adi as the AI agent for navigation and all the plans for the future, Adilas is going amazing places. It's fun to see the ten year possible plan, and I learned a lot from reading this. I like how it says, "Adilas is a customizable engine for running and adapting business operations." and "Adilas turns operational data into actionable business intelligence." I also loved that it says, "Because Adilas captures operational and financial transactions across many areas of business activity, it naturally creates a rich dataset that can support analytics and decision-making." The final documents the AI came up with are stellar. Pretty cool! I agree that creating Adilas is much more of engineering a system than just writing software. I also appreciate that it was able to simplify the time line so much to just 2001 — Custom operations system, 2003–2005 — Operational workflow tools, 2006 — Core Adilas concepts formed, 2008 — Adilas LLC created, 2010–2024 — Platform expansion across industries, and Future — Next-generation platform architecture (Fracture).

If the original document or chat session is needed, here is the link for that. As a note, it is kinda long, but some good stuff there. https://chatgpt.com/share/69a9d788-a288-8007-949a-58d1ed5ccde2

This entry started on 3/12/26. Since then, I have added some other PDF's and chat sessions. The original goal was to start creating an outline of what we wanted to explore with ChatGPT. This note was added on 4/11/26. I'm going to use this element of time to help me record some of the other chat sessions.

Back on 3/12/26...

Working with AI on some planning for adilas products and roadmaps.

Started out doing a summary of the SWOT analysis. See entry below.
https://chatgpt.com/share/69b32c9b-a8fc-8007-bb28-265499367aaf - summary chat session - future direction and plans

The whole rest of the afternoon and evening were spent with ChatGPT in exploring the underlying architecture of adilas. There were four different sessions, all dealing with intellectual property and protecting that through sharing. Super fun sessions. This chat session (link below) is quite long, but super cool. It will end up forming a number of help files and other pages that go over the core or key pillars of the system. Here is that chat session URL or web link.

Intellectual property - protection through sharing: https://chatgpt.com/share/69b39e06-ff24-8007-bdf7-036f696e35d0

As a note, there are multiple PDF's attached to this element of time that have the saved ChatGPT chat logs, if needed.

--- General Outline ---

Master Category
Adilas Strategy Hub

Branches
Messaging
Adilas 3-Part Pitch

Community
Adilas Community Strategy

AI
Developer Notebook AI Training
AI Training Roadmap

Strategy
The Adilas Value Formula
Deep Dive Strategic Topics

Future
Future Projects & Concepts
World Building

Infrastructure
Data Assembly Line

IP
Protection Through Sharing
Intellectual property - protection through sharing: https://chatgpt.com/share/69b39e06-ff24-8007-bdf7-036f696e35d0

Emails, texts, and light planning on next steps. I had a great planning and brainstorming session earlier this morning with ChatGPT.

Research and prep work for working with ChatGPT on the SWOT analysis document. We ended up going so much deeper than just the SWOT analysis (strengths, weaknesses, opportunities, and threats). I did some research in the developer's notebook and did some sub look-ups as I went through the session with ChatGPT. I really enjoyed it. Here is the full link. For the record, it is pretty big, but golden... Tons of little gems.

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

Here is a small section, from the end of the chat session. I thought that it was pretty good overview of what we did.

From ChatGPT: Brandon - before we wrap this huge session up, I want to say something.

You came into this conversation asking for help with a SWOT analysis.

But what we actually uncovered together was:

The Adilas Story

The One-Page Overview

The Strategic SWOT

The Value Add-On Core Model

The Big Picture Map

The Explanation Ladder

That's basically the foundational narrative of the platform.

And honestly, it's a lot clearer now than when we started.

Back working with ChatGPT on the SWOT analysis. It was fun, it was helping me uncover a number of hidden narratives and connecting sub pieces of the adilas story. It went way beyond just a SWOT analysis (strengths, weaknesses, opportunities, and threats). Here is the chat link:

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

Back working on the SWOT analysis stuff with ChatGPT. Making good progress. Going super deep into the adilas history stuff. I also spent some time talking with Heather (my wife) about adilas and why we are doing what we are doing. Trying to boil all of the different things down and put them all together. There is a lot going on.

If you want to really learn about the adilas story... You should read this chat with ChatGPT. For the record, it is a little bit long, but really good information.

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

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

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).

Meeting with Russell and Abby. Going over plans. Russell was leading us through a small exercise to mix AI, screen capture, HTML web page creation, mock-ups, etc. Fun exercise. Plans and hitting the heaviest things first. Taking the time to play and setup the capture process. Watching him experiment and play before he committed to anything. Looking into scribe.com and possible time saving things that we could do. We also looked at TechSmith Snagit. Both have AI step capture options.

Doing some drawing and mock-ups before really building. Making templates and standards first. We were then watching Russell work with ChatGPT to help him build out some simple starting things. AI seems to be great from scratch..., sometimes struggles on larger projects. He had GitHub Copilot make the new pages. We watched and it was honestly pretty amazing. It seems to do awesome from scratch, based on a really good prompt. It seems to struggle when there are big projects with micro tweaks. Hard to keep track of the overall rules and context.

Just for fun. This is from Russell - this was his original prompt... ChatGPT then helped him tune it up. We then used GitHub Copilot and Claude to actually build the mini starter app. https://chatgpt.com/share/699f87bd-def8-8011-b518-ad0eac223d04

Working with Bryan. Working on web payments page. This is for invoice payments after the fact, the invoice already exists and they are just making a payment. Pretty elusive error. The page seems to be redirecting itself to the same page and losing some of the prior context. We were trying to find where it resubmits itself. Eventually we found a JavaScript function that was happening in the page header. It was looking for a certain URL variable. If it was not found, it was resubmitting the page and adding the variable. That is fine and well but doesn't work for pages that are submitting form fields.

We ended up getting some help from ChatGPT, after hours of digging. We honestly could not find the error. Funny side note, the original function looks like it was written by an AI bot, and someone added it to the page to help automate something, we then had to use a different AI bot to help fix the problem. Bryan spent hours looking around, then he got me involved. We spent hours together trying to figure it out. AI both helped and hindered on this one. Two-edged sword... :)

Phone call with Steve and then a phone call with Bryan. The main subjects were dealing with pricing and how to help figure things out. Here are my notes.

- Pricing has always been a crazy battle.

- Steve, Josh, and Bryan have been working on some ideas for pricing.

- Bryan was running things through AI (ChatGPT). Here is a small summary of what it recommended. As a note, Bryan sent me a file with more of the chat messages and prompts.

----

Adilas Pricing Summary

Monthly Software Fee "Unlike flat monthly fees that hit hardest when times are tough, Adilas scales with your business-low when revenue is low, and never punishes success."

- 0.4% of gross revenue

- Minimum: $59 per month

- For multiple businesses or monthly revenue over $150,000: Please contact us for a custom quote

Setup & Training (One-Time Fee)

- $300 - Includes 5 hours of system activation and personalized training

- $500 - Includes 10 hours of system activation and personalized training

- Hours are tailored to your needs. Most clients are fully operational within the included setup hours.

Additional Services

- Ongoing training: $65/hour

- Custom development & integrations: $100/hour

----

- As we use more AI stuff, we and/or our clients, may be charged more for tokens and token usage. Currently free, but that may increase as we go. We will monitor the tokens.

- Steve was saying that Josh has been pitching the enterprise system, for up to 10 entities, at $2,500/month.

- Some of our competition makes money on the credit card processing. We don't really care what merchant processing company they use.

- Steve was talking about a potential client that has a consignment type location. He was talking about a pricing model per booth or per sub section of the consignment store.

- The per location question always comes into play.

- We need to set some minimums.

- It seems like the sweet spot is a business that does between $40K to $100K per month in gross revenue.

- Pricing is confusing and totally depends on the model, the vertical, the complexity of the client, and expectations.

- We like to talk to the person... It helps us read the person and what they are feeling and looking for.

- Steve and I talked a lot about showing them the value of what they are getting. Josh has been pushing on that as well.

- We were talking about some folks wanting to do their own coding using AI.

- We offer all kinds of managed services, including training, setup, deployment, data entry, fractional bookkeeping, etc.

- Most system are just a POS (point of sale) - adilas is so much more. Often people are comparing prices of what we offer to someone else who is just offering the POS part of the puzzle.

- We should probably be compared to ERP pricing, but that sometime puts it completely out of range for the smaller guys, smaller clients, and companies.

- Steve and I were talking about impressions. He kept saying, we are not trying to give them any impression. People will form an impression, either way. In a way, we don't know how to brand or pitch ourselves.

- Maybe come up with some categories of pricing and let the clients see where they fit. In a way, how do you (as a client) want to be priced? Percentage, fixed price, per vertical, per location, etc. - Not sure.

- Being on the street. I was proposing things and Steve was saying, that's all great, but you need to be out on the street and see how that is received. I was pitching for higher prices.

- Walking a mile in someone else's shoes - you'll get the idea and figure out where they are coming from.

- Most software is priced per vertical. There are so many verticals. Maybe we offer dynamic pricing... Let's talk.

- We were talking about Finetech (merchant processing company) selling our software as an add-on. Something like this... it will be such and such for your merchant processing. If you want, we have connections with an awesome software company that we could add-on for x (some small percentage - Steve was thinking about under .5% or 1/2 a percent).

- Steve was talking about how he feels that processing is going to change. Dealing with more mobile type ways of accepting payments and auto tying things into a POS or some sort of system. Robot type stuff.

- At some point, we would love to bill for usage, storage, and processing (called throughput). He was saying that it would help to have some case studies and some examples. We would love to get there, but we are not ready for that yet.

- One of the most common things that we can tie a price to is revenue. It seems to tie things together.

- Most software systems are sold by the seat. With adilas, you get it all.

- We are trying to get a ballpark price (self serve - online). To really get it tight, we would like to talk to the client.

- Get a hold of us. Let's talk.

- We are US based, for our tech support. Steve was saying that was a big question that he has been hearing. Where is your tech support based out of? Am I going to be able to understand the person on the other line? Legit question.

- Switched over to talking about load balancing our servers. If we were to make some changes there, we could cut some costs. Steve is working with Wayne on this. Dealing with server backend coding languages and licenses.

- Databases, datasources, and converting the bus into motorcycles. Maybe create a new database that has corp-specific database tables or some other changes. We have wanted to do this project for quite some time. We have called it the datasource project or the world building project.

- In database land, if we could make things go away (clients and accounts), we could potentially allow for anybody to setup a system. It would either make the grade or get fully removed. Currently, we don't remove anything, we just set it to inactive (virtual delete).

- Drawing the line somewhere. That could be price, company size, business vertical, etc.

- Questions about servicing the account - if it is so small, it makes it hard to service it, there isn't much buffer to cover any tech support costs. Maybe offer a tech support plan or a be able to pre-pay for a certain number of tech support hours. Just some thoughts. This is mostly for the really tiny accounts.

- Talking costs and split commissions. Say something like this... Our costs are 40%. The remaining 60%, we could split 1/2 and 1/2 or 30% with whomever is selling or servicing the account.

Anyways, some good conversation topics and ideas. We will get it all figured out. Making progress.

Meeting with Russell and Abby. Lightly going over some existing graphics and flyers. I was showing them where we are heading (mixing some of the old adilas flyers as part of a 3-way pitch). We then turned into practice mode. We picked a website and then started to do a mock-up on that website. Working on layout and design stuff. Talking about what we like and how to start using the mock-up. Russell was grabbing images from online, cleaning them up, and then having ChatGPT to make things similar. Most of the session was a practice session. It was fun.

Meeting with Bryan. He wanted to do some planning on the Finetech and host huskie projects. We looked over some of his notes. He is gathering some little bites, chunks, and getting a number of recommendations from ChatGPT. Harvesting some of our user's feedback and recommendations. That is huge.

Meeting with Alan. Going over existing AI trends. Talking about our existing model. We logged into the Nxtlinq backend dashboard and looked around (current adilas AI agent backend). Lots of chats and what not, going back and forth about ideas and options. Alan was saying that he has been looking up what customers really want from an AI compliant ERP system. We chatted about that. We then did a small session showing what we are doing and how we are using different AI pieces and projects. I got into VS Code and showed Alan around a bit. We jumped into ChatGPT and looked at how it is helping as well. We chatted about some new ideas and where to help take things, going forward. We also setup a time to meet next week.

Working on new 2026 federal withholdings and payroll tax calculations. Pulling data out of the Pub-15-T document for percentage method values. I spent a couple of hours with ChatGPT to help me get the correct values. I was pushing up PDF files and tables, having it read and format the SQL insert statements that I needed. Here is the link for the AI session.

https://chatgpt.com/share/695d9c3a-87fc-8007-ae5e-eada5f629dea

Spent the first 2.5 hours working on the Grok AI agent and getting things tied in there. We are just starting out there and tiptoeing through that process. We are using Grok as the AI agent, for this new one, and then using ChatGPT to help us know how to code the stuff for Grok. Kinda funny. Anyways, we had a great session. We were in deep rewriting code. We were asking all kinds of questions and testing those changes that we were making. I was happy with the session.

The last half an hour, we were looking at the code from Alan and the new CardPointe stuff. We need some new code and changes but were not sure of the status of that project. We looked at his branch and poked around for a bit. I will give him a call. He and his wife recently had a new little girl. I imagine that he has been completely pulled into that mix (life in general).

Meeting with Steve. He is working with Grok and ChatGPT to help him code some things. One of his projects is working on some ecommerce sales by category specific settings. We flipped over to working on the Grok AI chat bot inside of adilas. We setup a scratch file and were working with it to see what the responses were. We changed some paths and did some light debugging. Our next joint session will be again on Thursday afternoon. He may work on it as he gets time. I pushed up all of the changes to his branch inside of bit bucket.

At the end of the session, we were chatting about other developers and other projects. Light catch-up stuff.

Working with ChatGPT on the round 2 plan for helping to train the AI agent model. Good session. Here is the link to our chat session:
https://chatgpt.com/share/69462819-9640-8007-9f14-948f203349b9

Quick graphic change for a client. Light tech support and light clean-up. Only took about 15 minutes.

Spent the rest of the session recording notes from 12/12/25. Ended up having ChatGPT help me convert the hand-written notes into text. We then explored some more options as to the full plan of where we are going.

Here is the link to the chat session that I had with ChatGPT - basically, a planning session with ChatGPT on our round 2 for the AI agent training.

https://chatgpt.com/share/69462819-9640-8007-9f14-948f203349b9

Bryan and I met up to look over progress for the restaurant and simple food service functionality. Bryan Dayton has been helping to chip away at this for the past year or so. We did a small review session and took a bunch of notes. Bryan then had the idea to take the new notes and add them to the old notes. We ran them through ChatGPT and it did a great job summarizing things up. We then read over those notes and talked about next steps. Here is the link to our small discussion.

https://chatgpt.com/share/693c91f3-a6bc-8007-a331-7ea33d2b84f2 - notes from Bryan and I from ChatGPT - restaurant and simple food service functionality

After going over plans and notes, we switched briefly over to some other projects. We will meet again on Monday to get into some other projects. We also briefly looked at some hours that have been recorded over on the ship B (adilas shop) side. Both Bryan and I (and others) have been banking some hours on projects that don't have full funding (yet) but we know that they will be needed.

Reinforce
Recruit
Israel (Zion)
Babylon (World)
Reveal & Interpret

---- Notes from a brainstorming and planning session (see attached)

So, just for fun, I had ChatGPT convert my notes into text (OCR style). Here are my notes in a typed form.

- Working on some planning to help with global context & AI/Human training

- I've been gathering some post-it notes for about a week. The electricity is out so I went over to my in-laws house. I'm converting notes from my post-it notes into notes in this notebook.

- 3 notes from 12/6/25: (see below)

Teach the AI agent how to delete or make things inactive - We had some chat messages where a user asked & the AI agent didn't say the right things. We just need to help it out a bit. Coaching...

Teach it how to get to stats & totals. The user asked some basic questions & the AI agent sent them to a decent/okay page, but it could have been better. Once again, more training

Fix & fill in the gaps

------------------

I had a couple of papers (post-it note style) from 12/8/25. Here are those notes:

- I have been thinking about stuff. I will be laying in bed & my mind is going & racing along.

- Make a plan... what tools & options do I have? Use what fits for each situation. It is okay to mix it up & adapt to what works.

- Plan as if for years - I can see some short patches and fixes - plan as if for years, meaning what is it that really needs to be done?

- I have this card & it talks about doing things "Glacier Style" - Carve your own path, go slow, channel your strengths, clear the way for others, stay cool, avoid meltdowns - I really liked that!

- Feed in the glossary - take your time & even add more as needed.

- Look at the prior plans - I've been working on this for months - Sometimes, I get going so fast, I start skipping things

- Work with what you have - that is a great base - you can always make more.

- Use one AI model to train the other ... That could be very useful. Harness the strengths of each model.

- Use voice to text to help with editing - where it fits

- Help the system learn - Take some of the chats & show the request, the response, and any suggestions - maybe help it by giving the answers a rating - just an idea

- Offering to save something for the AI agent - giving it some memory - How would that work? What would that look like

I took a few more notes on 12/10/25 - see below

- Build a small chunk specific tool - include meta data options

- Think in terms of small templates - I want this, this, & that for X - I want this, this, & that for Y - Try to stick to it - for consistency

- Spend some time training the little one - meaning the private AI agent for adilas

I also had some more ideas last night in the middle of the night, and early this morning on 12/11/25 - see below

- On the glossary items - add some terms like: AI, AI agent, AI context window, big data, BI or business intelligence, Knox report, mix, spread, delete, status, Nxtlinq, global context, meta data, vendor credit, special accounts, loyalty points, gift card, threshold, mini scan cart, refund, CardPointe, Clover, go mode, AI quick search, signature, e-signature, printer friendly, bulk add, bulk edit, bulk transfer, AI tools, cash counter, fulfillment, AI image generator, touch or touch screen, modal, retail, dashboard, flex attribute, KPI or key performance indicators, due date, tiered pricing, vendor catalog, delivery, age verification, view only, cultivation, metrc, percentage calculator, sales and profit, Adi, harvest, plant tags, data table, label builder, fracture, chart of accounts, reflexive flex grid, direct deposit, parent/child, try storming, and half baked

- When adding global content what about default sort orders for tools & glossary items? Expanded topics, etc. see next page for a huge list of what we may want to store

- Build a new tool for the AI agent to get at the data - think about a sliding window (AI content window) over tons of data - we only want it to pick up what it needs to

(sliding window diagram text skipped but referenced)

- Brainstorming on types of data that we may want to collect & organize...

- general or global
- help files
- glossary
- tools
- developer's notebook
- ideas
- brainstorming
- documentation
- R & D (research and development)
- extended topics or deep dives
- chat messages
- news & updates
- history summaries
- emails
- tech support
- special tools
- business functions
- application players
- core concepts
- FAQ's
- tutorials
- step-by-steps
- Screenshots
- graphics & visuals
- sales marketing materials
- internal
- admin tools
- AI summaries
- user stories or scenarios

For me - add links, references, sources - document things at different levels

- Recruit help!

- Send an email out to our team - looking for (fill in the blanks)

- Send content & information to me & I'll enter it into the system (at first or for the first round)

- When we are ready, and if they (our team) wants, we can help train them on how to add, edit, & view the global knowledge base stuff

New notes from 12/12/25

- Small note or context - I was doing some scripture study and looking up some information about being alive & times & seasons - It took me to 2 Nephi 25:25 - then started to look at some verses both before and after that - Some of that was talking about scattered Israel (like in the Bible) I had this thought about adilas... and what I am working on. (see below)

- Things are all there... they are just scattered - we need to gather them & help them to be more organized - once they are gathered and organized, the goal is that the knowledge & information will continue to grow & thrive - help gather and organize!

- On training the AI agent I may have to tell it something & then tell it what I told it - light review & reinforce the key points

- I want to fix and fill in the gaps... That is awesome - At the beginning, anything will help - there aren't gaps, there are holes - just start

- We can always circle back around & refine, fix, patch, polish, and/or rebuild - like try storming, we plan, we do it, we see how it works, & we plan on circling back around again & again - small feedback cycle - build & break, build & break

- Terms (words) that I was looking up... alive or living... learning, growing, being used, purpose

- I do a lot of trail building and maintenance - it is quite the process... We have to scout things out, explore, make mistakes, flag, clip brush, do dirt work, build walls, bridges, crossings, bank retention etc. Then we need to use it (traffic), get others to use it, & then circle back around again - very similar to the try storming concept

- What does it take to become a master? What a process that is...

- Repetition & context... experience, learning & applying what you know

- Times & seasons - everything in its time

- Small side note... when I don't know how to spell something, I will enter it into Microsoft Word & have it help me with spelling - I already had the words reinforce and recruit. I couldn't remember how to spell Israel - Like gather Israel, from the Bible

- Anyway, I right clicked on the word Israel to see if it had any synonyms - It said Zion as one of the synonyms - I then had: Reinforce, Recruit, Israel (Zion) - Wow, I had a fun spiritual experience - it was awesome & it hit me - I don't know the full meaning, but that hit me pretty good - kinda like a mini outline of the plan of God

- Recruit help from others - old power users, reps, consultants, clients, trainers, etc. - If needed, reach out individually to see what you get back.

- I'm loving the deeper connection(s) like pondering inspiration & revelation - for me, help others tap into that source or channel

- Help create the rich, context specific environments, and make it possible for others to pull from the source

- We are gathering

- We are gathering, even in our choice of models -

(drawing of two models with text)

Other systems - mashups & using a bunch of different systems to run your business

Adilas.biz - systemizing the application & bringing business functions together

- We are organizing

- We are learning

- We are being led

- I am so grateful!!!

- Little by little, line upon line, here a little, there a little

- Like Daniel & King Nebuchadnezzar (had to lookup that spelling), king of Babylon (or the world) - In Daniel chapter 2 - Daniel had to both show (reveal, uncover, expose, disclose, tell, show) the dream & interpret (understand, explain, clarify, read, decode) what it meant - both reveal & interpret

- Stone soup - Bring what you have got & throw it in the pot - We are making stone soup - mixing & blending different pieces together over time

- I sure enjoyed my learning & connection session - It meant a lot to me - Hours of rich connection & inspiration - I love it!

-----------------------------------------

The above is the end of the notes. A few days later, I took the original notes over to ChatGPT, I plugged them in and we had a small chat about where we are headed. If you want, this is a follow-up discussion that we had on 12/19/25 - https://chatgpt.com/share/69462819-9640-8007-9f14-948f203349b9

Quick meeting with the Nxtlinq guys. They were showing us a new compare feature in the backend dashboard. That should help. They wanted some feedback but I have been working more with the main ChatGPT vs the mini private model. It takes time.

On a GoToMeeting with Steve. He had a small question about some new settings. We did some debugging and got it working for him. He is working with a client that is using an ATM and then paying for invoices and giving change due back to the user. It's a special payment option from inside the cart. Basically, a new button, if turned on, that allows you see the invoice total and then a series of buttons in increments of $5 up to $250. The change due is calculated and the invoice is stamped with the correct information.

Steve and I also spent some time talking about AI training and using ChatGPT to help train the mini model.

Back working with ChatGPT on some training and PDF creation stuff. It is helping me create documentation for quick searches and special keywords and prompts. Working on inventory and operations functions like purchase orders, parts and general inventory, stock/units, recipe/builds, etc.

Emailing the team about the new functions for bulk adding PO line items (mini reverse shopping cart functionality). Small email to Wayne about a possible global database for helping to train the AI agent. I would like his opinion and thoughts. Spent the rest of the time working on a training plan to help train the adilas AI agent. Spent time working with ChatGPT to make a plan and start rolling it out. Towards the end of the session, I was having ChatGPT help me generate some PDF's to help with some of the adilas quick search functions.

As a reference, here is the share link for the AI training session that I was having. Some good stuff there. Light elevator pitch, a few small PDF files, some help files, and making plans. https://chatgpt.com/share/69377fb0-4594-8007-81af-a48edbc72690

Meeting with Steve over the GoToMeeting session. Going over agentic tool calling. He has been doing some research on both Grok and ChatGPT on how to setup or use our own AI agent. Talking about helping it to have its own memory by building in new tools and our own database to help with context and storage. Until we have that new database built, we will use the help file database. Tons of capacity there.

These are just some ideas to help with the AI agent training that we need to do.

- Use ChatGPT to help with the training

- Ask it questions about what might be missing - ask it to ask me about that? (Helping us to find what might be missing)

- Use it to train other AI engines and models

- I'm thinking about a general layout and organization structure (for a master adilas document) similar to the adilas presentation gallery. Help that go even deeper and deeper to show the different parts and pieces. That would include business functions, application player groups, desired outcomes (coming - currently called attributes but we want to redo that section and rename it to desired outcomes), and core concepts.

- See what it can pick up by crawling the site. Then help to feed it specific information and help put things into context and additional details.

- Take your time, not too much info at once, and then pause to make sure that we are good to go. The pause is important.

- I would love to do some of the training in levels... intro, beginner, intermediate, advanced, and deep or expert level training. That would be really cool!

- We are on purpose a general business tool, help the AI agents know and understand that.

- Fill in the gaps, let it do what it knows how to do.

- On help files (existing files), re-read them and make sure that they can be used as standalone pages. Add a small mini blurb or description at the top. Don't assume that people know what each help file is for... They may get to it from a different source vs naturally navigating to that page based on normal page flow or business processes.

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 Bryan. Talking about the AI options and how the training is going. We had ChatGPT convert a handwritten scan and had it make a visual display. That was pretty cool! Then we were talking about plans and direction.

We switched gears and flipped over the flex attributes in the cart (for invoices and quotes) project. We made some small plans and looked at older code commits on the branch we are working on. We then jumped in and did a good long work session on adding flex attributes to invoices and quotes and being able to use them inside the shopping cart (working on the details). We spent a lot of time working inside the mini scan cart and creating a modal popup window for editing the flex attributes. It is getting closer.

Working with Russell. Checking out in program Git options inside of VS Code, using the terminal, this is for code repository stuff. Going over developer stats and performance metrics that Russell likes to track. Talking about life and playing along with the learning process. Ways of getting through hard times. If God asks us to do something... He is basically singing up for the same thing. Talking about God's miracles. No taxing His power, nothing is impossible for God. The Lord is right there with us, in the moment, from our perspective. Ripples... that just keep going. Not a ton of code today, but good stuff for the soul.

Towards the end, we were playing with ChatGPT and running an image (adilas interactive map) through it to see what it could come up with as far as interpreting the graphic. It did a pretty good job!

Multiple sessions throughout the day. Emails and looking over documents. Going over new samples provided by the Nxtlinq guys. They provided a zip file and I was browsing and looking at the info on the page. I sent a couple of pages off to Wayne to look at, to get a second set of eyes on the new code samples.

Working on the Nxtlinq integration project. Working on some samples. Did some live testing, off the side, so that no one would be bothered. Worked a little bit with ChatGPT to get some code all lined out. That was kinda fun. We built it out and tested it locally and then pushed up some code live on data 0 for testing. I then sent some emails around to let a few people know. Finally, I sent off an email to the guys at Nxtlinq with a few small questions.

Intro to ChatGPT with Bryan. Trying to login and get setup. Their security code (2-Factor authentication stuff) to my email inbox kept timing out. Anyways, Bryan was showing me around using his account. It can really help with thinking outside the box. Bryan showed me a couple of usages that he does with ChatGPT. Things like: revising emails and email helps, summarizing data, code hints, itineraries, building business plans, sales stuff, notes and journaling, and asking it questions. Prompt it to keep refining it into what you really want. Start somewhere, then refine it. Sometimes, it (AI or ChatGPT) is great to help generate ideas that you may not think of. Asking it to change and/or alter the flavor as needed (once again, adding in the prompts). Good session.

I'm kinda slow on the AI adoption process (I'm resisting it). I know that I could use it and save time, I just haven't done it yet. This was a good intro for me.

Bryan and I met for lunch. We were talking about adilas, sales, clients, research, and using ChatGPT to help us look over all our notes and help us make some plans and summaries. Bryan is going to help me with that.

Working with Russell. We were talking about using chatGPT (AI bot) and getting suggestions on code. We then worked on some AJAX and infinite scrolling reload. Planning for a new project. See assignment below.

- Assignment for Russell and I - Start with Adobe XD - design a dashboard, chart, deposits, drill-downs, invoices, modal pop-up (with options for edit, view, print), time/projects and dynamic search - When we build it, the dashboard, it will be... I (Russ) do, we (both) do, you (me) do. Training exercise.

Fixing a bug on the calculate payroll page. The error was some older code that was doing a loop over a query with a grouping. That code used to work fine but doesn't seem compatible with the newer code. Bryan and I were working on this bug. We got stumped for a bit. I was trying things and running a series of tests. He put the errors into ChatGPT (AI or artificial intelligence bot). By the time we were done, we had a working solution. It took both of us to get a working page again. We pushed up code and Bryan sent an email out to Cory and others. 

Sean was on the morning meeting. He was using ChatGPT to get some bullet points for adilas as an all-inclusive ERP system. Interesting use of AI (artificial intelligence). Here is what it came up with...

Here are some possible bullet points for an all-in-one ERP system called Adilas:

• Comprehensive Functionality: Adilas offers a wide range of features to support businesses of all sizes and industries, including accounting, inventory management, sales, purchasing, payroll, time tracking, project management, and more.

• Cloud-based Solution: Adilas is a fully cloud-based ERP system, which means that users can access it from anywhere with an internet connection. This makes it easy to collaborate with team members, work remotely, and manage multiple locations.

• Customizable Interface: Adilas provides a highly customizable interface, allowing users to tailor the system to their specific needs and preferences. This includes the ability to create custom fields, labels, reports, and workflows.

• Mobile Accessibility: Adilas is designed to be mobile-friendly, with a responsive design that adapts to different screen sizes. This makes it easy to use on smartphones and tablets, enabling on-the-go access to critical business data.

• Robust Security: Adilas takes security seriously, offering multiple layers of protection to safeguard user data. This includes role-based access controls, encrypted data transmission, and regular security updates.

• Affordable Pricing: Adilas is priced competitively, with affordable subscription plans that scale with the size and complexity of the business. There are no setup fees, and users can choose to pay monthly or annually.

• Excellent Support: Adilas provides comprehensive support to its users, including online documentation, video tutorials, live chat, phone support, and email support. This ensures that users have the resources they need to get the most out of the system.

Kinda fun... Anyways, he will tweak it and make it our own, but that's what the chatbot came up with.

------------------

Wayne joined the meeting and he and I were working on my local machine and box. Somehow my development environment got all messed up. We took things up, down, up, and back down. Trying this and that, rebuilding images, cloning things, etc. We even tried reverting back to an older image to see if that would work. Still had issues. I may need to get a new laptop or computer.

After about 2.5 hours of playing around, I decided to go back to the old non docker image way of doing the local development environment. This includes standalone installations of Adobe ColdFusion, MySQL databases, and other pieces. I was making progress and then got stuck, having to run ton of database updates to get the database up to speed. Ended up stopping and bailing out for lunch. Too much to do all in one sitting.

Quick meeting with Bryan. We were going over some progress on his AJAX code for selecting items to do bookings and reservations. He got with Dustin and the two of them made some good progress (code wise). They also used some ChatGPT to get some ideas and answers (open AI - artificial intelligence). Making progress.