Small tweaks for Sean. He needed me to un-void a PO on data 16. Then on a phone call with Bryan to make a few quick edits. Pushed up a few files on data 6 for testing in recipe and production land.

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.

Phone call with Bryan going over next steps and priorities. We launched a bunch of new code last night for him. He has been meeting with different folks and getting requests and ideas from them on what they would like adilas to do and be. Trying to help make it easier and more marketable. Some of our clients want it to be more simple. We may have to go a little bit deeper before we can do that (more complex controls to make it look or appear more simple). Small to do list items.

Recording notes from 12/1/25 to 12/3/25.

Stuff for Cory. We had a report of some errors when adding things that had flex attributes (PO's, customers, and elements of time). We made some quick fixes and then pushed up code. Wayne was on the Zoom meeting with Cory and Steve and he was able to give me page names and lines where errors occurred. He was looking at some paper trail audit reports. We fixed a few files and pushed up new code. That small fix it session went pretty slick. Basically, a small on the fly bug fix - Wayne was telling me where to go, I was fixing , and Cory was testing.

Working on the flex attributes for invoices and quotes. Quick meeting with Bryan to show him the progress. We looked over a few things and did some test transactions. We created quotes, restored quotes to cart, made a few invoices and then duplicated those invoices. We have a little bit more work on the submit cart page, but getting much closer. Some of this stuff (code pages) are things that Bryan is wanting for restaurant functionality like areas, sections, tables, number of guests, reservations, etc. Good stuff. Making progress.

After Bryan left, I spent the rest of the time testing code and fixing merge conflicts. This was a pretty big branch, and we ended up with 20 files with merge conflicts. That is because we started it, this flex attribute project, almost 9 months to a year ago. Lots of cart and invoice changes during that time. Anyways, we got it all merged in.

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.

Emails. Paying bills and reading information from Steve working with Grok (AI) about the adilas AI model (Adi). He sent some texts around with some new features that were being highlighted based on AI going over our news and updates section. More emails.

Looking over logic for the flex attributes for the shopping cart (quote and invoice flex attributes). Working on the add/edit process through the update cart page for saving quotes. Updating logic for the classic cart.

Working on the flex attributes project for invoices and quotes inside the mini scan cart. Reviewing code for yesterday and then jumping back in on the project. Small work session.

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

Recording notes from 11/24/25 to 11/27/25.

Work session with Bryan Dayton on flex attributes for invoices and quotes. We are getting closer. Working on showing both invoice flex attributes and quote flex attributes inside the cart. Lots of moving pieces. Bryan was fixing some merge conflicts and I was coding the new logic for showing and updating the flex attributes. We got all the way to inserting the new flex attribute records. We ran into a little snag but will hit it again with fresh minds and eyes. Good long work session today.

Touching base with Abby. She has been working on some vector art training and is doing great. We jumped in and looked around on her practice project and talked about a bunch of things. That was fun. She is catching on very well. We also talked about other training in the photo editing and desktop publishing side of graphics and digital art. We then got into a number of other topics and talking about optimizing images, image sizes, dpi, resolution, and other semi technical pieces. Towards the end, we were even talking about saving your practice documents. We revisited some original ideas on the adilas logo and where that inspiration came from. See element of time # 4144 in the shop for some graphics of where the adilas logo ideas came from.

Meeting with the Nxtlinq guys. Talking about advancements on persistent memory and where things are going. We talked about the backend Nxtlinq dashboard and how to read and help the agent really learn (make things stick). We may need to focus on a specific part of the application and get it really tight. Due to Thanksgiving, we will meet up again in a week. In the meantime, I will be working on some other projects. Once ready, we will get back to AI agent training.

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.

Doing some AI agent training inside of adilas. Training on help files and adilas elevator pitch. More AI testing and even doing some testing and training from different servers and different user id's. See attached for some of our notes.

Emails and recording notes from last week on 11/20/25. Trying to use the AI agent a little bit more. Currently, it is kinda slow... "Thinking...". I can do it way faster using the AI quick search or the plain adilas quick search. We'll get it all trained up.

Emails and logging in and checking out the Nxtlinq backend dashboard. I'm hoping that I can use that or the main chat interface to help train the AI agent. Either way, we are making progress. We'll see where it goes.

Quick testing of the AI agent. It is still not retaining all of the information that we are training it on. We have to figure out a way for it to retain the correct background information (persistent memory). see attached.

Meeting with the Nxtlinq guys. Small updates. Thomas was showing me his nxtGPT product. They are tied to multiple LLM's at a single time and comparing them to each other. Figuring out the next steps. Talking about updates and ability to train and sync data with new and upcoming data. Talking about tax codes and new rules and how to keep the updates coming in. We need to make sure that the model (our AI agent) can get fed with new and updated business rules, data, and logic.

Meeting with Steve. Looking over some code for low part quantity email alerts. He is working on a some new email services. We then switched and talked a lot about training the parent and the child - AI bots (multiple agents, not just our mini). Our current model is not retaining any real information on a global level (yet). From Steve, maybe work more with the main or parent AI models.

Meeting with Hamid. Going over CSS training stuff. We were watching a video and talking about what the instructor was asking us to do. Good training session.

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 on some AI training... testing the AI agent. I wanted to see how it did with graphics, URL, PDF's, HTML code, etc. Just experimenting with it. See attached for our session and notes.

Recording notes from yesterday and today.

Cleaning up some recorded chat sessions with the adilas AI agent from last night. The original document was huge. I trimmed it way down.

Phone call with Josh to go over progress and direction. He wanted to know how the training was going, for the internal AI agent inside of adilas. I reported on what I knew and told him that the new persistent training was not sticking quite yet for the AI agent. I sent an email to the Nxtlinq guys, and they are looking into it.

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!

Trying to work with the AI agent, inside of adilas, to see if any of the training from last night was retained. Sadly, it doesn't look like it. We'll get it figured out, but currently, it seems that the training is just per session. See attached.

Recording notes for the day. Spent over an hour working on some AI training inside of adilas - see attached. As part of the training, I went over some of the older training sessions and then did some stuff on help files and general file structure within the system.

Meeting with the Nxtlinq guys. They wanted a way to get and show the error messages in the chat bot. If the page is able to navigate to the correct page, all is well. If not, meaning it throws an error, they want a way to get at those error messages. We also talked about helping to make better error messages to show what to do to fix things (make things more intuitive). They gave us an update and have optimized the memory functionality of the AI agent. There are now a number of users that can affect the global context (actual AI training) within the system.

After the meeting, Ted, Thomas, Josh, and I were talking about 3 buckets for our customers - low hanging fruit (those who are using it), those who could use it but aren't, and those who don't want to use AI. Ted was really pushing for us to try to get the people actively using it, even while we are training it. His focus is the commercialization process. We talking about the need for data and feeding the AI agent. After that, we were looking at AI data and logs, encouraging people to keep going and ask for more (what else would you want from the AI agent - figure out what the customers are wanting). Somewhat of an outreach plan to help commercialize things to our customers.

Back working on the add bulk PO lines items page. I copied the code from the parts homepage. I then had to go through it and strip it out a bit. Got the search and display page done. After that, I started working on the submit or action page for the bulk add PO line items page. Lots of validation and looping. I pushed my changes up to the correct branch in the repository.

Emails and quick fix for the Nxtlinq AI agent SDK file. Recording notes from the past couple of days (11/17/25 to 11/18/25).

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.

Getting back into the partial PO project. Here is a small list of things that still need to be done for that project.

- Open up the external_alternate_id field for all of the 12 main player groups. They, the database tables, already have that field, it is just hidden and not being used right now.

- In-store credits (customers and invoices) - new special account option

- Vendor specific or category specific PO line searches - add lines in bulk - somewhat of the reverse shopping cart for PO's - the normal shopping cart is for invoices and quotes.

- Full visibility - track total request quantities, total live quantities, and total still on backorder quantities.

After doing some review, I spent some time looking at what it might take to help add bulk po line items. Created a new branch to work on some of the new functionality. Started working on a new page for bulk adding PO line items. Took the original code from the parts homepage and then worked on tweaking it out a bit. The page will allow for filtering parts and items by vendor, by category, by item, by description, by location, etc. That should really help speed things up.

Emails and paying bills. On the phone with Bryan going over some ideas. Talking about custom development, running specials on development (prices), helping with training manuals, and having a custom code budget per customer, if needed to help make the sale.

Recording notes from the last couple of days (11/13/25 to 11/15/25).

Emails and sending an email to Thomas with some user/payee id numbers for adilas super users. These will be used to help train the AI agent.

The Nxtlinq guys are adding in more logs so that we can track some other things. They are working on a number of things including improved memory and global context stuff. Memory in AI is making training and knowledge stick. We also talked about a number of other topics. Here are a few of them:

- The costs for the infostructure and keeping the AI agent up and running.

- Talking about global information storage - we really need this, from our team to the bot.

- Talking about influencing things upstream and downstream. We need the AI bot to remember and learn, but we also have to be careful about where it gets its information.

- Light talks about an audio issue between multiple tabs. The AI agent is still listening in a different tab and responding. The simple work around is the mute button on the microphone. We may look deeper into this, if it becomes an issue.

- After the main meeting, Steve, Thomas, and I stayed on the meeting to talk about pricing and future plans.

- Being able to train the agent so that it can help with support, setup, and deployment. Figuring out the pain points and helping us as a company as well as our clients and users.

- Thomas was telling us some stories about introducing agents for other companies.

- Steve was talking about being able to help get the agent up and going and helping with oversight.

- Lots of talk about ingestion rates and values (how much we feed it).

- Human in the loop to help with the training.

- Thomas talking about manual crank windows (roll up/down the windows by hand) vs electric windows (power windows). Ideally, we show our clients and users how awesome it is with AI help. Then, hopefully, they won't want to go back to older tech.

- Getting into the BI level (business intelligence level) later on, as we go.

- If we train this agent up, it will really help our users and clients with training, consulting, etc.

- Here are our steps and phases for working with the AI agent - 1. Navigation and prompts, 2. Setup and training, and then 3. Clear out to consulting.

- Small phone call with Steve afterwards to go over our internal plan a little bit. Good meeting.

Meeting with Hamid. Showing him some graphics and then playing with the adilas AI agent inside of adilas. One of the goals for the AI agent is... training and retaining (keeping or holding the info). We then worked on getting his VS Code instance up to date (his code editor). We played around with some code and letting Copilot (a different AI bot) help with some of the coding. We also talked about the value of knowing what is going on and/or what is being prompted/generated by the AI bot. Especially in code, the bot may give you a bunch of code, but you don't know what it does and/or how to fix it or tweak it slightly. You can get yourself in trouble. You still have to know code. Fun little session. Lots of show and tell and light playing around with different tools.

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.

Recording notes from yesterday and today (11/11/25 to 11/12/25).

Meeting with Russell and Abby. Reviewing some graphic lessons and drawing with the pen tool. That one takes some practice. They were helping me with a small project with some suggestions. We then did some more advanced work with gradients and blending shapes. Fun training session. Russell also helped me get signed up for a copilot (AI) code helper.

Meeting with the Nxtlinq guys. They were giving us some updates. They changed the word verify wallet to verify account. That will help out a bunch. They were giving us a number of other updates on things that they were changing and updating. We are all making good progress. They were making a few requests on and we were as well. Both sides and working well together. They are trying to get us some global admin permissions so that we can help and teach the agent. Lots of talks about ways to monetize things (we've got to pay for this thing). Steve, Josh, and Ted were heading that up. This is new territory for everybody. Anyways, the adilas AI agent (by Nxtlinq) was opened up (turned on and allowed) on every corporation and every server this evening. Here we go!

Quick phone call with Shari O. She had some questions about some sold inventory reports. Spent some time refactoring some code on the adilas third party action page. Removed tons of lines of code. Consolidated some of the sub API socket assignments into a function call.

Jumped on a meeting with Steve to go over some prep stuff for the AI agent launch. We were asking the ai agent to help show us some info. It didn't retain our last training session. It did, during the session, but then it didn't keep it long term or globally. Light AI training... see attached word doc - eventually, we want to make all of our documentation public and use it to train all of the LLM's (large language models). That would be super cool.

Working on cascading the code to get the Nxtlinq AI agent up and running for all corps. Added some code to the classic homepage to check for the AI agent. If the AI agent is not found, it auto adds it. That should help with new corps coming onto the system. Finished up the code to cascade the auto deploy of the AI agent to all servers and all corps. Pushed new code up and ran the update.

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.

Checking some of the new code on the servers. Recording notes from yesterday. Light research into what the other guys are doing on the team. Working on some bulk flip tools for the AI agent. Setting up a new function to help with the process of opening or closing subs or mini API sockets.

Multiple sessions throughout the day, all working on the AI agent launch. We are just a day or so out from the live launch. Here are a few of the things that I was working on today.

- Doing some planning for the day. We have a bunch of things planned to help with the AI agent roll out. Sat down at the table, away from the computer, and wrote out about three pages of notes. If I go right to the computer, I get an idea and just want to do it. Sometimes, it really helps to step away from the computer to do some planning.

- Started coding by adding in a new user level on/off switch for using the AI agent at the personal settings level. Tied that mini switch clear down to the login level of the application. Cascading code throughout the system to match the new setting.

- Working on bulk flipping the AI agent on for all corps. Tightened up the mini API to specifically look for the Nxtlinq web id to see if access is allowed or not. Read through a draft copy of a new entry from Cory for a news and update on the AI agent inside of adilas.

- More planning for a bulk update to help turn the AI agent on for each corporation and get the correct API sockets turned on as well.

- Checking code and then cascading database changes to all servers. Running updates to add the new user level setting for show/hide for the AI agent. Pushed up a couple of files and did some light testing on data 0.

Adding in some new corp-wide settings, to the local variable scope for the SDK for the AI agent. Sent a small note to the Nxtlinq guys with a few questions. Responding to some emails. Sending information back and forth with the Nxtlinq guys. Showing them some newly proposed corp-wide setting variables. Nineteen new variables for things like what to call the company entity, what to call your customers, your parts, inventory items, locations, etc. Basically, helping the AI agent speak the language of the corporation or company using the agent.

Working on some PO chaining and linking for Cory. Using flex grid tie-ins and reflexive flex grid tie-ins (going from main or parent to child tie-in - both directions). This is a sub part of the partial PO project. Added new code, did some testing, pushed up new changes. Small tweak to the help file. Sent Cory an email letting her know.

Had a small training session with the AI agent inside of adilas. We started into the corp-wide settings and how adilas is setup as a general business tool. I ended up with a multi-page document from the training session (copy and paste from the chat bot). See attached for the document.

Paying bills and recording expenses. Quite a few from the trip that Bryan Dayton and I made to Las Vegas for the Adobe ColdFusion Summit conference. Checking emails. There were quite a few emails going around in preparation for launching the AI agent next Tuesday.

Meeting with the Nxtlinq guys. They have been removing the AIT validation stuff, at our request. It just makes it smoother. We are tracking and logging things inside the system already. They are also logging things based on the passed in user info. Here are some other notes from the meeting tonight:

- Maybe an internal survey to see what is important to them, security wise

- Shooting for a friction free environment for the users on the AI setup and usage

- Automation of orchestration and governing the management of the AI tools

- The launch is just the start. Then we finetune and optimize things as we go

- Possible customer services bots or agents monitoring support bots and prompts

- Talking about support and helping to see some automated options - less manual work - maybe use the AI agents to submit any support needs or bugs

- We talked a lot about prepping for a launch next Tuesday. We are planning on pushing the AI agent to all of our existing users. They don't have to use it, if they don't want to, but it will be turned on and available for all users.

- They, Nxtlinq, are going to do a quick video or series of gifs to help with the wallet link-up and verifying the user.

- Steve was saying that we will be trying to stay in front of our clients - prep what we can

- From Ted... our super users will become superhero users

- Small discussion about people - they need to use the new tools, or they will be left behind

- Ted was talking about the wheel. He was saying that AI will be as impactful as the wheel, in his mind.

- Helping our customers become believers

Recording notes. Reading over a plan from Josh dealing with AI stuff. He was chatting with an AI bot and got a number of suggestions and ideas on how to help train the adilas AI agent. See attached for that document.

Small side note, I was thinking and daydreaming about what it might take to help train an AI agent... I have trained quite a few humans - project managers, developers, designers, clients, users, consultants, and sales reps - just not an AI agent yet... :)

On the phone with Bryan. He had some questions about reoccurring or recurring invoices. We talked over the process and other options that we could add in, if needed, including full automation and dynamic data (changing invoice prices and totals vs a fixed reoccurring process). We also talked about getting back to some of the restaurant functionality that he was working on back in August of this year. We set a date to get back to that in a couple of weeks, before Thanksgiving.

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

Recording notes from yesterday and today (11/4/25 to 11/5/25).

Emails and installing some new software. Then working with Russell and Abby for a couple of hours. Working and practicing on doing vector graphics and working in Affinity Studio. Lots of pen tool work. After Russell left, Abby and I kept going and doing some one-on-one training. After that, Abby showed me some stuff that she is working on her own. She is working on some graphic ideas to show the different versions of adilas and how things rolled out. That should be pretty cool. We then jumped into some photo editing skills and such. Abby is still in the learning phase but picking things up quickly. I sent her home with one of the adilas laptops until she gets her new laptop. That way she could practice using the actual tools vs simple drawing tools that she had. Lots of work with Affinity Studio today. Fun little product.

Quick meeting with the Nxtlinq guys. They were reporting on a number of enhancements. They now have complete audio options, no need to click the send button. They are wanting to get an Adi (our dog avatar mascot) image for the AI agent. Ted is really wanting to get the AI agent out to all of our clients. Even for free for the first little bit. Light talks about learning cycles and dedicated learning time for both us and the AI agent.

Some of the feedback that we are getting is that our clients want more deeper functionality... things like customer histories, PO's for specific vendors, and other more advanced look-ups and datasets. We have to start somewhere... we'll get there.

Jumped on a phone call with Steve. Mostly talking about the AI agent and how to help push that project forward. His laptop isn't working.

- He wants me to jump on the meeting later tonight

- We are going as fast as we can

- He wanted me to check on the progress on ingesting all of the adilas help files

- Work in progress... There really isn't a set or defined end to what we are doing

- Let's see if they can crawl or ingest the developer's notebook pages

- Move into deeper testing and getting some great feedback

- Ted really wants us to give the AI agent to all of our customers vs just having it available through the 3rd party solutions page - Steve and I were talking some pros and cons for that approach

- We need to include the new setting to turn the agent on/off at the user level. The main level is the corp level based on the 3rd party solutions page. The sub or individual level is on the my settings page. This needs to be built before we push the main AI agent live to all clients.

- Looking into building complex prompts or multi process prompts

- Most of our clients are using sub inventory, we need to plan and test for that. Currently, most of the cart activity is based at the parent inventory level.

- Steve was saying that we don't want any of the wallet verification stuff inside of the AI agent setup process - it causes friction and seems to be a hassle

Working on duplicating PO's with the flex attributes. Going through the process to make sure that everything is setup and allows for duplication even with sub inventory. Also worked on the duplication process for PO's to work with flex attributes. Small tweaks to help with flow. Cascading code to other places. Light clean-up around the site for adding and updating flex attributes. Testing and committing changes.

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.

Paying bills and checking emails.

Updating all of the server and their time zones.

Recording notes from yesterday 10/30/25.

Meeting with the Nxtlinq guys. They had a small agenda and we went over it. Nothing too crazy. They are using a crawler to go over the help files. They did have some questions about some of AI quick search prompts that did not have a help file and/or would go to some other site or external reference. We talked about it and they are going to use their web crawler and get what they can.

Thomas from Nxtlinq was talking about their AI agent, they are calling NxtGPT (GPT stands for Generative Pre-trained Transformer - AI deep learning stuff). That seems like a cool name.

I may put in writing some of our requests with regards to the AI agent. We just want to turn it on and not have to verify or set permissions. Our application has built-in error handling and user permission checks on every page. If we have to do settings inside the system and inside the AI agent, our customers or clients might say no. Too much setup... Anyways, I will put some stuff in writing and we'll go from there. Basically, I'm going to say that adilas, as client of NxtGPT and Nxtlinq, we don't want the AI agent to require permissions. The adilas.biz application will take care of the permissions at the user per corp per page level.

They reported that they are ingesting the help files and pushing them over to the agent. That is awesome. There are over 500+ help files. That is awesome and will really help get the AI agent smarter on adilas stuff.

Lastly, I really want to read over some feedback that they, Nxtlinq, gave us from the last meeting. I briefly saw it, but want to really give it a better look over. That is mostly for me. Anyways, good meeting. I sent Steve a quick text after the meeting.

Meeting with Hamid. We did some reviewing of where we left off last time. After that, we then jumped back into the CSS course from Udemy that we were working on. Practicing and playing around with the commands and code. Went through a few chapters and videos. We are both trying to learn more about CSS. I already know some things and I've worked with it before, but never gone through an official course or class. It is surprising how many base level pieces I either thought that I knew or only mildly understood. I'm enjoying the learning process.

Emails and reviewing a super cool video on Affinity Studio - It has some awesome custom menu options and is a well done promo video. I watched it and then sent it out to a number of our people to show that what they are doing. I would love to be at that level where we can push something like that out and create those kinds of tools, features, and razzle/dazzle. Pretty cool!

Paying bills, phone call with Bryan about transitional invoices and options. We have the functions and functionality, but nobody knows how to use them... We need more training and easy ways to get at what is possible. I was explaining to Bryan how it all works. We also talked about moving away from sub inventory, depending on the scenario. Sometimes parent inventory tracking works better than subs, for certain scenarios. We also need to get to the ICC (internal cost corrections) project up and going. That has been a requested feature for years.

Recording notes from yesterday and today.

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 help files. Back tying and back sewing help files to prompts. Finished up the first round of back tying (just over 100 help files modified). I then went to each server and pulled down the latest help files (syncing data across servers).

Recording some notes from yesterday. Meeting with Russell and Abby over a Zoom meeting. Small lesson on drawing vector graphics and playing along together. Russell was leading out. Abby didn't have the right program, so we did some screen sharing to let her get some practice. Great little training session.

Meeting with the Nxtlinq guys. They went through our feedback (from Sean) and tried to duplicate and checkout any and all of our feedback that we gave them. That's pretty awesome. Some of the feedback was requesting complex or linked prompts. We know that the users want us to get there, but we have to take it one step at a time. We aren't there yet. We tried to provide them some answers and such. I think that it went pretty good. Talking about ingesting help files for the AI agent. Talking about re-verification of identities within the AI agent. We are making progress.

After the meeting, I was working on a newly requested combo prompt for starting a new cart and assigning a customer to the cart. Finished up the new advanced prompt. It looks like this: new customer cart assign [customer id] - Here are all of the cart prompts as of right now.

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.

Recording notes from yesterday and today.

Jumped on the GoToMeeting session with Steve. We were talking about some of our plans for building out the AI quick search and AI agent stuff. See elements of time # 12392 for some details and fun ideas. We also talked about the Ship A to Ship B transformation and paradigm shift. See elements of time # 12385 for details. We are currently heading in a great direction. We just need some revenue and/or funding to help it keep going. Here are a couple of other topics that we chatted about:

- Getting back to sales - we need to sell what we have

- Trying to use technology to help us, as we keep pushing forward

- Sales - It is just a game of numbers

- Teaching people some simple keywords and then point them to the quick search - keywords like: new, home, adv (short for advanced), all, last, prompts, and help. With those seven keywords, you can do tons and tons within the system. That's it, just those couple of keywords.

- Steve is watching some of the AI news... He is going to try to use it to generate some images and videos. He likes that kind of stuff. Things are progressing in leaps and bounds.

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.

Working on help files. Redid the classic quick search help file (click to view). Started back threading help files to AI quick search prompts. This means that we are adding a link with the prompt or keyword on the help file that allows you to navigate to that file inside the system. Going through a number of help files and adding nav help stuff.

Cory and I flipped over to do some clean-up for a client. We looked into an old bulk tool for cleaning up deposits (invoice payments that need to be deposited). Had to make a small fix on that but got it working. Then we reviewed some questions about vendor credits, vendor commissions, and how to distribute those vendor commissions and track what was given and to whom (payee/users who get the commissions). Talking about some backend accounting options. Talking about different ways to track things.

Working with cory. Looking at flow for the partial PO project. Talking about what to push live first. We may end up breaking the project into smaller parts and pieces. Bulk edit and bulk flipping PO line items. Auto filling in some sub inventory stuff, where possible.

Recording notes and paying bills.

Recording notes from yesterday.

Prep work for adding a personal setting to show/hide the AI agent. The main AI agent will be turned on/off up high at the corporation level. If an individual user doesn't want it, they could turn it on/off at their user level. Just in the planning phase of this project right now.

Getting back into the partial PO project. Re-reading some of the plans and looking into what it will take to get this going. Keep getting pulled off of the main project by the need to fix some stuff on sub inventory. There is a big pull there and has been for years. Anyways, went on a walk and tried to iron thing out and figure out a plan of attack. Recording some new notes and ideas on the project. More reviewing the project notes. Sent a text to Cory asking to meet with her to see the functional side of the partial PO project.

Recording notes from yesterday. Small to do list items. Transitioning between projects. Pointing Abby in a good direction on her text editing and graphic stuff.

Meeting with the Nxtlinq guys. It was just Thomas and me. We briefly spoke for a few minutes and then jumped off. I then went in and disabled the user access that I had given them to the data 20 box. We will give them a different user login. Light clean-up and then a small email with an update.

Jumped on the GoToMeeting session with Hamid. We were reverse engineering some different web pages and looking under the hood. He is a collector of sorts and had some questions about a site that he visits a lot. Anyways, totally different learning, but we spent the whole time looking at generated code (source code) and searching for small variables and key values. It was kinda fun... Not really hacking, but just looking around and seeing HTML, JavaScript, and CSS stuff. Interesting evening, but still learning.

Small spelling correction on the idea farming graphic. Cascading some small spelling changes. Recording notes from 10/21/25 to 10/23/25.

idea_farming_rose_analogy.jpg (1024×750) - Changed out the graphic for idea farming

Working with Bryan. We got him all setup with a VPN (virtual private network) and FTP (file transfer protocol) access to the servers. We talked about flow and some pros and cons to some of these pieces. We talked about security. He used to have access, then we changed servers. We then jumped into adilas and started working with the new AI quick search prompts. He was curious on the progress. He turned on the AI agent for his own corp. Light talks about direction and progress.

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.

Working with Russell. Abby was over at my house. We flipped from coding to graphics. Small art lesson to help Abby with some graphic ideas and such. Russell was working with some drawing tools and showing Abby some different techniques. Duper fun lesson. Ee then played with some older adilas interfaces and talked about what that would take to remake those using newer tech and newer tools.

Small note from Russell - You have to know how to break it down... If you don't know, you can't build it. We were looking at things and talking about how you would approach them, if they were a real project. You almost have to see the smaller pieces so that you can get into those harder projects. Once you know the pieces, you can then start building them up and mixing them together. Fun stuff!

Meeting with the Nxtlinq guys. Fairly quick meeting. Making some great progress. I reported that the multi-tenant options were available on all servers. I also reported on a number of new keywords and prompts. After the meeting, I spent some time and got one of the older accounts on data 20 up and running as a new test spot for the AI agent.

Working on more prompts, keywords, and search options. This was the process - build it out, test it, document it, repeat. Over and over again for a number of features including invoice sales reports, reoccurring invoices, statements, update inventory counts, reports homepage, and master time templates. Pushing through a few new prompts.

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 on help files sub inventory attributes and parent attributes.

Emails and checking up on the proposal/questions sent over to the Nxtlinq guys. Working on some code changes inside the system. Added a dynamic server name to be passed through the AI agent code. Went in and added seven new API sockets to be turned on through the 3rd party solutions page for adilas API sockets. Sent an email to the Nxtlinq guys with a small update.

Somewhat of a long and technical email to the Nxtlinq guys. We need to make some decisions on how to proceed from testing to a multi-tenant type environment. I ran through a number of questions and tried to provide some possible solutions. We honestly can go in multiple directions. Hopefully I said that in a way that it wasn't too confusing.

Small clean-up for the day.

Doing a few random things. Data clean-up for Sean and a client out of California. Reading through emails. Recording notes from yesterday 10/16/25. Lots of good direction and ideas. Including info on creating your own aliases and AI quick search prompts. Lastly, working on an email... started a draft for the Nxtlinq guys. I ran out of time.

Phone call with Steve after our AI meeting. Going over tons of ideas and options... Exciting times.

- On the 3rd party solutions page, add in the other API's that Nxtlinq may need to access their data. Do this all behind the scenes so that a user doesn't have to go in and turn any of those settings on. That way, all of these API sockets will be monitored and controlled via the 3rd party solutions channel.

- We can handle the user level permissions - meaning allowing a user to turn the AI agent on/off at will. The corporation may turn it on, but not all users may want it. Basically, the corp level will be the top level and the user level will be on an individual basis level.

- Earlier today, we were talking about subsets of aliases - Steve had the idea... What about multiple levels deep? Aliases of aliases of aliases... We can totally keep it all strait but what if a user does something all the time... What if the AI agent was able to make its own aliases for common tasks. Talking about predictiveness and interpreting input and intent - We even talked about slang or certain terms that may be used in different regions.

- "Adi go" - command prompt - We already have "Adi" as our little blue dog avatar (helper or mascot). Maybe using "Adi" as a command prompt. This would be similar to how smart phone users can talk with Siri or Alexa. Ours would be "Adi". Idea from Steve.

- Sell what we have

- The value of hyperlinks - mixing command line, Gui interfaces, web, and API - we are built for this

After Steve and I got finished, I was wrapping up for the day. I was really grateful that everything was going good, meeting wise, direction, etc. I was saying a little prayer and had a number of thoughts pop into my head. Call it inspiration, direction, or whatever. I'll take it and I love it! Here are my notes:

- On the user set aliases (making their own prompts), for the AI quick search prompts, what if we used a "#" (pound or hashtag sign) for all user specific prompts. That would not compete with any of our existing prompts. For example: #xyz or #something or #somethingelse... - we could even reclaim certain existing prompts by just add the hashtag in front of it. Another example may be... The prompt or keyword for clocking in/out has an alias of "my time" - what if a user wanted to use that for his/her own prompt for project time tracking. They could create "#my time" or "#time" and it would totally work. Even though both of those values are normal keywords by themselves. It could be really cool. Imagin a hashtag and at least one letter, more if needed. Super simple for quick speed.

- Be able to build and show the prompts and what they are tied to. Simple user interface to setup and maintain their own AI quick search prompts. Very similar to the icon payee top links in the snow owl theme, but even more, and easier to get to... they would be clickable and usable in the AI quick search text fields. Anywhere in the system... That would be super cool! Even better than the icon payee top links (existing link building or special button feature inside of adilas right now).

- What if we used the "go mode" page (new AI quick search prompt page) to show their own prompts or even a fracture type interface - simple tiles and buttons - (small sample image)

- When creating your own buttons, be able to name them, color them, set an icon, a link (advanced - they have to know the URL or web link) or a simple quick search prompt. Maybe even tie the user created prompts and buttons together or make it a dual-purpose database action. Some of the buttons may need to open up a new window and some (most) will just jump to that new page. Just some ideas.

- What about being able to tie multiple prompts together in a mini list, process, or mini prompt recipe? That would be super cool. Imagine something like this: start cart, choose customer, show x or add y to the cart, simple cash checkout - simple English or natural language instructions and the system would help them walk through that process... kinda hold their hand. It won't just do all of them at once, but it will know what the process should be. We could easily create those one-to-many relationships and virtual steps or phases of the process. Just for fun, it makes me think of a data assembly line or assembly line for data. Cool stuff!

- Along this multi-prompt line... We already allow for duplicating invoices to the cart. What if we used a template type scenario and setup a master invoice and then were able to duplicate the exact thing in one click. If changes are needed, they could modify it, but cut out all of the searching and such. What about a partial duplication process... once again a mini recipe for certain steps or data assembly line controls.

- We have a page inside the current system called "my favorites". It currently has a number of buttons on that page. This was one of my todo list notes from a couple of days ago... It totally fits here (see below).

todo: Get back to the ideas of the my favorites page inside of adilas... it got taken over and a bunch of hardcoded buttons put on it. But it does have some potential. See this help file - help.cfm?id=418&pwd=favorites - or visit this page - top_secret/secure/my_favorites.cfm. Added this note on 10/14/25 - it would be so cool to let the users choose anything that they want in the system and then organize it and name it. Cody Apedaile started a draw your own interface (but got pulled off of it for budget reasons). Anyways, the goal is still there to help create your own interface and organize your own buttons as you see fit.

-  Super simple, using old school tech with a modern or new school flare... it will work

- What about helping with memory... We could help hold small comments, save/hold this or that, or even helping to string things together... Maybe help them with their memory... It won't tax the server very hard (store simple things in session - per login). Imagine small AI quick search prompts like clear memory, save to memory, view memory, etc. Super simple stuff. Use JSON storage if saving memory in a more long-term fashion. Simple interface to get things in/out of memory and even use the AI quick search field to help. That would be cool.

- This may not be ready yet - but what if we record and then help them go from one thing to the next to the next... simple session memory with a display... If we know a series of AI quick search prompts... It wouldn't be that hard to display something with a next button, help them step through the process.

Meeting with the Nxtlinq guys. Going over progress. Then talking about multi-tenant options (settings, domains, corps, keys, secrets). We setup some small dates and goals to get an MVP up and live. Other small talks on different subjects. Fairly quick meeting.

Working on help files and AI quick search prompts. Got on a meeting with Steve. We went over a bunch of things. Things move so fast sometimes. We were talking about where we are heading, MVP levels for the AI stuff, questions about making the AI agent multi-tenant and able to handle different domains, corp id's, keys, secrets, etc. We spent a little time, and I was showing Steve what this can do (current AI quick search prompts), small dog and pony show, bouncing around, looking things up, showing some future plans, and making some decisions.

Here are a few other notes from our meeting:

- We already have so many AI quick prompts and keywords. What if allowed our users to setup and create their own aliases or mini prompts? I'm kinda cheating here... It is now hours later (the next morning, when I am recording this). But, we came up with some good ideas and had some inspiration on this topic later that evening (last night - click to see EOT # 12392 for more info).

- The value of simple text look-ups vs straight AI or Id based look-ups. You have to start somewhere, but ideally, you get it tuned into just normal natural language stuff. The computer wants the Id's but normal people want to speak their normal language. Find that happy middle ground or even favor the human side... a bit...

- If we go more to natural language prompts, if a decision can't be made, provide roll-over fail safes - options if things don't work out.

- We are seeing at least four levels of permissions right now. They are corp level (world level), group/category level, page level, and user level.

- In order to make the AI agent into a multi-tenant agent, it will need a way to dynamically deal with domain names, sub domains, corp keys, corp id's, and users. I will try to put some things together on this topic.

- Steve and I were talking about multi-threading and other threading questions... keeping things straight from server to server and between users and users. In this case, for AI, between serves and AI agents and AI agents and users within certain corporations. 

Working with Russell. Talking with Chuck for a few minutes and catching up. They, Russell and Chuck, were on a previous meeting. After Chuck left, Russell and I did a little flashback and were talking about CSS and modern tech. Sometimes it is hard to try to keep up with all of the changes. The old basics are still super important. A developer needs html, JavaScript, CSS, SQL, and some kind of backend technology.

As we were working today, we were talking about exposure, in development, leads to some new ideas and knowing what is possible. Not all exposure is good, but certain kinds of exposure can really help you imagine what is possible. Once you know that, it isn't super hard to then go try to figure it out. Granted, the term "isn't super hard" is relative...

We did some training on the VS code interface, some speed tips, some Git tips (code repository and branching stuff), and then spent some time tweaking a little bit of adilas code. We changed some older hardcoded values (in the CSS) to use flex box instead of older direct positioning. Good little training session.

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 on help files for sub inventory attributes and templates. Also started to work on help files for parent attributes and high-level templates.

Small data clean-up for a client. I had some old code but had to tweak it a bit. The new request was specific for just certain changes.

A couple of sessions today. Total time was just under five hours. Here are the notes from the different sessions.

Organizing my to do list. Back working on new AI quick search prompts. Started adding a number of new part/item prompts. These are things like printable lists, grouped inventory, global mark-up, view ecommerce items, and find & replace functions. Updating help files for ecommerce settings. Working on adding things like part categories, sub attributes, and parent attributes. Some of these still need some help with their help files. Once that is finished up, I will provide the correct documentation and let our users know. Currently, a couple of those are hidden (for now). I will expose them once we fix the help files.

Working with Abby (my daughter). Going over some ideas for projects. She is going to do some graphics for some of our projects. She is hoping to do 15-25 hours a week. I will pay her for now until it gets approved from adilas. We went over what she had done, the last time that she worked with us. She is excited and has some direction. We'll see where it goes. I'm excited to see what she comes up with. She is very creative. We spent some time going over timelines and versions of adilas. Abby is going to make up some graphics to help show some of those things and how the development story unfolded. Should be fun.

Recording notes from the day. Busy day. There are a lot of moving parts and pieces to this game we are playing. Very interesting... :)

Meeting with the Nxtlinq guys. They have automated and worked with 350+ tools to date (adilas AI quick search prompts). We were talking about testing. Going over the auditability (following the audit trail) and tokenization tracking. We want it to be more loose and they want it to fully follow full block chain tokenization stuff. Functional testing vs real user experience testing. Talking about really beating things up. We are trying to get things done within about a week as far as all of the tools. We are shooting for sub 500 total tools. That means I have another 100 or so still to go before next week... I hope I make it... :) I've got a list, a plan, and a bunch of notes... What I don't have is time.

Making a plan. Went through a bunch of menus and found 30 or so homepages or sections that I want to add to the prompts list. Started working through my small list. Ended up doing some special coding to allow a vendor/payee id to be assigned directly to a new PO right from the AI quick search prompts. That should help out the Nxtlinq guys. Steve told me earlier today that they were looking for something like that.

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.

Quick meeting with Steve to show him some of the progress on the new prompts and actions. He had some API questions, and we pointed him in a good direction. We were talking about the value of the URL crafting and mini API stuff. This has been a big push for us. We are excited to see if we can gain some ROI (return on investment) with these new features. We are also excited to see how our users and the adilas community take to these new changes. It is a small paradigm shift for us. That's exciting!

After Steve left, I started making a to do list, emails, and light planning.

Six different sessions throughout the day. Starting at 7:30 am and ending around 1:15 am (on the 14th). Long day. Here are a few of the things that we did.

- Working on help files and emails.

- More work on help files and navigation options. Recording notes from Saturday, big work session day. Back rolling through the additions, changes, and updates for the AI quick search prompts. More navigation and help options. Trying to expose some of the different resources like switching corporations and the developer's notebook.

- Working on new prompts for the API sockets and other key pages. Spending some time in the invoice and deposit sections. Things like apply payments, show invoice payments not yet deposited, sales tax reports, etc.

- Adding in a new payee lookup for the mini API, at Matt's request (from Nxtlinq). Started working on the new code.

- Working on some new code for a vendor lookup and an employee lookup for the mini API. Working on the code, testing, and pushing things up. More work on documentation. Then went to all servers and pushed up new database records for help files (10 new ones) and new permissions (7 new ones). Did that for all of the servers. Email to the guys at Nxtlinq with some instructions.

Recording notes. Working on new modal popup to help with the normal quick search that shows up on every page. I want to help people get to the prompts.

New AI quick search prompts, options, and keywords. Doing some more detailed ones and ones that we had missed. Kinda filling in the gaps a bit. New nav options, new help options, and other values. Ran out of time, didn't push up the new code. It will be good when we push it up.

This is more for me, but in a way, I'm also hanging out some of our dirty laundry (sections that aren't fully done yet or that we are still working on). It is probably good for me. I don't like doing that. I like it to be fully done and ready (ish) before pushing up live. I saved everything to a new code branch. I'll merge it in on Monday. Good work session.

Looking into ideas on the reverse shopping cart for specific items for a vendor. Did some brief research. It sure would be nice if we could use existing tools to search for PO items. Then once they show up, be able to do the reverse shopping cart stuff. This feature has been requested many times, clear back from 2009 and 2010. Maybe a switch or something to help use the same pages. Started looking at other bulk tools. Small tweak to the bulk transfer parts page. I was checking it out and then looking at other bulk tools.

Recording notes and looking at some JavaScript and what it would take to make a few changes on some pages (math calculation stuff). Then working on some new AI quick search prompts. Light code and logic refinements.

Working with Russell. We jumped in and played with writing ColdFusion in VS code editor. We then spent some time inside of Chat GPT playing with snippets and converting Sublime Text snippets into VS code snippets. It went pretty well. I ran out of my free version (number of requests) for Chat GPT. I may need to get the paid version here soon. After that, Russell was showing me some of his AI image generation stuff that it was doing. We were playing with some images and then having it make some different versions of the images. Fun stuff. Mostly an exploratory learning session today. I enjoyed it.

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.

Recording notes from the past couple of days and doing emails. Paying bills and recording expenses.

Opening up the time id in the edit mode for sub dates and times. This is in case the sub time record gets put on the wrong main element of time. This was a request from a potential client. I thought that it was a good idea. I could see how this could be useful.

Spent some time getting back into the partial PO project. Looking into tracking PO back orders and partial payments or partial receiving PO line items. I'm glad that I wrote some notes (almost 20 pages). It's been almost four months since I was on this project. It took a few minutes to get my head back in the game.

Helping to open up the date field on vendor credits. It actually took a bit of work. I thought that it would be pretty easy, but it had some hidden catches. Anyways, we got it done. This was a request from Shari O. and Cory to finish up vendor credits and other special account transactions.

Meeting with the Nxtlinq guys. We showed them tons of new progress. We have really spent a ton of time in there (in the AI prompts and keywords) prepping the model. They had a couple of questions, and we had some good conversations. Bryan pitched a cost sharing model and then we got into some questions about the future of AI and where we see it going. The last 15 minutes or so were Steve and Thomas going over lessons learned and what each sees as part of the future.

Talking to Bryan about AI quick search options. We went over some vision stuff and where we are wanting to go vs where we are at. Then we switched over to talking about changing out our prices (lowing them) so that people will buy more. He was showing me some examples: Say we charge a $100/hour or $150/hour, how many hours of custom programming would we get? What if the price was $50/hour or $65/hour, what would that look like? Bryan was showing me some potential curves and what some of that might look like. Fun ideas. We may want to play with this and see what happens. Not everything will go this way.

After the meeting with Bryan, I switched over and did a multi-hour session on AI quick search prompts. Adding photo and scan prompts to all of the main sections. Doing some crisscrossing of the different sections. Switched over to other main navigation pages and their prompts and shortcuts. One thing that was different with this section was, I would code it, test it, create the prompt documentation, add it to the help file, push it live, retest it live. I wasn't just coding or just doing documentation. I was doing all of the pieces, then repeat. Small little sections but finishing them up. That was kinda fun. I never let it get out of balance, I would code, test, and make sure that the documentation was there. Good little session.

Working on new AI search prompts and actions. Going through Bryan's list and adding code, prompts, and help file entries.

Reading over some notes from Bryan. He was doing some prep work on the AI prompts, keywords, and options. Small changes and cascading changes to prompts and help files.

Formatting a number of AI quick search prompts. Worked on the stock/units, elements of time, vendor/payees, and VIN/serial number prompts and keywords. See this help file for some of those pieces.

Quick meeting with Bryan. He was doing some research for me on new AI quick search prompts to help round out the navigation section. He passed me over a bunch of things via the GoToMeeting chat. I'll try to work on them before tomorrow evening, meeting with the Nxtlinq guys.

Recording notes from 9/25/25 to 10/4/25. I was way behind after going to the Adobe ColdFusion conference. Feels good to get caught up again.

Working on tightening up the logic on the employee/user quick search. Started to record the employee/user prompts and keywords into the bigger prompts help file. Finished up the help files (for now). Had to combine four help files to fit it all in. Sewing... but no needle and thread... digital weaving and sewing.

Working on prompts and documentation for employee/users. Another long session. Click here to see some of the prompts, keywords, and options.

Bryan jumped in and he, Steve, and Alan, were talking a bit. They were talking about AI quick search stuff and then some sales. Steve and Alan had to take off. Just Bryan and I were then working on stuff. We made some plans, and Bryan is going to help me try to finish up some of the AI quick search prompts and such. Small work session. Making some plans to divide and conquer.

Meeting with Alan and Steve. We were talking about some new accounts and also helping with the accounting for these accounts (offering other services). The goal is to help fill in the gaps on the accounting side of things. Let them do what they can and then we fill in the gaps. Steve was reporting that a client was saying that they were happy to find us. They didn't know that we existed. Small talks about QuickBooks and how many people use them.

The main meeting was between Alan and Steve. I was there, recording notes, chiming in, and doing a little bit of driving (clicking on pages and reports). Here are some of my notes... Instead of being sequential, they are broken down into things that Alan said and things that Steve said. Good meeting.

Notes from Alan:

- Shifting our mindset a little bit

- What is working and what is not working

- Skating to where the puck is going to be vs where the puck is at right now

- Being proactive in our approach

- Running to the fire vs doing what is needed in the long term

- Say a budget of 30 hours - 15 hours working on big projects or using that time to do some prospecting, 5 hours communication stuff (emails, texts, recording time), 5 hours bug fixes, other 5-10 hours maybe using AI to help clean-up the system or refactoring older code

- Maybe some new dashboards

- AI is amazing when it works

- Using AI to help us modernize our interface

- Talking about time - not too rigid on timelines - we want to finish things... - everything takes time - we never tend to get to things

- Taking about proactive maintenance

- He (Alan) sometimes struggles with communication

- It is easier to just knock out projects at times, then talk to people and/or get distracted by different things

- Code fits into multiple areas - paid, fun, wow factors, etc.

- Taking time to work on their own projects (one of his wishes and/or dreams) - basically either continuing education and/or fun projects (what can we do to make it better) - fixing things that bug us (as devs) - making things easier for others

- Alan's been working on some refunds (card pointe and clover - merchant processing stuff)

- Talking about dreams and what would that look like

- Stuck in between what we want and what we have

- Fearing the slowly sinking into nothingness (an analogy about adilas - like a ship)

- Running in circles

- Chasing a ghost (phantom look and feel)

- Alan asking about the goal with the investors

- Talking about the size of the client that we are chasing... how big of a fish are we looking for? - we may be trying to get too big - who are we? can we handle that size of a fish? - what is our goal and how will we get there?

- Alan had some questions on pricing and what does our ideal client look like? how do we find that person/company?

- other sales related questions - how do you judge a company, size, needs, etc.? - what about customizing things? good or bad? - we don't have a big huge team - we have been burned with merchant processing and other 3rd party solutions

- Talking about adilas and where we are at financially

Notes from Steve - once again, not sequential, but just things that I wrote down that he was talking about.

- Learning to adapt - using AI - it is going so fast - we need to be in that race

- Talking about databases - yes, they are still really needed (good multi-relational databases)

- Steve was showing some of the AI stuff in his demos with some potential clients - that has been going well

- We are really bad at estimates (we have had our lunch eaten time and time again)

- Talking about client churn and companies falling off of the system - pretty normal - we are actually doing pretty good.

- Looking around in the system a bit

- Maybe going with $100/hour for development work and $65/hour for setup and oversight

- AI has sped up Steve's work - he is learning along the way - guiding it along - taking in small sections at a time

- Steve was talking about time budgets and not getting too tight on certain time blocks

- Some of Steve's projects are tiny and fulfilling - inch by inch and little dabs

- We need some firewood (sales and revenue coming in) - we are low on revenue

- Steve thinks that Alan needs a break - maybe getting out there and talking to people about what we have

- Sean has been helping with deployment - Cory is doing more client work

- Steve loves to figure out the angles (problem solving for clients and what they need)

- We have an MVP (minimal viable product)

- Finding people who are happy with what we have

- Investors tend to look at the reoccurring revenue - we are looking for an angel type investor who sees the vision and value and says, yes, let's push this thing forward

- We have gotten it this point without a sales team and without marketing... imagine what we could do if we get that going

- Big fish are expecting to be courted (wine and dined)

- They, our clients, have to be big enough to afford us

- Shooting for $400/month

- No big fish and no little fish (super little) - being able to offer our services and they pay for it

- Learning to say no

- Most companies pay around 3% for merchant processing... say we go less than that - say 2% of monthly revenue - start higher and then go down if you need to - if you are dealing with a big chain, we may have to negotiate with them

- Steve talking about numbers... say we have made $10Million from paying clients. If you take number and divide it by our total client count over the years, for us, it is around $12K per client

- We should be selling stuff - that is a super high number at around $12K per client

- Steve would like to get 5-10 new accounts a month

- Offer our other services - activation, deployment, and servicing the account

- We have done a lot of stuff for free... we need to change that

- Sales - can be broken down into three main things... they are like, trust, and respect

- Just tell everyone what you do (from Kiva)

- Do they have inventory? Do they need to track stuff? Great! - Nobody does inventory management like we do - QuickBooks is sending people to FishBowl and Shopify

- Being outside and out and about

- Helping people with their over needs - these are things that they can't get to - their over needs

- We could offer lots of other outside or inside services - we are $65/hour for those services

- We either do it or we don't do it, go to the next

- Stay on the good side of town

- On custom code, they, our clients tend to really like to dream and can't really afford it - we have been burned on doing too much custom - we are $100/hour, paid weekly, if yes, ok, let's go

- The bigger the lift, the bigger the pain (time and money)

- If needed, we could move forward with bigger teams - like a lawyer, we could work off of a retainer

- We can get lost in "custom world" or "custom land" - we need to steer clear of major custom

- Looking for happy clients - we have a bunch of clients who are not calling us, they are happy

- Trying to stay away from black box stuff - building settings or small bridges

- Being able to remove columns on reports (fracture or adilas lite stuff)

- Simple website stuff (easy hosting) - simple pages and some settings (landing page, contact us, and about us, plus adilas ecommerce)

- Trying to be around $1,000 and then a monthly (have to have an adilas account)

- Taking things off of their shoulders - they are already spending tons for all of these other services (mashups)

- Maybe look at some sport teams - other team sports

- Not trying to sell things, just doing some exploring

- Talking about sales and/or trimming things down a bit (financially)

- We may to stop or curve the development and really focus on sales

- Talking about the AI quick search - going beyond normal API endpoints (URL crafting, AI quick search, mini API, etc.) - Steve jumped into the test site and was showing Alan some of the AI agent stuff that we are working on.

Overall, a great meeting. Some good takeaways as well. Good stuff!

///////////////////

Bryan ran this page through AI and got the following summary back

AI Summary:

Sales & Strategy Meeting Summary

Attendees: Alan, Steve, Brandon, & Bryan

Meeting Overview

The discussion focused on expanding Adilas’ service offerings, improving operational efficiency, refining sales strategy, and leveraging AI to modernize both processes and the user interface. The team emphasized the need to balance custom work with scalable solutions and to strengthen recurring revenue and client engagement.

Key Discussion Points

Alan’s Focus

• Encouraged a proactive and forward-thinking mindset (“skate to where the puck is going”).

• Suggested a structured time allocation for projects, maintenance, communication, and AI-driven improvements.

• Emphasized AI modernization for the Adilas interface.

• Advocated for proactive maintenance and allowing time for innovation and internal improvement projects.

• Discussed defining the ideal client profile, pricing models, and balance between customization and scalability.

• Highlighted challenges in communication and prioritization but emphasized long-term goals and clarity of direction.

Steve’s Focus

• Stressed the importance of adapting quickly to AI and new technologies.

• Acknowledged issues with time estimates and scope management.

• Proposed pricing structure:

  • $100/hour for development

  • $65/hour for setup/support

• Highlighted need to increase recurring revenue and attract an angel investor aligned with Adilas’ vision.

• Advocated for focusing on sales growth (targeting 5–10 new accounts/month).

• Emphasized charging for all services—move away from unpaid work.

• Encouraged avoiding excessive custom development to protect scalability.

• Recommended prioritizing sales and marketing efforts to drive short-term revenue.

Action Items

• Define the ideal client profile and align pricing accordingly.

• Increase focus on sales, marketing, and client outreach.

• Use AI strategically to streamline operations and modernize the platform.

• Improve internal communication and proactive planning.

• Explore investor options and sustainable growth strategies.

Checking emails and light research. Small AI quick search changes. Reading over notes from the Adobe ColdFusion Summit Conference from last week. Scanned my notebook and made a multi-page PDF file of my notes. Recording other notes from 9/22/25 to 9/23/25.

Documentation and then working with Bryan again to get his new code implemented into the system. Lots of back and forth, testing, documenting, and pushing up code.

Meeting with the Nxtlinq folks. We presented on what we have been doing. I showed them some new stuff and all of the new prompts and documentation. Hopefully it is helping them out. I am happy with it. The new prompts are already making my life easier (I have been using them).

Working with Bryan to get his new prompts and AI quick search options live and online. He did quite a bit of work. We got together to do some work. He is going to go back through some stuff and do some clean-up. We will meet back up and try to merge and push things up live.

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 Bryan on his new keywords and prompts. We also did some work on allowing for the calculate payroll to be used through the AI prompts and keywords.

Reviewing the document that Suzi made for some simple step-by-step instructions. Looks great! See attached for the file. Switched over to doing more documentation of the AI quick search prompts, keywords, and options.

Phone call with Alan going over plans and ideas. We are hoping to get a meeting with Steve setup for Friday of this week.

Speaking with Steve about AI security. We then started talking about possible options and where we are going. Talking about tracking time and communications. Small history and waves of selling what we have... Steve going out and selling (software on the internet - cloud), Cannabis space wave (we had some internal struggles - who would be willing to play), Steve is seeing the third wave as the AI wave. Good phone call.

Working with Russell. Talking security with Russell on the AI quick search. Talking about customer data, employee data, banks, financials, and tons of other data. After that, we switched over to training on CSS.

Meeting with the Nxtlinq guys. Steve, Josh, Bryan, Matt, Roger, and Vincent were on the meeting. We showed them some progress and sent them over some help file links. Mostly what we were able to show them was the new documentation stuff.

One thing that Vincent said that I liked was "Remove the friction". That should be our main goal in this venture. I liked that saying. If we could remove the friction on other parts, things would be even smoother. Without getting too technical, you have to have some friction, but making things smoother would be a plus. There is a balance point.

Working on AI quick search documentation for options, keywords, and prompts. Had to combine two help files in order to get all of the data that we want and need. Here's a link to the help file. After that, jumped on a meeting with Bryan and Steve. Got new code from Bryan and merged it into master.

Quick update meeting with Steve. Showed him some of the progress we are making. Briefly showed him a few updates. Sent out a couple of quick emails and doing some light follow-up.

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.

Going over the plan for receiving partial PO's

Meeting with Cory and Steve. Going over projects and timelines. The time part (how long things take) is one of the hardest things to control. Lots of unknowns. We then went over some other questions. Lots of 3rd party solution stuff. Our clients want that stuff, but it takes time. Tons of little mini questions and small tweaks that are needed.

Working on documentation. Pushed up new code and did some work on the AI prompts and keywords help file.

Working with Bryan. He is coding some of the nav options for the AI quick search. He is working on the employee/user options. We went through a few of the new prompts and I answered some questions. He is going in a good direction. We will meet up tomorrow at 3 pm to see what we can mix together. I am hoping to mix what I am doing with what he is doing - all in the AI quick search stuff. After Bryan left, I started working more on documentation and such.

Here is a link to the AI quick search prompts help file that I am working on.

Documentation and recording notes for keywords, options, and prompts for the AI quick search. Got a small PDF from Suzi with some step-by-step instructions. I briefly went through it and sent her back some quick feedback. Great start, just need to tweak a few things. Jumped back to filling in information on the AI quick search prompts page. Pushed up new files. It is rough, but we got small descriptions on all AI quick search prompts.

Working with Bryan on AI prompts and keywords. Small Saturday work session. We reviewed our notes from yesterday. Made a few new notes and pushed them up to element of time # 12286 in the shop. We then did some pair programming, and I showed him what we were doing and what we were working on.

We started coding some things for employee/users and payroll. Good back and forth training and working session. Towards the end of the session. I committed my files and pushed them up to bit bucket. Bryan then pulled them down and started to work on things. We went through a few of them together and setup a time to meet on Monday. He is off to the races. We will touch base, but hopefully he can keep pushing things along.