Meeting with the Nxtlinq guys. They were showing us some new updates and how the system (adilas AI agent) is able to ingest uploaded files and how we can edit the main context window (backend admin stuff). After the Nxtlinq meeting, I jumped on again with steve on our GoToMeeting session. We were talking about training it (the mini model) on core concepts and creating a stable foundation. We are going to be using help files to store global context (for now). Eventually, we would like to make a new database that will be just for AI chat, learning, and context on multiple levels (global context, industry specific context, corporation or world level context, and user level context). Steve will be working on a side AI agent (testing things through an API connection). We are trying to get the best options available.

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

Working with Hamid. He was trying to get his old portfolio website up and live again. We had to fix some URL's and some paths and such. He was having fun getting things back working again. We had to flush his cache a few times to make everything show up.

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.