Emails. Small data clean-up for Cory and a client who was doing some practicing before going live.

Working with Russell on some CSS training. We spent some time working with the box model and playing with content, padding, boarders, and margins. We then played with specificity and playing around styling with different elements. We then went into some OOP (object oriented programming) concepts and looked at some code and samples. It is important to think about everything as an object. That really helps.

Recording notes from yesterday and today.

Working on the AI options and prompts for the AI quick search. Had a good 3+ hour long session working on the search action page and refining things.

Later on, we jumped on a meeting with the Nxtlinq guys. Going over progress and answering questions. They are wanting more options, prompts, and documentation. They are doing a great job. Some of their questions will require Steve and I to get together to make some plans. We are all making progress.

On a quick Zoom meeting with Cory. We were looking into a 3rd party solution and trying to get it ready for one of our clients. We jumped into some code and did some light research. Cory took some screenshots and will send an email out to the 3rd party to see if they can help us with the integration.

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

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

Working on new AI options and prompts for the AI quick search. Started working on new quick search main categories for AI, images, media/content, navigation, cart, and help.

Text messages, reaching out to a client, then typing up some directions for Suzi to help us build some scenarios and user stories for the AI agent to follow some directions and instructions. Other emails and trying to do some follow-ups. Lots of moving pieces.

Demo with Calvin Chipman to go over some AI technology that he is using and working on. We jumped on a zoom call. He is thinking about an exit strategy and trying to jump in on the AI race while it is hot. He is using an AI agent to go over dead or old leads and trying to reconnect with some of those people. We did a demo, and he will send me a video. He is using his Gmext product (group mass texting) to help send out those SMS messages (texts for a chat bot). Fun little fusion and combination and what he is doing, what he already has, and where it could go. I enjoyed the demo.

Emails and then a phone call with Josh talking about AI agent options. Looking for some scenarios and user stories to help with flow. POS or shopping cart stuff.

On a GoToMeeting session working with Bryan to help him get lined out on a custom data upload project for a lady who does candy vending machines.

Small fix for Cory. She sent me an email that was reporting some CSS being shown at the top of a page. It ended up being that one of our developers was not allowing output and was suppressing whitespace. It ended up not using some custom CSS that we had wrapped in cfoutput tags (Adobe ColdFusion stuff), in order to pull in special corp-wide settings, colors, and look-and-feel settings. pushed up new files to all servers.

Small updates for the SpringBig loyalty points. We have a future client (hopefully launching this next week - going live) that is currently using them to track their loyalty points. All of our other clients we have transferred over so that they are using adilas loyalty points. Anyways, it has been a minute or two since we had to do anything with SpringBig. Just circling back around to make sure that everything still works. Did some research, added some new code (copied from another page), and then sent a follow-up email over to Cory with some information and instructions.

Recording notes from 9/12/25 to 9/13/25.

Recording notes from earlier this week 9/9/25 to 9/11/25.

Went over to Brian Stewart's house to go over some AI consulting. I paid Brian to help us look into some options for how we could use AI inside of adilas. We met up and he had a small questionnaire that we went through. Lots of talking about this and that. He then showed me some of his proof of concepts (small mini projects that he has been working on).

Next, we switched gears, and I then had him go into the system and look around inside of the adilas system. This was his first time ever seeing it. Lots to take in. We ended up in a small demo site and had to configure a bunch of things. It wasn't setup very well. Anyways, we did a small demo and it kinda overwhelmed him. He was able to see where we could use some AI help and hopefully to help simplify the setup process and the training. All and all, a good session.

Small fix for Benning Construction. They only wanted certain checkout fields for the mulligan stuff (golf tournament - custom ecommerce checkout). Ended up doing the same thing for their donations to St. Jude Children's Hospital. Small checkout changes.

Working on the AI quick search and logic for the search action page. Added in a number of aliases and worked on -key:value pairs for the customer lookup functions. Making good progress.

Meeting with the Nxtlinq guys. They are trying to streamline things. Removing user friction, less logins, less security checks, etc. The also changed their main permissions and sub permissions. If more are needed, we may add an advanced mode or deeper permissions. They are getting faster on the UI/UX. They reported on some changes to the voice feature (microphone). It is able to remain active vs closing right after usage. We may need some more real-world testing to see what works best. After the meeting, I sent a quick text to Steve to fill him in on the progress.

A few different sessions throughout the evening working on changes for Benning Construction. They wanted a new item for their charity golf tournament (custom ecommerce site). They want to offer pay-for-mulligans for the tournament (pay for a do-over shots or second chances). They are going to let them, their participants, buy as many as they want... kinda funny. $25 per mulligan. It is for a charity golf tournament (just for fun). I added new item category, new images, new item, and turned things back on for the ecommerce website.

Meeting with Hamid. We did some catch-up and then jumped into CSS. We are going over some course files and small practice stuff from a Udemy course. We are somewhat co-working on the practice files. We will do things, talk about them, and then go in and play around a bit. We are then sharing what we are learning. That seems to help both of us get a lot out of the practice sessions.

Working more on the AI quick search. Created a new help file to list out options and AI prompt helpers.

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

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

- Project overview hub - Adilas ecosystem

- Ambitious roadmap for next generation SaaS map

- Clean, modular, teaser, further explanation

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

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

- Technical depth and community

- A vibrant hub for

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

- Grow into a dynamic dashboard overtime

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

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

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

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

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

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

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

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

- Vision - building a sustainable interconnected world around it

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

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

Working on AI options and prompts. Good long work session. Did all of the old quick search options and tied them into the new AI quick search. Trying to define all of the existing routes, what help files go with what, new simple text options, and paths. Lots of URL crafting and updating the AI quick search. Pushed up the file to do some live testing.

Got an email from Sean with some data that needed to be tweaked and altered for a client. Working through his list and doing some clean-up.

Working with Russell. Talking about video streaming options. We may need to look into some pay for streaming services, build our own media player, share links from google drive. Talking about plans and cost/benefits analysis. Russell is trying to get me some exposure so that I have seen certain things and know about some of the new coding options and practices. Exposure allows you to change when you are ready. We then switched over to training. Going options and making snippets inside of VS code. We worked on some CSS training.

Emails and a small fix for a client and their custom ecommerce site. They wanted to show a notice that online registration was closed for a charity golf tournament.

Meeting with the Nxtlinq guys. They were showing us a demo of what they are working on. More usage of the natural language and then converting that into options and prompts for the AI agent. Cool stuff. They had a couple of other questions, and we said that we would provide some user stories, scenarios, and requirements for the cart. Once that is done, we want to get a full sign-off on the cart functionality before rolling into the payroll functionality. After the meeting, I did some light clean-up of some of the records (customers and customer contacts) and sent them a small follow-up email.

Working on more AI options and prompts. I have a small list that I would like to add and make happen. See EOT # 12286 in the shop (private).

On a meeting with Steve. We went over the adilas mini API and the new AI filters (sub filters within the main filter). We then talked about some proposals. I was pitching for some guys to help us out and work on specific projects. There were three code masters (Calvin, Brian, and Cody), maybe give them each 1% of adilas, plus $20K to cover (3-4 months). Just some thoughts. Steve wanted to know what they would be working on. I showed him the ship A MVP list that I have. Talking about how AI can help with training. That would be so awesome. Going over adilas lite and I showed him that we have the first 4 done. We also set a rough goal of putting adilas, llc percentages up for sale as of October of this year. Trying to generate some capital to keep pushing things forward. Other talks about projects and AI stuff.

1) Add a box for digital signature on the invoice

2) Add a setting so that when you search a customer by these page settings: https://data4.adilas.biz/top_secret/secure/mini_scan_cart_customer_search_action.cfm?bName=Blythe

or these page settings:

https://data4.adilas.biz/top_secret/secure/customer_search_action.cfm 

the inactive customers don't show up

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

------ start - ai options and prompts -----

done - build a function to pull out sub filters - pass in the whole string and what we are looking for. return the trimmed value.

- make a new help file with everything all listed out... help ai know what to do.

- url help... search_action.cfm?aiSearch=[prompt]

- mini api help - web/adilas_mini_api_calls.cfm?useCorpKeyId=[]&mode=[]&aiQuickSearch=[]

- samples - expand as needed

- calls and actions to the url's - double thread, simple response, stupid simple - maybe out in web or public, predictive level, show subs, mini async calls, predictive material to work with, show all categoies, show all items under that category, same with customers

- cart stuff...

- items by vendor [] ai quick search and mini api

- items by category [] ai quick search and mini api

- my cart favorites - expand when ready

- edit cart line [], adv edit cart line [] - when looking up, remember line sorting and lines with 0 qty (skip)

- invoice mini [555], invoice mini last, invoice mini max

- invoice max

- invoice edit main []

- invoice edit lines []

- customer log []

- credit card checkout (checkout credit), cc checkout, external cc checkout, maybe spell it out as well

- on account or payment on account

- loyalty points

- gift cards

- cart groupings (sorting things)

- cart stuff - remove line [], change qty [], cash with change due, adv checkout, start cart for 5555

- classic cart settings, mini scan cart settings, view classic cart, view kush cart, view mini scan cart, deliver options, split cart, bulk edit line items, save cart, save quote, save as new quote, refresh cart, choose subs, add sub inventory with a quantity, auto open next sub package, cart as a whole discount, show discounts, other special cart functions... look them up and add items

- help all, help [], help -title:[], help -main:[]

- back, back [], forward, forward []

- bank home, bank running, bank reconcile, bank bulk verify

- developers notebook [] - expand when ready

- my home or just home

- gps core

- interactive map

- items by vendor [] - ai quick search and mini api

- items by category [] - ai quick search and mini api

- mini calendar

- ecommerce settings

- email settings

- media content [] - - expand when ready

- news and updates

- my settings, my profile, my password, change password

- homepages [] - expand when ready - this could be a big section

- a/r's, a/p's, payroll, fulfillment, settings, cultivation, production, back orders, special accounts, adv exports, reoccurring invoices, go through permissions and pages - expand

- chooser

- corp admin, corp wide settings, admin corp wide settings, corp look and feel, corp stats

- history home, history [date]

- switch corp, switch corp [corp name]

- my favorites

- p&l, p and l, profit and loss, income statement, adv income statement

- page level actions... submit, select, select option, tab, shift-tab

- public shortcuts (corp id 7 simple prompt) - not sure what this means... it was part of my notes. maybe think on this a bit.

- bulk tools - expand as needed - define as needed

- labels - expand

- existing normal quick search options - see search action or help file

- edit main, edit lines, verify, history, add photos, add media content, add payment, edit payment, printable, etc... normal actions per section

- duplicate time, working with time, add sub, add flex grid, add limited flex grid

- for me - if they are already on an existing main player... maybe remember the type and the id... then the other edit main, edit line items, history, etc. will play through better. help it remember where it is or what it is dealing with...

- for me - change the options and prompts to an accordion style page - printable list - translate or interpret language - also make a new help file that is public facing

- take time to record what is possible... help train users and ai agents - think the value of education

- add links to the ai quick search from the main headers and chooser page

- last [count] - for example: customer last 10 or invoice last 25 or po last 5

- stats - use this to get basic stats for a section - for example: customer stats, invoice stats, po stats, item stats - maybe even some keywords... today, yesterday, this week, last week, two weeks ago, tomorrow, next week, this quarter, this year, last year, etc. maybe allow for day, month, year, range.

- special reports - daily weekly, closeout, knox report, grouped, etc. think of special options and reports that are used all of the time.

- logout

- images and media searches - general, specific main player groups (customer images, item images, expense images, etc.) - maybe some small filters like -from_date:[], -to_date:[], -caption:[], -user:[], etc. media could be similar...

- organize all of the ai quick search pieces according to the main business functions. that will help show what we can do. don't get stuck on the number 12. it could be whatever... - link to the presentation gallery - business functions

- show [], show prompts, show homepages, show pos options, show crm options, show payroll options, etc.

- what about creating some more quick search permissions... things like help, ai, images, media/content, navigation (nav), etc. That would be cool and would create some great crossover between the older quick search and the newer quick text options and prompts.

------ end - ai options and prompts -----

Meeting with Alan, Cory, Steve, and Bryan on a Zoom meeting. Here are some of my notes:

- Talking about budgets and payables. It's been a long grind for all of us.

- Talking about options to sale a portion of the company (percentages) and what that might look like.

- How can we increase sales and improve the communication (internal and external communications). Lots of back and forth.

- Talking about ideas, solutions, and different lessons learned.

- Spent some time talking about custom work for clients. We have been burned over and over again. Also, nobody knows who is working on what. There is a real lack of communication within our team.

- We are honestly trying, but it gets tough.

- We have so many things going on... that is awesome, but it adds challenges.

- We switched over and spent some time talking about funded projects and trying to focus there.

- The subject switched over to talking about sales... Small list from Steve - like, trust, and respect - that's selling. Helping to solve people's pain. We may have to switch to our sales hat.

- Alan had a number of questions about selling or sales... what can adilas do? How do I sale this? Being able to speak their lingo, meaning our clients.

- Focus on bringing in revenue vs building. That is a hard transition for us, but we can do it. Steve's analogy - go out and get some firewood.

- Towards the end of the meeting, Steve was working his magic and basically selling us on some things... he is super good at that. We are planning on going out to sale systems.

Paying bills and recording expenses. Recording notes from last week and today - 9/3/25 to 9/6/25.

On with Bryan looking at code. He was trying to fix an online bill pay page for paying for invoices after the fact - making payments on account. We ran a test payment and it worked. We then pushed up the code live and did a live payment and it worked. He then sent out an email to the client to have them try it.

Emails and phone call with Calvin. He is getting into tons of AI and wanted to meet with Steve and I to show us what he has been doing. We would like to meet with him next week. General to do list items. Paying bills, entering expenses, and other stuff. Had to update some API keys for the guys who are testing the AI agent for the POS (point of sale stuff). More expenses and paying bills.

Multiple sessions throughout the day. Building more AI options and prompts for the cart, the AI quick search, and basic adilas navigation. Spent some time planning. Then building a new AI search helper function to sub divide the simple options and AI prompts. Lots of time playing with AI and learning some RegEx (regular expressions) stuff. Couldn't quite get it to work. Went through different versions. Finally switched over to a simple RegEx find and then pulling out what I needed. The new function can easily find any valid next key/value pair within a simple search/option/prompt string. I'm excited about that. This should really help speed things up, development wise.

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

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

Meeting with the Nxtlinq guys. They are wanting to know about progress and how quick we can get them stuff to work with. They were showing us some new changes. They are simplifying things and making it easier to integrate the SDK's and to toggle on/off certain pieces of the AI agent. We told them that we are working on putting the AI agent in the headers and footers to make it show up (if turned on) in all pages of the adilas application. They would like that done as soon as possible. We set a date for this coming Tuesday. They would love it sooner, but we'll see how it flows and goes.

After the meeting, called and talked with Steve for a few minutes. He is pretty comfortable on where we are heading. We also talked about a couple of other projects that are circling around as well.

Working on getting the AI agent into the headers and footers of all adilas pages. Did some planning and some AI research as well. Small work session. The Nxtlinq guys sent us some samples. I was looking through things and pulling them apart. I only want to add just what I have to. Nothing extra. Making progress.

Phone call with Bryan to help him get his local system all up to date and caught up with the master code branch. We had to trouble shoot his Git and Bit Bucket stuff.

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

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

Emails and tech support.

Working on the adilas mini API. Added security for the part lookups. Adding in options to help with the customer lookup options. We also added in options for searching customer business names, first names, last names, customer phone numbers, and customer email addresses. Light testing and playing around with different search options.

Recording notes from 8/27/25 to 9/2/25.

Meeting with Greg Weess from Calder. Talking about options for selling part of the adilas business to raise some capital and other possible options. We are just looking into what options we may have. We don't really want to sell, but we really do want some sort of angel type investor who sees the vision of what we can do and where we can get to. Lots of talks and options.

If wanted, here are some adilas investment options that we see as options.

Meeting with Steve. He and I were working on the AI agent stuff and where to go with it. We would like to include some code on our headers and footers to help the agent show up on every page. We really want to use the adilas mini API, full adilas API, and our new URL crafting (AI quick search). That is our goal. Josh joined us at the end, and we had some good conversations about ideas and options.

Working on the adilas mini API and what it can do. Added some security options to help keep it safe.

On a meeting with the guys from Nxtlinq. Going over progress and doing a little bit of show and tell to help each team see the progress. They are making improvements on the user interface and being able to keep the AI agent screen on top. They also showed us a possible version where the AI agent interfaces and works with a SPA (single page application) type interface. That looked a lot nicer but would require us to rewrite quite a bit of code.

Mobile first design. Working with Russell on some training. I don't need to know everything... I just need to know how to figure it out...

Russell wants me to keep doing the training, using AI, and then experimenting with what I'm learning. Exposure is really important and seeing things and how they work. We spent some time working on some practice files. Inside of our practice file, we have a touch image slider, navigation buttons to do next and previous images, and we can click on individual dot indicators to jump right to a specific image. Playing with JavaScript and CSS and mobile first design stuff. Started working on the other page content.

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

Recording notes from last week. It was a busy week, and I didn't them all fully recorded.

Emails and tech support. I then had to help a client with a custom ecommerce checkout process. They wanted it a little bit tighter, so we added some code and a redirect if other things were needed. Sent them an email with instructions to the client. We also got an email from the same company with some other updates. They found another small bug and we went in and fixed it. I'm so grateful for users who push on things and then let us know if things need some help. Good stuff.

On a meeting with the guys from Nxtlinq. They showed us some progress and had a few questions. They are just barely being able to start using some of the URL options and prompts. We still have a ways to go, but they are making progress. After the meeting, I sent an email to both Steve and Josh with a small overview of how it went.

Working on a mini version of the API for the adilas API sockets. This is a super quick, human readable, API call that has minimal fluff. Building and testing things as we are building. Here are some samples:

for the web/adilas_mini_api_calls.cfm page...

URL.useCorpKeyId or FORM.corp_key_id - pass in the corp key id value - Example: USE-0053 or Adi-22

URL.aiQuickSearch or FORM.ai_quick_search_field - search string or option/prompt value

URL.mode or FORM.mode - default is blank, if blank, it will show JSON. If it has a value like mode=show, it will show a CF dump (visual) of the object.

valid aiQuickSearch values...
customer types [filter]
customer lookup [filter]
item categories [filter]
item lookup [filter]

Sample URL for the AI quick search look-up page (in the public web folder)

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=customer%20types

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=customer%20types%20VIP

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=customer%20lookup

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=customer%20lookup%20Sponge

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=item%20categories

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=item%20categories%20Candy

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=item%20lookup

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=item%20lookup%20bit

Internal tech support. Had to look-up some settings on a main API connection for a client. They had not turned on a master switch "show on the web" to yes. It was still marked as no and was denying access to the API. After that, I had to do some backend changes for Sean and Cory and a deployment that they are working on. We had to flip some vendors on PO's and items globally in the system. This took some time and we had to look up vendors and sub vendors under the different PO's.

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

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

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

Cory and Sean requested that we add the delivery stuff for the mini scan cart. Took some time and did some research, coding things, light testing, and pushing code up to data 0 for some testing. Let Cory and Sean know to go do some testing.

Emails. Got some good information from Wayne on video live streaming. See attached.

Working on gathering information for a letter of recommendation for Cody. He did a great job and worked for us for about 6 months. The only reason that we had to stop working together was because of budgets (tight). We would love to have him back if possible. Just for fun, here are almost 80 entries in the developer's notebook where I was working with Cody. Lots of good stuff. Click here for the link.

Working on some to do list items. Planning, brainstorming, paying bills, emails, and API stuff for cory (internal research and gathering data). Reviewing video streaming stuff from Wayne. He was doing some research on how to do that. He ended up converting a bigger MP4 video into an HLS version or format (a bunch of smaller clips that are played together in a play list type fashion). Anyways, I watched a few videos and looked around a bit. Interesting conversion process. We'll see where we go with that.

Phone call with Steve... going over ideas and how to put some simple look-ups into the public domain... We are thinking about building a quick mini API (short and sweet). Talking about AI agents and options. Predictive levels and seeding (prepping) the environment.

On a Microsoft teams meeting with the folks from China. We went over the AI quick search and did a number of walk-through demos. They had a couple of questions but seemed fairly happy with the progress. They are planning on playing with it and even trying some language translations on the AI agent (bot). That would be super cool.

Work session with Steve on the AI quick search and URL crafting stuff with small normal text prompts.

Talking with Russell about AI models and back and forth. Talking about security and validation routines. Talking about scraping pages and pulling stats, even if the client doesn't know. Going over AI options vs AI prompts - creating an AI consultant for adilas. Baby steps - take one thing at a time. Talks about API sockets, endpoints, URL crafting, and mixed solutions. We spent some time talking about human interfaces... speaking, writing things down, OCR scanning and reading (ocr - optical character recognition), AI chat/prompt bots, etc. Russell is curious about the implementation and what we end up doing,

Russell and I were talking about mixing API sockets and session values. Good options.

Switched over to the CSS training. Working on the JavaScript for changing images and creating an image slider.

Meeting with Bryan, Alan, and Brian from Finetech. We went over some merchant processing stuff and questions. We talked about some needed changes for Clover devices and some Card Pointe enhancements. After everybody else left, just Bryan and I stayed on for a bit. We did some light training and set it up for one of our clients to accept split payments for ecommerce. We didn't allow it directly, but we used some existing settings to let that happen. We then started talking about AI and how we are using that in some of our development and processes. I showed Bryan some of Steve and I's AI quick search stuff that we were doing (options and prompt to help generate URL's and do custom URL crafting).

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

Great meeting with Steve. We were going over options to help let AI agents and AI bots use the adilas application. Steve is working with some guys out of China who do that kind of things. We spent some time going over some ideas and where we could go with things. We talked about the external adilas API sockets, an internal option that involved cookies, tokens, and JSON data storage. We also talked about using the existing structure and URL (web addresses) and how that might look. Our favorite option was the web links and URL crafting ideas. See notes below...

- Use the custom_json table - if we went with internal data storage options, this database table could be used for storage.

- Cookies and tokens - We help them save and retrieve them and then they have a spot to stick and store their data.

- Mix a hash... say something like this... auto id, main id, app type id, date, and then get a hash from mixing those pieces. This would end up being the virtual token that would let you look-up the actual JSON object.

- This internal cookies, tokens, and JSON data storage would virtually provide them a small shelf space for them to use. This could totally work and we may end up using it by itself or in conjunction with other options.

- On the ColdFusion side, internal app stuff, we could do a virtual 1-off on the code pages. Basically, don't stop or interrupt the main page flow. Just build little side or frontage roads as needed.

- We were looking up existing API sockets and methods. We may end up using the addEditCustomJSON method - in search_15.cfc - possible new API

We then switched gears and were talking about using the URL... hyper links or web address links - We really liked this option.

- With simple URL's or hyper links we could virtually use the system just like a normal user - We could let AI do or make interactions vs human powered links.

- AI cold potentially help with understanding normal voice controls or prompts and even different languages - translate and convert to the options or prompts.

- Let the user talk to the system

- Steve's word or phase "URL crafting" - I liked that

- Natural conversation and then boiling things down to the prompts which will translate to the correct URL crafting option

- Normal html pages and web addresses. Once the pages come up, you could do some scraping and then using those pieces

- AI, the user, the interface, and the URL crafting - perfect marriage

- Steve had so many ideas... recording time, recording notes, etc. - so cool!!!! AI could help our users be a super user

- 3-legged stool analogy... One leg is the system and its features and functions. Another leg is the users and the money that they spend to use the application. The last leg of the 3-legged stool is education and training. AI could help be the trainer and navigator (major help on the education side).

- My mind was blown a bit today... that's been awhile since I had that much fun dreaming and brainstorming. We had help from above - guidance and inspiration. I'm so thankful for that. Just trying to give some credit where credit is due... :)

Recording notes from end of last week.

Phone calls with Bryan. He is working on a couple different projects. One is dealing with CSV to PO (bringing in new inventory) and they got some duplicates. The other questions he wanted to ask were dealing with the Plaid API (external banking stuff) and recording external reference numbers from bank transactions and id's from outside software systems.

We then jumped on a meeting with both Bryan Dayton from adilas and Brian Mowris from Finetech. We were debugging and checking out an error with Card Pointe. For some reason, one of our merchants (clients) was get an authorization error. We checked the credentials and were able to make a manual transaction happen but could get it to connect to any hardware terminals. We will pull in Alan (other adilas developer) next week, as he was out of the office with his family.

Meeting with Steve and the developers who are building the bot engine and AI agent for a voice-controlled POS (point of sale) options. They are using the adilas API endpoints and sockets to interface with us (currently). We got on the meeting and we went for a little over an hour. There were eight of us on the meeting. We would speak and then wait for them to translate. They showed us a small demo and had a small agenda ready to go. We talked about different options. Originally, they just wanted to use the adilas API sockets and endpoints. Now, it feels more like they want to build the engine inside of adilas to have more options and access. That is potentially good and bad. We want to look deeper into this before we just say yes, do it.

After the meeting, Steve, Josh, and I got on a call and talked about some possible options. We will meet again as a team on Monday afternoon to come up with a plan. We will then present that plan to the Nxtlinq (spelling?) guys.

Meeting with Hamid. We went over some of the things that I am learning with Russell and on the Udemy CSS course. We then did a small practice file and did it together. That was fun. It also gave me a chance to use what I know, in a teaching environment. I enjoyed that. That helps it (the learning) stick better.

Training on CSS. Working with selectors and combinators (CSS theory). Going through videos and practice files - course in on Udemy.

Emails and recording notes. Light research on a funding company and responding to some email enquiries.

Internal emails and small research and review for both Sean and Cory on different subjects. Sent an email to Wayne to follow up on being able to stream videos from the adilas content server. Sent some links to Sean that either migrate and/or copy customers, parts, part categories, vendors, or chart of accounts from corp to corp. He has a client that had an old system and wanted to setup a new system and use some of the older values. These are files that help copy between corporations on the same server.

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

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

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

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

- Adilas will do some training

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

- Resource coordination, putting together whatever combination that is needed

- Training is a resource

Meeting with Russell and doing some CSS training. Working on setting up a small card (page element) with images, buttons, and icons. Lots of CSS and dynamic placement of items and content. Practicing CSS by building a mobile friendly card or app for a recipe app.

Recording notes. Doing some research on our current mini scan cart and ways to help it out. I have a big list on my local computer of things that we either wanted to do and/or are prepped or ready. Small wish list or feature list of sorts. Reading over those to do list entries. Back working on the code review for Bryan and his invoice and quote flex attributes project. Going in and setting up a number of defaults, even if not being used. Trying to prep certain pages for future usage with quote and invoice flex attributes.

Prep work for working with Bryan. Jumped on a meeting with Bryan to show him my progress. We talked about the next steps, and I will keep working on code review for his project. We are working on the flex attributes for quotes and invoices. This project also deals with how those things are passed through the shopping cart as well. Bryan wants to use some of this tech and these sub features for restaurants and cafes. Both Cory and Steve mentioned in our earlier meeting that they have clients that could use a similar feature but in their own ways. Good stuff.

Meeting with Cory and Steve. Going over vendor credits. Looking over a quick question on calculating taxes for invoices. Small API socket stuff. Steve left and then Cory and I were going through a list of questions and small internal tech support pieces and requests from clients. We jumped through a number of small projects. Lots of the requests are user/client preferences. Certain people like it one way, others like it another way. Eventually, it will end up being a setting of some sort. That's what it is looking like as of now. We will get to those changes when we can, once other projects are done. There is a constant demand for new and enhanced features.

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

Checking out some code for Bryan. He has a branch that needs to be merged in. It has 40+ pages that have been changed. Checking things out. This is for new flex attributes for invoices and quotes. Small merge conflict fix and then running code locally on my machine for testing. Going through pages and making small tweaks.

Working with Steve on some code. We jumped in on a big bulk transfer page for quickly moving tons of inventory around. We did a few small fixes and got his page working. He has to go back in and do some clean-up, but it is coming along great.

Emails and recording notes. Had to call tech support for PB&T bank. Couldn't get into the online account. Checking out a code branch for Bryan. He wants me to work on it and merge it into master. It has a small conflict, looking at code to find the conflict.

Checking email and recording notes.

Email to Wayne about streaming videos. We would love to be able to do that easier from the adilas content server. Then a semi-lengthy email to Chuck and others about the shopping cart and updates to my cart favorites. Phone call with Bryan to go over a page that does an upload from a CSV file and allows for dynamic mappings to be used. He would like to help some clients with possible EDI (electronic data interchange or transfer) type stuff for buying and receiving inventory.

Here are the two videos that I sent to Chuck about the shopping cart.

https://www.adilascontent.biz/videos/internal_shopping_cart_r1.mp4 - small future cart demo

https://www.adilascontent.biz/videos/cart_touch_and_discount_options.mp4 - current cart demo with my cart favorites

Recording notes from the day. Checking emails.

Prep work to get a video ready for showing the new feature for the vendor credits functionality that we just launched. Made a quick outline, did some practice, and then made a number of videos and pushed them up live. Sent an email to Cory and Steve to show the new features. See attached for the video links.

Mereged in some code that we have been working on.

Research on a small bug. Phone calls with our developers and a rep from the merchant processing company. It seems that the error is on the client's bank putting a hold on fees being taken out for credit card processing. I love it when it is not our fault... :)

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

More continuing education stuff on CSS. Going through videos on Udemy. Recording notes from the day.

Meeting with Russell. We were going over some positioning basics with CSS. Spent the whole session going over small tasks and placing boxes (small placeholders) where we wanted them to be placed. Lots of challenges and then coding to the challenge. At the end, Russell was showing me some of the things he has in his portfolio and things that he has built on the side for his own personal training stuff. It was really cool.

Continuing education - dealing with CSS - course on Udemy. Talking about the continual process of development of the CSS language, modules, and how it rolls out. Interesting. Getting into the course outline and overview. See attached for a screenshot of the course outline.

Recording notes from last week. Going through emails. Got a text from Steve with a question about adilas API and which ones I would recommend. Light research on which API call to use to get the parent part or inventory item quantities. Sent him some info via text message.

Small fixes for Sean and Cory on the mini scan cart. They had sent me an email asking for a few small tweaks and changes. Added code to dynamically hide the "on account" checkout button based on money type selection and settings. This just makes it a little tighter. The other request was looking into the formatting of prices and discounted prices for line items in the mini scan cart. Added code to check the corp-wide settings for the number of decimal places. The corporations/users are able to select up to five decimal points of accuracy. Did some testing and pushed up new files to all servers.

Hamid and I were playing around with ChartJS stuff. We built a number of different charts, playing with the x and y axis and pulling data from different spots and sources. Fun training session. Trying to get more familiar with the possible graphs and charts.

Looking at code with Bryan. He is getting closer on some of the restaurant code that he has been working on (rooms, tables, and servers). He is adding in flex attributes for invoices and quotes. They, the flex attributes, also get passed through the shopping cart which will be pretty cool. There are more things than just restaurant level functionality that will be taking place, but that's a start. Good session. He basically turned that branch over to me to do a deeper code review. I will review it and merge it into the master branch.

At the end of the meeting, we were going over plans for the upcoming Adobe ColdFusion conference at the end of September. Making plans and shooting around ideas.

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

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

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

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

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

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

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

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

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

- Talking about value-based upgrades and user perceptions.

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

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

Prep work for merging in code for the vendor credit branch into master. Had to fix a few merge conflicts. Cascading code and database updates to all servers. Recording notes from the day.

Small changes for the Benning Construction charity golf tournament out in ecommerce land. They needed one more sponsorship level to include a complementary foursome for the golf tournament. Changed a graphic, added some web long descriptions, and updated the checkout code.

Meeting with Russell. Talking about continuing education. Try to use this strategy for continuing education - learn something, go play with it, learn something go play with it. We will be doing some fun projects. Taking small concepts and building them on top of each other. Russell wants me to write things down, If I have questions, and we will go over it. We downloaded VS Code and a bunch of extensions. Started playing inside the new editor and IDE interface. Looking into CSS. Russell wants me to pay for and take a few CSS and JavaScript classes from Udemy (online learning). Good session.

Updating help files. Reading over pages that deal with vendor credits and seeing if any changes are needed.

Working through balance sheet entries and reports for vendor credits. Light testing.

Phone call with Bryan. He is working through a merchant processing setup. He reached out to a number of people and just wanted to talk about what to do and where to go next. It seems like a small mix between a specific merchant account and specific hardware being used. We are trying to figure out the next steps.

Recording changes in the adilas ownership percentages. Sent an email to both Shari O. and Steve with documentation.

Recording ownership percentages for adilas co-owners inside of adilas. On the phone with Bryan to talk about database field validation on merchant processing auth keys. We have a client that is trying to input values that are not allowed. The system is setup to not allow certain words, phrases, and strings (cross-site scripting protection stuff). They were given this auth key from the company, but it violates some of our validation routines. We had to open it up a little bit for that page. Crazy stuff.

Paying some bills and documenting expenses in the system. Other small to do list items.

Brainstorming on some ideas about receiving inventory and training people... the brainstorming then switched over to AI agents - job queues and prep mode... see EOT # 12195

Jumped on a GoToMeeting with Steve. We looked at a small bug and got it fix for a new API socket that he is working on. Steve is exposing all kinds of external API sockets and harnessing some work that was done years ago. That is awesome.

We then switched gears and spent a few minutes talking about possible job queues, prep work, and ordering inventory and receiving inventory and client needs. See more notes on element of time # 12195.

Paying bills and recording notes. Phone call with Bryan. Going over ways to speed up the PO and entering inventory process. Talking about training for our clients and needs. We then got on a conference call with a client to go over some custom ecommerce checkout requests. Going through emails. Quick phone call with Steve to go over some API socket stuff. He is really making some headway there. We added API sockets back in the early 2000's but it has not been fully used until somewhat recently.

Use this EOT to track API development for AI Agent Endpoints

This was just some brainstorming... It started out with training people and then moves into possible AI agents and bots.

On the people side - What if we trained people to help work inside of adilas... and then helped to staff them at other people's business. Almost a small staffing service for trained adilas workers to help with data entry, input, etc. - just a thought... We have seen huge needs on ordering inventory and then receiving inventory. There are multiple steps but very trainable...

This could be part of the adilas cafe and community concept.

If I had the money... It would be super cool to setup a training program to help people who want to work, get them the training, even get them certified, then get them connected with the right companies who need work done. They could then use their skills to earn money. These people and their skills would then become an asset to companies that use adilas, as a trained labor force. It still needs some more info, but it could really help out in different ways.

Switching over to job queues... and AI agents...

This needs more thought, but what if you could even setup a virtual queue of things that need to be done... It could all be done from outside of the system and then people could pay for the work to be done... Basically, abstract it enough that a person working wouldn't have to have permissions to work inside another person's system. Build the whole thing on the outside. Think prep work... prep level interface... They could do the work, on the outside, in a special prep environment, then it could be approved, pulled in, and flip it over to real or live. Like I said, it may need some more thought, but that would be super cool.

I could see a company, quickly add a job to the queue, uploading a PDF or scan (some kind of documentation), and then they get notified when it was done. That would allow someone who is doing stuff to work for multiple companies without actually affecting their live systems (everything is in a prep stage). The work would be done, recorded, and basically prepped for changes and quick import. Another thought would be to build an AI (artificial intelligence) agent to do a similar thing. It looks through a queue, does the prep work, applies the rules and training on OCR (optical character recognition) documents, performs one or more processes, and when it is done, it submits it for approval (go live status). All kinds of options.

Steve is already working with a company that is building AI agents to do voice activated POS (point of sale) functionality, payroll functions, and other tasks. What if we could keep adding to that list... expenses, deposits, bank reconciliation, sales receipts, quotes, PO's, inventory levels, ordering inventory, receiving inventory, pricing, ad campaigns, discounts, special sales, CRM stuff, ecommerce, scheduling, etc. Think of everything that adilas can already do... What if we could allow for people (real people) or AI agents to do some of those tasks... It (whatever work was done or prepped) doesn't go live until the requesting company clicks approve or some process that would allow for real prep work to become real live data transactions. That could be super cool!

Working on showing special account transaction histories. Lots of database work and using SQL aliases to join similar queries. I thought that it was pretty deep. The report shows all special account history actions per user for a specific date/time range.

Recording percentage ownership changes for adilas members and co-owners. Sent the guys emails with signed copies of the promissory notes. Recorded stuff inside of adilas and uploaded documentation. Paying bills.

Working on some changes for the Benning Construction ecommerce site. They needed some vendor/sponsor information collected during checkout. Along with that, they also needed some complementary foursomes sign-ups (golf tournament stuff) with the purchase of certain sponsorship levels. Multiple sponsorship levels. Four of them had the complementary foursome and the other three did not. Pushed up files and did some testing.

Meeting with Hamid. playing around with graphs and charts. flip flopping between bar graphs and line charts. playing with options, colors, and data sets.

Working on adding a payee/user filter to the special account transaction page. This page is a sub of the history homepage that needs to be able to filter and sort by specific payee/users.

On a conference call with Bryan and an adilas client. They were requesting some small changes to a custom section of their ecommerce checkout process. They are going to send an email with details and more information (paper trail). Promised these changes by end of day tomorrow.

Back working on the history homepage and data level drill-downs for special account transactions.

Meeting with Cory and Steve. Quick review of my projects. Then on to some questions that Steve had with the adilas API sockets. We went over some internal pieces and how things work outside in the web/API realm. Good conversation. He is connecting the pieces and helping some outside developers get connected to the API. One of the companies that he is working with are some AI agents that are building voice activated POS systems.

Working on the history homepage drill-downs for the vendor credits and other special account transactions. Lots of new queries and drill-down links.

Recording notes and checking emails. Light research on a networking platform called Alignable. I watched a couple of videos and browsed around a bit.

Checking out the online ordering process for booking a reoccurring event (online scheduling). Looked at code, data, and sent an email report back to Cory and a client who had some questions.

Recording notes from last week and today. Trying to get caught up.

Working with Bryan. Looking over some files to help with some merge conflicts. Making changes and trying to retrofit things that were made on both old and new branches. We kept running into some issues. We may make a new branch and then plug in pieces vs trying to update the old code from the old branch. Basically, change the direction of how we are retrofitting things together. That should help.

Downloading a new photo editor. Converting some .png files over to jpegs. Started working with Russell. This ended up being somewhat of a mental health session. Talking about communication skills. Here are some of my notes. They may mean more to me that what someone else gets out of them.

- Things that are kept in the dark are very destructive - air them out.

- Plans of reality vs real reality. Story of an army on the ground vs the ones who are planning to do a certain invasion. What is really happening on the ground.

- Expectations and who knows what. Lots of assumptions are being made.

- If things keep going, it can actually cause other problems. Undoing the underpinnings... hurting inside, affecting all of the other things, spiraling downwards.

- If you don't change anything... nothing will change.

- Admit what is true and do what is right.

- Can I change the situation to be more manageable? My choice not to do something is a choice of acceptance.

- Where is the line and how do we defend that line and advance the ball? Boundaries and what those mean and look like.

- The illusive dragon is very tempting (chasing that what if dream)... just keep fishing (doing the small things). There is a pattern in what is going on.

- The worth of souls.

- Priorities... first things first.

- Take what I am doing with adilas and super charge my training... Stick with the smaller budget and do all the rest of the hours in what I want to do and learn.

- God wants a discussion. Express your wants and then move in a certain direction. God doesn't move a parked car. If you are moving, he can work and influence that action. Momentum.

- Letting go, in order to get out... hand in the pickle jar, you can't get out of the jar if you are still holding the pickle. You may need to let go, in order to get out.

- Budget... 20 hours... and only do those 20 hours. Use the other hours as continuing education and building new skills.

- I'm a helper, a dreamer, etc. Adilas is both my hell and heaven (be real about what is what).

- What is my exit strategy? You have power to bail. Start building toward that exit strategy. Where is your line? What are your boundaries?

- Regardless to what happens... I do this (whatever that is - ideally in righteousness - according to God's law).

- This life isn't the end. What can I do to make the most of what I can do? Bloom where you are planted.

Working with Steve and looking over his new projects. He is working on a bulk transfer for subs (parts and items). Looking over his code for the bulk transfer invoices of sub inventory back and forth. We worked on some code for a while and got it to a stable spot. He will keep working on it. We then rolled over to the external adilas API sockets and talked about some flow for a little while. Steve is working with those AI bot guys who are doing some voice interface stuff with API calls to do a voice operated POS system.

Recording notes from last week.

Recording notes from earlier in the week.

Working with Sean on a customer data upload. We grabbed a sample of the data and wrote a custom import page to help with the different logic pieces (combine this, remove that, split this and that apart, etc.). I got him all setup and pushed a file up to the data 4 server so that he could do some live uploads.

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

Meeting with Bryan. He had an older branch that had multiple merge conflicts. Going through that process. We had to get his local box up to speed with new environment variables and settings. We ran out of time to do the merge conflicts on the old branch. We will do that at a later date. We then flipped over and did some more work on getting Bryan's local machine up and running. After that, we looked at Cody Apedaile's checkwrite and label builder code. Bryan wants to use some drag and drop functionality to build out a restaurant interface type environment. Bryan and Cody are going to be working together on that project.

Working with Russell. Mocking up single date range graphical interface and date comparison graphical interfaces. Russell was doing the mock-ups. We did one with a single date range and another with a comparison date range. Just to get an idea of what it might look like. See attached for some screenshots.

Working on user history look-ups for the special account transactions for the history homepage.

Emails and looking into a small bug out in ecommerce land. Got a text from a client and then called him back. Texting with Alan about checking on a possible bug dealing with merchant processing.

Jumped back into checking out some Excel formulas and functions to help out Sean. Did some online research and playing. Sean has to move names around to different places (middle names and last names to new columns inside of excel). He was doing some manual copy and paste stuff... this research will help him out by using some functions and then doing a paste special to paste just the values. I sent him a big email with some steps... we may have to jump on a GoToMeeting session to really make it happen. We'll see how he does. Good stuff.

Back on the vendor credit project. Last time, I left off on doing some new queries to help the special account transactions show up on the history homepage. Built in dynamic code to handle possible data drill-downs as well. Trying to get back into the project.

Emails. Touching base with some older leads and contacts. Trying to follow-up and see if those potential clients need anything. Got an email from Sean, from adilas, with some questions about a customer data import. He needs some custom code to help split things up. There are over 32 thousand customers and the data is kinda messed up. Checking things out and sending him an email with a few suggestions.

Got a phone call from Bryan. We went over some of his current projects. Some of our code branches are getting older and have a number of merge conflicts that we need to work through. All part of the game. I then spent some time emailing back and forth with Cory from adilas about the partial PO project. That project somewhat got put on hold while we were working on the custom checkout process in ecommerce for the Benning Construction charity golf tournament project. Just circling back around and getting things oriented as to where to head and go next.

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

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

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

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

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

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

- Structural failure (at what point)?

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

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

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

- See a need, fill a need.

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

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

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

Emails and recording notes. Small typo fix for a client on their ecommerce site. Had to un-void a PO for different client. Did some research and had to reset some system environment variables for some AI bot stuff that Wayne is doing. Spent a few hours catching up from last week. Recording notes from 7/14/25 to 7/18/25. Busy week last week.

Paying bills and checking code for changes made last night. Ran a couple of sample transactions through the system. Light debugging and pushed up a new file. Sent an email to the client to have them do some testing.

Multiple sessions working on custom cart logic. Back on the logic for the golf tournament and how many participant records to show at checkout. They have donations, singles, foursomes, sponsors, etc. Testing counters and logic to show the correct number of participation and contact info records. Started working on saving that data to the cart memory object out in ecommerce land. Recording the contact info records and advancing the page on to the web make payment page. Also, at the client's request, made the ecommerce custom header non sticky, meaning it stays in one spot and the whole page scrolls down. Recording the flex grid tie-ins for the dynamic contact info and golf team registration

Helping Steve with a quick merge conflict resolution for a file. He also showed me some of the efforts that he and Josh are working on to do voice automation bots through AI agents. They are playing around with a company out of California that Josh knows.

Working with Steve on a custom ecommerce shopping cart. He is working on selling sub inventory by choosing a sub package to purchase. He had a bunch of code from Grok (AI stuff), and we had to back most of it out. We did it the old fashion way and got it all working. Not that the code was bad from AI but it didn't fit into our page flow. Anyways, we got it all fixed up and good to go. Steve is going to keep tweaking on his code, but we got the main task done and accomplished. Good work session.

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

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

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

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

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

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

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

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

Working on the dynamic flex grid tie-in logic for the golf tournament registration (custom ecommerce checkout process). Going over scenarios. Thinking about ways to remove records.

Dealing with multiple participants signing up for the golf tournament (singles, doubles, and foursomes). Tons of dynamic coding to setup multi flex grid tie-in options out in ecommerce land for gathering up the dynamic data. Deep looping logic stuff. Sent an email note to the client letting them know that it would be done by tomorrow afternoon.

Working on the custom cart logic for the Benning Construction checkout process. Building and checking the logic section by section. Uploading a small sample file and then testing the black box (custom code) live on the server.

Working with Russell. Jumping onto the chart stuff. We started out talking about life here and life after death (fun talking philosophy). Talking about limitations in our vision and outlook. So many good experiences here on this earth life. Take advantage of that.

Working with Russell on Adobe XD mock-ups. Going over plans for date pickers, date ranges, and advanced comparisons for dates and presets (day, week, month, quarter, year). We also want to build in jumper values for next and previous dates. Exploring navigation options, scenarios, pagination, and drill-downs.

Russell loves the full experience... for code projects - plan it and implement it - design, develop, and project management - mix all of those things together. That is fun to come up with it and then see it all the way through. Good stuff!

Bulk flex grid stuff for the Benning Construction golf tournament. Fixed some black box code for both internal tooling and external tooling out in ecommerce land. Both have to play along in the custom realm. Trying to collect names, contact info, shirt sizes, and dietary restrictions per participant and then tie everything back to invoices. Possible one-to-many relationship between invoices and how many contact records (golf team registration stuff).

Working on the Benning code to catch and gather the contact info per participant in the golf tournament. They opted not to setup a normal customer and are doing all of their invoices through a quest customer profile. We then have to catch a bunch of other data after the fact and tie it into the invoice. Also added in some bulk add and edit buttons to help with bulk flex grid tie-ins for internal pages (invoice line items and printable invoices). This will help later on, once they start getting some registrations.

Meeting with Bryan. Fixing some small bugs out in ecommerce. We made the changes and did some live testing. Once we got that finished, we switched gears and looked at Bryan's code for his Plaid API stuff (external banking API). We did some more testing and tracked down a number of different variables. Trying to make the whole process smoother.

Working on code changes for the Benning Construction ecommerce site. Working on some tweaks to the donation entry, had to hide the price and add some extra verbiage. Working on collecting contact information. We will be using some custom code to gather things like name, contact info, shirt sizes, and dietary restrictions. All part of the golf tournament registration stuff.

Work session for the Benning construction site. Added a new top header logo. They provided a nice flyer. Took a bunch of the images off of the flyer to rework the header graphic. Working on the custom code to help with the donations page. Had to open up the pricing field. Meeting with the construction company and Bryan and Suzi from the adilas team. Quick meeting. We are getting closer. After the meeting, then working on a small to do list of items. Small cosmetic stuff.

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

Paying bills and recording notes. Lots of internal tech support stuff today. Also, at two different times, we tried to jump on the GoToMeeting session but others were using the account. Steve was on earlier in a demo when Alan and I were going to use it. Then Alan was on later when Bryan and I were going to jump in. All is well. I'm glad that they were getting their stuff done as well. Busy day!

Phone calls with Bryan. He and I are working on the Benning Construction website. He passed me over some code via email. We also heard back from the client, and they are wanting a fancier looking site. Lots of lastminute changes. We'll see what we can come up with.