More work on help files, new aliases in the AI quick search, new navigation tips in certain help files, and small changes on the quick search (logic stuff). Small refinements. Working on glossary terms.

Small quick search logic changes. Updated the quick search options for adding or creating new main players (deposits, customers, invoices, PO's, expense/receipts, stock/units, vendor, employees, elements of time, quotes, etc.). Opened it up a bit to allow the wording to flip flop. Added code for keywords like new, create, and add. Prior, it had to be the type (which application type or category) and then keyword. Just for adds, you can now flip it, put the keyword and then main type or category. For example: old way - deposit new or time new - now you can do something like this new time, new invoice, new cart, new deposit, etc. Added in options to pass a prompt to the quick search page. This will help with navigation from help files and other pages.

Recording notes from 12/16/25 to 12/20/25.

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

I had to help with a school Christmas party for my daughter. Russell and Abby started at 2 pm. I jumped on at 3:15 pm.

Meeting with Russell and Abby. They were going over some options for app and web desktop layouts. Russell was teaching Abby and doing some training on design and layout options. Here are some other notes that I took, once I joined:

- The more people that you talk to, the more feedback you can get. That really helps.

- Having a reason behind what you do and why you do it.

- A good system or interface system that teaches the user about itself and how to use it.

We kept going over some layout options, for almost the whole time. We jumped into Adobe XD and showed Abby what some advanced layouts look like and such. We showed her some things from Jonathan Wells. We also showed her some historical stuff from both Russell and I over the years. You could see the progression. That was kinda fun.

Russell had to jump off around 4:30 pm. Abby and I met for another hour going over her stuff and direction for the future. We looked at a few more samples and she showed me a flyer that she was working on. She is still in training mode. We then talked about some plans and where we want her to focus. She will be building out some of the graphics for the adilas lite project, starting as of January 1st of 2026. That will be one of her first main assignments and projects. Nothing like jumping into the deep end... :)

Helping cory fix a bug with my cart favorites. We did a simple reverse if statement and it went back to what it was. We will get with the developer and help them refix things and then relaunch the code. In the meantime, it is back to how it was and people can use it. My cart favorites is short for my cart favorite buttons (custom POS buttons with special functionality built-in all controlled by settings).

A couple of days ago, I was recording notes and looking at glossary entries. I noticed that we were missing a few. I went through some of the newest news and updates and just grabbed some entries from the news and update titles. Spent the rest of the evening working on adding in new glossary entries. Here is a link to what we have done on the online glossary, at this point. I still have a few more to add, but it is looking good (as a starting point).

Looking around the site and seeing what resources we have or already have available. Looking in the adilas shop and adilas university sites. Tons of elements of time, flex grid tie-ins, and media/content records. Not just some, but like thousands and thousands, already done and public facing. Switched gears and sent out some Christmas gift cards to our team. Recorded those gift cards as flex grid tie-ins to the different team members.

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.

Meeting with the Nxtlinq guys. Going over frustrations with global context memory options... They will look at possible solutions. Ted was pitching some stuff... He wants us to focus on SOP's, ask our clients for their SOP's, flow charts, processes, documentation (good stuff), and helping to walk the system through the reasoning behind the decisions and the context.

We love the idea, we just need the AI agent to be able to really store all of the stuff that we are throwing at it. It can remember stuff, but it is super tiny. Also, because it is so tiny, and we have such a big application, it will load things into the global context window (its small memory space) and we will ask it about something else. It then kicks out the old to make room for the new. It really needs to be stored in small chunks in a database and then be able to get to that information on the fly. That's where we are heading. Frustrating but it will work out, it will just take time.

Meeting with Steve. We spent some time talking about the mini private AI agent. We logged into the Nxtlinq backend and were looking at their context window. Josh jumped on for a little bit. Steve and I were making plans and talking about things. Where do we want to go and how are we going to get there?

We talked about some global context pieces and what we are hoping for. We would love the AI agent to help us with some videos, running comparisons, drawing (whiteboards what to do).

Steve has a couple of other projects going on right now. We flipped over to them and went through them for a bit. We talked about three other projects and went over some questions that he has. One of the projects is that Steve had questions about using Grok AI as an AI agent. We talked about getting new session variables on the login, logout, change corp, 3rd party solutions, footers, and sdk's files or pages.

Next, we flipped over to a small project that is dealing with ecommerce and part category settings. Currently, we have a setting that allows for a corporation or entity to select a sales mode. These are inventory level controls like show and sell parent inventory, show parents and sell subs, show sub and sell subs, etc. All of these are dealing with parent/child relationships within the inventory itself. Steve is working on a new setting that will allow that bigger master switch to be controlled on the part category level. Some categories tend more toward child or sub inventory than other ones. Anyways, he is working on changing out that master switch and making it more granular at the part/item category level.

The last project that he is working on is saving a custom report from inside the system. The new report has both normal FORM scope params as well as dynamic, on the fly params. We went over some options and did some comparing of the FORM scope values. It goes something like this... We use a normal web-based form to pull the report. At that point, we have all of the FORM scope values or variables. If the user wants to save the report, we send all of the data over to a save report page that putts all of that information into a JSON object for database storage. We then take the new database id number and use it as a URL scope variable. Basically, run report X based on the settings stored by id number Y. It works pretty slick. We have done this for years and years. This particular one has some other random dynamics that are making it a little bit more difficult. We are not sure, but it seems to be a case sensitive problem with what is being created (dynamic FORM values) and what is being saved in JSON format. We didn't quite finish this, but were getting close.

Quick AI training session to see what it was able to retain. We did a longer session yesterday. See attached for some quick tests and new information about what we do and how we do it.