Emails and recording notes from 4/27/26 to 4/30/26. Adding graphics, screenshots, and AI chat PDF's to the elements of time.

Working with Bryan. Going over some of the Gemini stuff that Bryan is looking into. AI learning over time. Using AI for chats, questions, tasks, filling out forms, training, and full service. Talking about database scaling, both ideas and issues. Tons of drawing. Going over existing database logic, session management, servers, corporation creation, and setup stuff. Instead of just jumping into the mini POS or MVP POS, we are seeing that the next logical step may be some pre or prep work, before a client sees anything. It appears that the turnkey setup is the next step. This deals with automation of the corporation creation, setup, and configuration steps. We may not do this fully, meaning full automation, but we will move the ball closer by working on that process. Bryan wanted some help with budgeting and coming up with a rough budget for the project. We setup some time to work on it again next week. The current goal is to keep chipping away at it.

Meeting with Steve and Andrew. Talking about all kinds of ideas and possible solutions. Andrew was showing us his AdiBrowse, AdiHome, AdiChat, and other Adi features. He is using Adi, the dog mascot, for all kinds of possible tools and features. We were talking about the concept of having a possible browser at the adilas level (built-in). Talking about inside AI agents and outside AI agents like Gemini and others. Just to give you an idea about Andrew works, he is loading and working on three projects at a time. One on the phone and a couple of others on iPads. All at the same time.

Talking about how to scale businesses. He has helped other companies with this task. Bringing value to the table. There is a pricing disconnect - between what we bring to the table and what people are willing to pay. We went on and talked about plans, possible solutions, and how to work together. I grabbed a bunch of screenshots of things that he is working on and also showed him a few small things. Good back and forth. I also told him that we are idea farmers and sometimes have to sit on things (like planting seeds and waiting for them to grow). Eventually, we circle back around to things and work on those projects.

By way of a note, I'm going to add a bunch of screenshots and infographics that Andrew has done with ChatGPT and AI. I didn't get all of these tonight, but they all kinda fit here, in this discussion. See attached for the graphics.

Working with Russell and Abby. Back looking into the dynamic documentation project. Looking over security aspects of the project. We were doing some testing on the XSS (cross site scripting) validation.

Working with Abby. Looking over graphics. I got a number of new screenshots. She also finished up a small video on the adilas value add on core. It is looking good. See attached for a number of new screenshots.

Emails and reading through documents dealing with adilas help and support options. This was a proposal from Andrew.

Quick meeting with Bryan. Help on his eBay items and shipping stuff (new 3rd party solution). We made a quick fix and then he pushed it up for some testing.

Reading emails from Andrew. He sent over three agreements and one dealing with Adi options.

- One agreement handles revenue and customers.

- One agreement handles leadership and equity alignment.

- One agreement handles capital and control opportunity.

- Adi becomes the face of the platform. Adi is the dog avatar or mascot.

- Adi is the interface. Adi is the assistant. Adi is the operator. Adi is how users interact with everything Adilas already does.

Multiple sessions working on the mini POS or MVP POS plans. This was actually five different entries, but they are all related and all happened on the same day. See attached for some of the documents. Here are some of my notes.

Planning on the mini POS. Great little session with ChatGPT. "Start simple. Grow into the full system." I gave it some notes and got some good direction. We still need to go to the next level, but making progress. Created a PDF of the conversation.

Working with Bryan on the mini POS or MVP POS. We were going over the ChatGPT chat and plan. We ended up talking about a thing that Bryan found called the university of the people - possible free entry point - thinking about lesson plans, simple usage, and helping people progress. We would really like to make a simple or free version, along with classes or course curriculum. Make it as easy as possible for entry and people to learn. 

Bryan was asking - how to transition from MVP to more features and tools? Keep funneling it down.

Help our team flip the switches quickly - manual setup and configuration steps. Make that faster.

Light planning. How can we build a guided bridge into our ecosystem. Did a secondary session with ChatGPT to help explore the ideas and options.

I really liked this line - Guided Entry Layer Into the Adilas Ecosystem

Capturing the Core Vision

Create a lightweight, mobile-first MVP POS experience that allows small businesses, events, vendors, and simple operators to begin using adilas quickly and comfortably, while preserving a guided path into deeper operational tools over time.

Primary philosophy: Simple First. Expand Forever.

Secondary philosophy: Help businesses gradually grow operational maturity without forcing painful system migrations.

The bridge itself becomes part of the product.

Branching from the MVP POS into the MBP timeclock and project time tracking mini app. Reviewing some AI chats from earlier today. Finishing up the chat session dealing with an MVP for "any" time tracking mini app as a bridge to the adilas ecosystem. See attached for links and PDF's.

MVP POS chat - https://chatgpt.com/share/69f0f80f-3638-83e8-9b55-8175e21262d2

MVP "Any" Time Tracker chat - https://chatgpt.com/share/69f40537-f6a0-83e8-b579-e52bc143c958

Working with Shannon. Got some feedback on the adilas lite stuff. She thought that it was too wordy and too busy/heavy. I will see what I can do to help modify that. We then jumped into the adilas GPS core help file. Reading through a few sections. As a side note, it is really tough sometimes to boil things down and make them really simple.

Recording notes from the end of last week.

Podcast interview. They mostly wanted to know about me as a person and what makes me tick. I got to talk a little bit about adilas and what we do, but most of it was dealing with being an entrepreneur and developer. After the interview, they wanted some feedback on their product and approach. Small marketing pitch for some of their services at the end. It wasn't too bad.

Reviewing a document that Steve asked me to write. Small edits, proof reading, and sent the document off to Steve for review.

Working on PDF's, graphics, and linking up content. Lots of time working on graphics for the adilas lite and fracture site. Working on banners, new images, etc. Changed up a few things on the adilas lite and fracture pages. Made each section have a separate graphic and also added a new banner showing more than two decades of development work. Steve had asked me to write a small letter to Andrew and Don, about the possible purchase of adilas percentages. Busy day!

Recording notes, pushing up files, and reading over other texts and documents. Small website changes for old main website top menus. Added links to the fracture - adilas lite plan, investment opportunities, and the presentation gallery. Working on some other graphics. Added a banner image to the adilas lite page.

We ended up meeting later today. I was talking with Heather's parents prior to our meeting. Heather's dad, Jim Wilson, challenged me to make a one-pager to pitch what we are doing with adilas. He recommended that we make it non-technical, show that we have proven the model, and currently generating revenue. Shannon and I spent some time going over some of Abby's new graphics. We made a couple of tweaks and sent her a couple of suggestions. We then looked at the new mini graphics that I pushed up for the adilas GPS core help file. We reread some of the text and made a couple of small graphic changes. Just to make things flow better, with the graphics (combo).

Recording notes and filling in more content for section 11 of the steps to success. Web link - steps_to_success.cfm

Working with Russell and Abby. Looking over some new changes. Russell helped me get some AI stuff setup in my code editor. Then we jumped back into the documentation search functionality for our build project. We are deep in the details of the search results. It is close, but we have found a few small discrepancies, code from AI. Working through those things. Going over scenarios, what would you do if... (fill in the blank). Small training session. We finished some of that stuff up and then moved on to some load testing. Talking about scale. Towards the end, we got into a discussion about time it takes to make changes, graphics or code. If it takes a long time, start thinking - how can I make it go faster.

Meeting with Abby. She has been working on the compass graphic and system main players. She is even working on a small video of the application players. See attached for a few new mock-up images.

Working on linking in some of the older steps to success. Light work on section 4 and section 11. Section 4 is meet the players and section 11 is financials and accounting.

Recording notes from earlier today. Working on some mini graphics for the Adilas GPS core layout help file. Web link - help.cfm?id=479&pwd=core

Getting stuff going for working with Charlie at Touchstone Business Advisors. Uploading a number of PDF files for his review. I also sent out an email to Shari O., requesting some adilas tax return documents.

Meeting with Bryan. Going over plans for the mini POS. See the EOT # 12814 for some other ideas. He has been wrapping things up with some of his other connections and obligations. We were talking about the "almost" product dilemma... small things that hold people up from fully jumping in. That could be small connections (outside services), certain features, size, perception, etc. We also talked about some of the small sales funnels and how those work. We see lots of needs on the smaller POS side. Just an entry point. We are somewhat backwards, meaning adilas, we have the big picture options and not much on the super simple stuff. We may need to provide some of the simple things and then let them, our customers and clients, grow into the bigger pieces. One of the biggest goals is getting people in... really easy. Everybody needs to start out smaller and then grow into it. Let's help them.

Switched over to what Bryan is working on. He is working on Stream POS connections and some security stuff. Bryan is seeing the needs and requests of different parties. We are trying to listen and then trying to build things out to help these potential customers. Sometimes we run into areas that need funding, just to play and/or connect. Some of the other companies charge us to integrate with them as an outside vendor or reseller of their products (certain connections). We already have customers that want these smaller or mini products. Trying to build out the MVP for these mini pieces. I setup some time later this week to do some more planning. Everything takes time.

Talking about Andrew and how to approach some of what he is doing. He is providing so much content and plans, it is hard to know what to do with that. Not sure what to do there. He is generating so much, through AI, but I don't have any direction on what to do with everything that he is coming up with. Shannon and I were talking about scale and education. Two known needs. We then spent time working on the world building levels inside the GPS core help file.

Emails. Then going through a number of to do list items. Worked on adding some new content to the steps to success pages. Spent some time on department settings, payroll, timecards, time templates, and flex grid tie-ins. Also spent some time working on the meet the players page.

Web link - top_secret/steps_settings.cfm

Web link - top_secret/steps_players.cfm

Recording notes from 4/14/26 to 4/18/26.

Working with Bryan and Oscar on an API connection. We had to do some checking and debugging of Oscar's code. We also pushed up some small changes on our side. We got it much further than where it was. Bryan is going to go back and rework some stuff to help get it ready for the next testing session. This was new code dealing with pushing things up to eBay from adilas.

Meeting with Mike and Jennifer from Harris. Touching base, sharing some background, vision, and where we are heading. Good meeting. They, Harris, buy companies, but they don't really do portions and small investments. They want to own and hold the company for all time. They don't try to resale it. Anyways, good chat and what not. They were highly recommending that we find a vertical or sector and really focus on that. We have heard that over and over again. We, on purpose, are general or horizontal. That is both good and bad. It can also require deeper pockets to get the marketing and advertising going. People want to be marketed to for their specific needs.

Mike also recommended that if needed, we split or sub divide the product into different smaller brands so that you can actively chase those sectors and business verticals. I told them that we want to be the underlying business or data engine. Similar to how the Intel chip gets used by various different computer and laptop companies. They don't make the computers, but they are sold as part of multiple other stacks and/or products. We would love to head in that direction. See plans in the adilas value add-on core model for what we would like to do with industry specific skins. All part of the master plan, we just have keep heading in that direction. Yee haw!

Going back through some of my to do list items. Recording notes for earlier in the week.

Adding some small links on one of the AI dashboard pages for Steve. Small graphic ideas back to Abby. She sent me a small sample of a graphic and I replied back to her with some other samples (ideas and possibilities). Looking into some of the green skin theme ecommerce settings. Mostly just looking around. Made a few small changes to one of the pages. It took a few minutes to get into the swing of things.

Prep for a meeting with Steve. Looking over some new assets, photos, and documents from Andrew. Sent him some light feedback on the images. Started reading over a large document with a plan for AI + social media marketing engine.

Meeting with Steve. Going over the mini POS ideas that we are doing with Bryan. Talking about other distractions and requests. So many demands. We then moved into talking about AI's and how quickly they are moving and what they are able to do. People are wanting everything connected. One thing that we can do well is - bringing client bills down (how much they are paying) and getting them all setup. All kinds of stuff going on and happening along the adilas front. Talking about email services and email campaigns. Emails with full tracking and money generation (full tracking). Basically, not just an email campaign, but an email campaign that is tied into your ecommerce, POS, and CRM functionality. Great blend of functions and features.

After talking about emails and email campaigns, we went into tons of other areas and sections of the system. We went over a bunch of new AI stuff that Steve and Eric are doing. Dashboard, new ecommerce changes, etc. Great progress. Not all of the pieces are fully done, but they are looking good. This is somewhat unsaid, but the current goal is "following the money... working with those who are willing to pay". Steve was talking about how they, adilas, are really only focusing on helping companies that have pain and are willing to pay.

Good conversation. I was glad to see what they are working on. Communications have been limited.

Code review with Bryan. We went over ideas on the mini POS (drawings and such) and then moved into code. A few small code changes for the eBay integration, making it more dynamic. We then got super deep into the adilas API stuff. It got pretty deep. We were partly doing some API training, quick fixes, and then some testing. We got it to a stable point for Bryan's new functionality for ChannelBox (third party solution).

Meeting with Shannon. Going over new changes and updates. We looked at a few graphics and talked about making the little mini POS thing for Bryan (upcoming project). We then spent the rest of the time working on the help file for the GPS core.

Recording notes from the past couple of days from 4/13/26 to 4/15/26. Didn't quite get everything done on the Tuesday 4/14/26 date. There were a lot of notes that day.

Working with Abby and Russell. Talking about the concept of a platform (adilas) and then supporting and building a floating city on top of that platform (system or application). Russell did a couple of drawings and Abby took some screenshots. The underlying pieces that connect everything are through the platform and/or API socket level connections. We then flipped back into working on JavaScript and CSS for the documentation project. We are trying to detail out the search options. We got the search fixed up. Much better now. Other small changes. Some manual and some AI augmented changes. Good work session. As a side note, Russell and I are helping to train Abby, as much as we can, while working on this project. Lots of little teaching opportunities while debugging, testing, or experimenting.

Meeting with Abby. Going over the master plan and the AI level (level 6). See attached for tons of new screenshots dealing with the concept of the adilas value add-on core model. Working through some ideas.

Small changes, emails, and more research on adilas CSS demo page. Going over ideas and options for quick changes. What would that take? Using CSS (cascading style sheets), how could we make major look and feel changes without redoing the whole app or system? Lots of possibilities there. We already have a number of themes; we could possibly use AI to help us with some other themes that would retrofit into the existing system.

Here is a small link to the CSS demo page. If you are a developer, there are some small notes inside the HTML page source. We used this small page and section to run a small internal game for our employees and developers. They had to leave the HTML alone and could only change the CSS. Russell Moore won the competition and submitted five different options. Later on, a few years later, he helped us create the snow owl theme that is currently being used. Tons of potential there.

https://data0.adilas.biz/css/ - older adilas CSS demo page

Light research for a phone call with Andrew. Gave him a call. He was driving, so we just chatted for a few minutes. He was working all day, while driving. He was just talking to ChatGPT the whole time that he was driving. Interesting way to travel.

Working with Bryan. Working on our pitch and a plan. We want to speed up and get some turnkey onboarding (instant start), QuickBooks equivalent (simplicity), full operational expansion (inventory, POS, manufacturing, CRM). We would also like to do some module separation, UI/UX improvements, with the major benefit of faster customer onboarding. Something to replace Clover, Toast, Square, QuickBooks, Shopify, etc.

From Bryan... the problems we must solve
- onboarding is too complex for new users
- UI/UX slows adoption and sales
- User default to known industry software packages for familiarity
- nonmodern UI/UX experience - expectations

We then talked about some things that we could do. This ended up in a small brainstorming session of sorts.

- Scope - figure that out, where are we headed for this lift
- Friction and pain points
- Map it out
- Time to first invoice (<10 minutes) - we want it less than 10 minutes. Super simple setup.
- Solving the same problems over and over again
- Helping the accountants adopt the new solution - if the accountants are onboard, they can help influence and push the clients

For us...
- Database scaling - known issue. We can make more and more of them, meaning databases, but we can't intermix them right now.

- You need a full staff member to run it, meaning adilas. If you just touch it every once in a while, you really don't get the full benefit of it.

- Some people and clients that we are looking at - Andrew with Hosthuski and Brian with Finetech - both have an existing set of clients and a possible sales funnel, even though it is small. People come to them and they reach out to people and small businesses that need tools and services.

- API integrations with delivery systems

- Canned business solutions or fully custom solutions - there is a difference - this gets tough.

- Auto launch a corp and be able to move it later if needed. Back to database scaling and mixing.

- We build and develop - we would love to have others sell it and support it.

- We all live on little islands, and nobody knows what he other are doing - meaning the adilas team

known needs:
- Need to simplify
- Turn modules on/off
- Create our own buttons and nav options
- Map out the system
- Known bigger pieces - db (database), nav, permissions, settings, functions
- Super small mini POS - vendors, part categories, items, cart favorite buttons, etc. Simple.
- Quick setup form... quick vendors, part categories, taxes
- Quick corp-wide settings (limited view)
- Simple forms first, then link to full pages if needed. think layers...
- Quick users with preset permissions
- Quick access to the last few invoices
- Quick access to setup (layered with nav, if needed)
- Quick sales graph and charts.
- Layers - pretend that we are dealing with the cache valley kid's market - see EOT # 12656
- Mapping out the mini POS system - pages, flows, screens, etc.
- Maybe look-up some ideas on wizards and quick setup flows.
- Old idea of a simple app for users, timecards, and project time tracking. We have all of those pieces, similar to the normal POS stuff. We just want to make some super simple versions.
- Ask Wayne where he is at on the db (database) stuff - get an update.

//////////

It is now a couple of days later... 4/18/26. I have been thinking about some of this stuff. Here are some of my new notes from this morning.

- What if we did this mini POS just using the existing adilas API sockets? That would be huge, cool, and great starting point for other users and developers.

- What would that take? Meaning a mini app using just the API's?

- Why would we do this? What would that solve? - I would say, it could be a huge stepping stone for others who may want to play along those lines. I can also think of a number of other ideas and reasons.

- Internally, we use Adobe ColdFusion. I would like to make a version that is in plain vanilla HTML, CSS, and JavaScript. Mobile ready and phone first design. Most of our internal products are desktop first with possible mobile responsiveness. Flip that!

- We could look into some simple frameworks, but I'm half temped to just keep it plain jane or plain vanilla.

- Is there a way to use what we already have without tons of new development? That would be awesome.

- A long time ago, I heard someone say that eventually, you have to eat your own dog food. That may sound silly, but they were talking about consuming what you push out for others to use and consume. Virtually, you have to eat your own dog food. If we have to use our own adilas API's, we would be using what we are pushing out for other to use. I love it, let's do it!

- What if Bryan, Alan, and I (and maybe others) start our own little side company and use the adilas API's as the backbone. We help to strengthen the core (adilas) while still being able to do other development projects. It's an idea. We could make all kinds of little mini apps and then tie them back into the adilas backend engine. That could be really powerful. I would like to expand and explore these options more. One thing that I was thinking, we are good at building, but sometimes not that good at selling. We may need to hook up with smaller sales funnels to help with that part of the equation. Just some ideas.

- I'm planning on teaching ChatGPT how to connect to the adilas API. I would like to get some information about that process and then be able to share that information. That could be huge, as far as other outside developers and development work. All kinds of new apps and mini processes, all connected to the main adilas engine. As a note, see the planning page on the adilas marketplace. These plans are a good fit for what we are doing and where we are heading.

- For me, instead of just telling AI (one of the models) to just create this or that, let's start super small. Then build things up step by step, make sure that we understand and can back what is going on. I was thinking of using the mini demo API connection first, then building a little mini sample app, then moving into the mini POS option. Step by step, little by little, keep it manageable. Tiny baby steps!

- Another small note - what if we took a single corp, set it up, and then added smaller locations and users per account. If they never have to login to adilas, we could technically keep a bunch of information together in one place vs having to setup a separate corp per account. This won't work for all parties, but it could work super slick for small parties and/or certain situations. The alternative would be a super small corp (world) per entity vs a small location (real or virtual) per entity. See this world building help file for more information on possible breakdowns of how to organize things. This could be pretty handy if all of the locations or sub entities were using the same merchant processing account. Once again, this would only play true for certain scenarios. Just some ideas, if nothing else, keep thinking about it. Lots of possible solutions.

- This may not go here, but think about Amazon, eBay, or other big sales sites. They sub divide the pieces and then use one platform to allow for checkout, money distribution, credit card processing, etc. There would have to be some planning, but in a nutshell, that is what we want to do with part of the adilas marketplace. Keep expanding on this...

Working with Shannon. Going over things, things are constantly moving and shifting. Part of the game. Reviewing the end of last week. Going over phone call with Josh, new stuff from Abby, and the limited SWOT analysis document. We then spent the rest of the time working on the help file for the interactive map.

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

These are the links that I sent him...

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

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

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

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

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

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

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

- He has some psychology training and loves people.

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

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

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

- He said that he likes to study.

- Create awareness and access - make it affordable.

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

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

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

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

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

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

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

- Being strategic with the bells and whistles.

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

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

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

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

- Give lots of free feedback.

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

- Target the medium sized industries.

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

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

Recording notes from last week. Tying things together. Read a bio from a guy by the name of Andrew. He seems to be a developer, entrepreneur, and ecosystem level thinker. Sounds cool! I have an email and a text message out to him. This is a contact from Steve.

Phone call with Bryan. He is meeting with people and wants to see what it would take to put together a plan for a super simple version of adilas. Almost like a mini white label version where it could be super simple and beginner friendly. I was telling him that we may want to start with the bigger or high-level settings and templates. I see this step as quick group settings applied as a group or in bulk, thus the templates and settings idea. It could also be filtered down into permissions and what shows up, based off of those high-level settings (system wide). Great ideas. we are going to meet tomorrow to see what that might look like and do some planning.

I then got a text from Abby and jumped on the phone with her for a bit. She had a couple of questions. We ended up on the phone for almost half an hour. She is having fun with some of the graphics and concepts for adilas. We talked about funding and how she may have to put some hours on the side right now due to budget constraints. She is good with that, for now. We chatted about some other things, and she has a good attitude and good vision. I love it.

Recording notes from the past few days (4/8/26 to 4/11/26). Adding new files and graphics to the element of time # 12793 in the shop. This was from a meeting with Abby, earlier this week.

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

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

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

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

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

Working with Bryan. Code sign-off. Small close frameset button on the classic split cart. Then looking at some eBay code (API stuff). Light fixes and pushing up some code. We had to fix some merge conflicts.

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

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

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

Working with Bryan. Small code fixes. We had to param some values to help with the new code that we pushed up yesterday.

Going over the simple stuff from Abby. She took some of the AI chats and pulled out little pieces. We then spent the rest of the time talking about the sixth layer of the value add-on core model. We ended up starting a new ChatGPT chat session. Shannon and I only got part way. I then ran with it later in the day for a number of other hours. Here is the link to that chat session.

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

As I got new stuff back from ChatGPT, I was adding it to the value add-on core plan. The new stuff is at the bottom or on the layer six section.

Here is a little snippet:

The sixth layer of the value add-on core is the AI level (artificial intelligence). While the earlier layers focus on structure, data, workflows, and scalability, this layer focuses on interaction, intelligence, and automation.

You could say that AI is both a layer and a cross-layer capability. Instead of thinking of AI as a separate layer, consider it an integral part that enhances all other layers. AI builds value by using the system's existing data, structure, and workflows to deliver smarter, faster, and more intuitive outcomes.

It represents a shift:

• from clicks and navigation to conversations
• from steps and tasks to outcomes
• from manual work and processes to assisted execution and automation
• In a nutshell, good data --> solid structure --> action and intelligence --> outcomes and results

"Instead of focusing on how to use the system, users can focus on what they want to accomplish."

Working with Russell and Abby. Back working on the search look-up for the documentation project stuff. We were deep in indexes and counts to show the correct search results and setup the deep linking correctly (page and subpage navigation). We got stuck on some JavaScript and looping over sections and showing/displaying the correct search results. Manual changes and checking console logs for index numbers and flow. Deep JavaScript debugging. As we are going along, there is some teaching happening and helping Abby understand why we are doing what we are doing.

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

See attached for some of the little gems and documents.

Working with Bryan on some code review. Going over some of his new code to allow charging a credit card fee on the online bill pay section for ecommerce. It's a new setting that allows or disallows the credit card fee. Fixed a few merge conflicts and pushed up the new code. He wanted it live on data 0 for some testing. After we did some testing, Bryan was just checking in on me, mentally and physically. It's been kinda crazy.

Formatting old user guide entries. Decided to dictate some new content. Working on sales tax settings and then moving into payroll settings. See the general system settings page for details. The eventual goal is to move all of this content to a different place, but I needed a spot to stick it until the other section is ready.

3.3 - Sales Tax Settings

3.4 - Payroll Tax Settings

Meeting with Bryan. He had a code conflict that needed to be fixed. We got in there and I helped him get some of his merchant account settings changed around. We then went through some code. He has a small bug that he will go back and work on. We were then talking about the future and where we are heading and going. I was trying to show him some of the vision of what we are learning and how things get tied together. I bounced to a number of pages and was doing some drawing. Fun little session.

I have so many things, all over the place. I am really trying to gather things together and organize them into a cohesive suite of tools, features, advantages, and benefits. Good stuff. Keep chipping away.

Bryan was mentioning grad school and how sometimes people will dedicate years to a single subject to try to bring it all together. In a way, I'm kinda doing that but without going to school. A giant gathering and refining process. I'm learning tons along the way.

Working with Shannon and doing some editing and content creation. I showed her my session with ChatGPT on the interactive map for adilas. We then spent the rest of the time working and reading over that help file, for the interactive map. Making progress. I really appreciate her help.

Emails and reading articles sent to me from some of my contacts. The articles were about trends in business for 2026 and also talking about macroeconomics and AI use in business. Paying bills, recording expenses, and uploading receipts. General to do list stuff.

Recording notes from a couple of days ago.

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

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

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

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

Working with Shannon on help files and defining parts of the interactive map. We put in a whole new intro section and started moving some of the numbered sections around. Overall, a good session. Here are a few notes for me...

- Go back to October 2010. I was planning things out and trying to figure out where things fit together. There are a bunch of brainstorming documents that deal with what are the topics, what is the scope of each topic, how does it play into operations, how does it play into accounting, and who are it's buddies. That brainstorming session, over days and days, was the initial catalysis for the adilas interactive map. Specifically, we were planning and mapping out how the balance sheet fully works. Here is a link to that info: October 2010 in the developer's notebook.

- It feels like we are slowly coming up the chain... This is an analogy with food and baking/cooking, but it has similar things that have happened with how we pitch and promote adilas. We started out talking about the ingredients, then moving up to the functions of things that you can do, and finally getting to the results and/or what you can create. So, in food, ingredients are things like milk, sugar, flour, butter, salt, eggs, etc. Functions are things like baking, cooking, boiling, mixing, frying, roasting, chilling, freezing, thawing, etc. The outcomes and/or results are things like pies, cakes, cookies, brownies, cinnamon rolls, ice cream, smoothies, etc. This is what people really want.

- In the adilas world, the ingredients are things like invoices, quotes, inventory items, customers, vendors, PO's, expense/receipts, banks, deposits, etc. The functions are thing like POS (point of sale) systems, CRM (customer relationship management), CMS (content management systems), ERP (enterprise resource planning), accounting, inventory management, etc. The outcomes and/or results are peace of mind, clarity, trust in your numbers and the story that you are getting, being able to make decisions, gaining visibility, accountability, business intelligence (BI), digital storytelling, confidence, etc. We are wanting to get there... to the outcomes and/or results. We are only now seeing that we have been spending all of our time telling people that we have invoices and customers or we can do POS mixed with CRM stuff. We haven't quite gotten to the part that people really want. That's where we are heading.

- This little analogy about cooking and baking as compared to adilas business platform and system tools (see above) could be a super fun graphic. We are learning and we need to show what is really possible. In Steve's words, we need to sell the sizzle, not the steak.

Working with Russell and Abby on the documentation project. Talking about traffic control and helping to regulate flow and usage - the job of developers. Making small changes with AI for small tasks in our project. Some good, some bad. Russell keeps using multiple AIs to improve the prompts for the other AI agent. We got to a point that we decided to manually change some of the code. It took a while to find out what it, the AI, had written. We only got as far as flagging some places to check for next time. We did force some values and got it to work, we just need to be able to either pass those dynamic values or have it recalculate them on the fly. We are dealing with search results and correctly showing and highlighting the correct search results within a page or sub section. The code deals with deep linking, highlighting search text, navigation, and setting the correct search index counters to the correct values (result 1 of 5 or 2 of 10 - etc.). Interesting, we weren't making as quick of progress today. There was a little bit of spinning our wheels - going back and forth with AI. We are in pretty deep.

Working with Abby on graphics. Also, spent some time and showed her around in the adilas financials and space (navigating the system). She is working on a new compass graphic - of where you want to go... We talked about adding in some fun business functions and application players (almost like virtual destinations - map and compass - choose your own adventure).

Emails. Then jumped back into reformatting the user guide entries from Shannon back in 2019. Started working on old entries from 4.18 to 4.24. Also, reviewed some key help files for the interactive map and the adilas GPS core.

Here are a few links to what I was working on:

Old user guide entries - You may have to scroll a bit - Web link - user guide entries 4.18 to 4.24

Interactive map help file - Web link - help.cfm?id=393&pwd=map

GPS core layout help file - Web link - help.cfm?id=479&pwd=core

Working with Shannon. Looking at tons of things that need to be done (projects, documents, content, websites, etc.). We have a bunch of half-finished projects. We jumped back into a document called the adilas core concepts overview document. We had to totally rework the first part of the document. We are trying to help show the concepts of world building and how they play out and into the business world building mentality. Fun session. See attached for our current progress on the document.

I was scheduled for a podcast interview, but the interviewer contacted me and had a family emergency. I spent the day reviewing a bunch of older records and entries. Reviewing notes from other people on the team. Looking over my to do list items. Working on formatting old user guide info on the meet the players section. This is old, unharnessed, work that was done by Shannon back in the day (2019). Lots of good stuff. Went from 4.1 to 4.17, meet the players, inside of adilas university.

Web link - old user guide entries in the developer's notebook

Reviewing a few sales and organizational structure documents (business training documents) from Gene Spaulding. He sent me a Harvard Business School document on the 7-S's. It was dealing with a model talking about strategy, structure, systems, staffing, skills, style, and shared values. They all need to work together (the 7-S's) and even help boost one another. It is basically a way to look at an organization and then analyze it on how it is doing (looking at the model). In the document they took the 7-S's, talked about each one, and even broke them down into the hard S's and the soft S's. Mixing and blending each section.

I then opened up and started looking at a sales document dealing with prospecting and building a sales pipeline. I got through the first few chapters. By the way, Gene helps teach some entrepreneur classes up at USU (Utah State University in Logan, UT). Here are some of my notes:

- Framework of process and plays - make a map - personal selling playbook

- The skill of persuasion - we all need it - we all use it every day - just some people make a career out of it - either way, we all use it, every day.

- Most businesses focus on revenue generation of some sort or the other. I know that is important, but... that's not my main goal. I know that it is needed, but sometimes, what drives me is doing what I feel is right. I have to figure out how to make those two things match up (revenue generation and doing what is right).

- Mix of marketing, selling, and customer success - looking at the big picture - see attached for a scan of the sales success pyramid.

Got an email from TechSmith about the value of telling stories in business. I love stories. Working on why stories work in pitching business. Gabrielle Dolan (gabrielledolan.com) and Matthew Pierce (TechSmith - visuallounge.net). Here is a link to the video from the visual lounge site. Stories create a visual. Helping people to be able to retell the story (not word for word) but being able to pass on the gist. Understand, remember (apply it), and retell it. How do visuals play in (actual visuals), and how a good story can helps create a visual in the hearer's mind. It's okay to use a personal photos or a personal story. They help and make it real. Vulnerability can be scary. Even sharing stories of when it didn't work out. Tips: Tell a true story, not just a story. Starts - time and place. Ends - get the message without hitting them over the head. Get to the point (30 seconds, 60 seconds, maybe 90 seconds). Sometimes, it goes into way too much detail. Single message per story. Storytelling is a super powerful skill.

I was going to jump on with Hamid, but he had to help out his daughter. So, I did some light research on the business unmasked podcast. I also spent some time working on my flow for doing screen captures and then marking them up and drawing on them. I tried three different systems and styles. I ended up liking the TechSmith Snagit process the best. I tried Microsoft Paint and the Window's Snipping Tool as well. All of them have different benefits. Snagit allows me to draw and keep recent drawings in the library tray, even without savings. I have it setup so that I can use my print screen key, get a capture, and immediately start drawing and marking it up. I can save if I want, I can also add shapes and use my undo button if needed. It seemed to be the best fit for my presentation and drawing style. Spent some time playing with the different tools.

Went into Bridgerland to participate in the software development advisory board meeting. We met, ate lunch, and talked about the program there at Bridgerland. Lots of talk and discussion about AI and how it is influencing software and web development. I really enjoyed the meeting.

Recording notes from the last couple of days (3/24/26 to 3/25/26).

Working with Russell and Abby. Planning and checking existing code on a small project that we are working on together. Slowing moving the ball forward. It takes time. Trying to have it, AI help us, do some code syntax highlighting. It wasn't able to do that. We rolled back the code. We then tried to have it do a text search function on sub HTML pages. That worked pretty good. Working on project prompts, and how to refine and use those. We were working with Russell as he would do a new prompt and then switch between the different AI applications. Talking about assigning tasks and starting a conversation with other developers. The task is not the end all, all it does is start the deeper conversation of what is needed, wanted, required, expected, etc. Working on the search function. Doing some detail work. Good work session. Abby and I are learning tons by working with and watching Russell.

Working with Abby. We were talking about working with a huge library (all of the adilas assets) and trying to get it all organized. We spent most of the session doing some training. I was showing her graphics and images and doing some drawing to help illustrate what is going on and where things are heading. I really enjoy that.

Main list of tools is on element of time # 4029 inside the adilas university site. Web link - time_web_gallery.cfm?corp=371&id=4029

1. Head and mind
2. Paper and pencil (pen)
3. Computer Based – word processing or a text document
4. Spreadsheets (rows and columns)
5. Databases
6. Software Packages and IT (information technology)
7. Web & Cloud
8. API Sockets or Custom (application programming interface)
9. World Building (digital story telling – ultra custom/hybrid level)

This is the entry for the level 9 or full world building level...

9. World Building (digital story telling – ultra custom/hybrid level)

a. Background: World building is a term that is often used when people create movies, plays, or write books or novels. What these artists or authors do is they try to create a world where you have characters that have relationships, and they make decisions which create consequences, which brings up some sort of a need to overcome something. As these characters interact these consequences become the building blocks of what happens next and it all becomes aimed or focused on fixing some sort of trouble or problem. What we do in a computer system analogy is we allow for those same pieces to be setup and created and for different actions to occur and things are allowed to be reported to other places and so on. It literally becomes digital storytelling.

Some people think that they don't want to hear the whole story but they just want the raw, underlying numbers. However if you capture the story as it unfolds over time it becomes such a rich environment to produce greater information. If you are recording your numbers in this manner over time you can see they are carrying with them the why, the when, the how, the who, the what, and other pieces of information and data that build a rich and desirable picture. Capture and record the story. So in essence, just like an artist or author, you are building your world and creating a story.

b. Features, Advantages, Benefits: What if you could mix and blend all the other tools into one platform or system. The concept of world building is open to all parties and peoples. As a disclaimer some of the pieces that we add going forward might feel like they are pointed toward Adilas. We are doing that on purpose but please know that we don't have a monopoly and we are not the only ones that participate in world building. But hopefully this can help to present the ideas and things that we have seen as we have encountered problems and needs in growing our own system or world.

c. This link is to a document called the Adilas Formula. This is basically a mix of business functions, business players, and concepts that are able to be mixed and blended together to virtually create a world.  https://data0.adilas.biz/adilas_formula.pdf

d. It is very common for computer systems to have lots of fun acronyms. World building starts combining all of these. For example:

Sales, Inventory Tracking
POS (Point Of Sale)

The other part of the adilas glossary (A-J) is on element of time # 4030 in the adilas university site. Web link - time_web_gallery.cfm?corp=371&id=4030

K

• Keep - This is usually some sort of an action where you are maintaining or keeping something for later use. It could also involve something that you do continuously - for instance keep clicking on this, keep drilling down, keep refreshing, keep checking back, etc. Saying either save that or continue on that path. 
• Kill - This is a general term usually meaning to delete, destroy, make inactive, hide, etc. It is a general term that means to get rid of something. Other times you might talk about if it is going to kill the system meaning too heavy of a load, too intense, too many sub details, etc. 
• Knock knock - Who's there? It could be a joke but actually we use it in computer speaking when we are trying to gain access to API sockets. You play knock knock with the server. The server responds who are you? What do you want? Then you have to respond that those questions/requests. It is kind of a back and forth protocol.
• Knox Report - Special sales report for invoices and payments made. It has the ability to show quick stats, counts, and other math totals. You can also run comparisons on different date ranges if wanted. The original report, and all of the columns and/or numbers, were requested by an operations manager named Phillip Knox, out of Canada. Thus the name. It's really just an awesome sales report.
• KPI or Key Performance Indicators - These are a set of values (totals, counts, averages, sums, etc.) that are used to determine how things (people, processes, or campaigns) are doing. Some of these KPI's are used on reports, dashboards, and in other areas. Basically, someone setups up a rule and and benchmark goal. Then things are evaluated based on those key performance indicators.
• Kush Cart - This is a version of the internal shopping cart. The three main versions are the classic cart, the Kush cart, and the mini scan cart.

L

• Labels - Can be printed via browser settings from multiple locations in the database. Item labels can be used to add items to the shopping cart, item labels can be printed from within the shopping cart for certain industries, labels can be printed for plants from the cultivation homepage.
• Label Builder - Special application and/or functionality to help with custom labels. Inside the system, there are various label builders. Some are very basic (auto linked from specific pages to the label generator) and other allow for all kinds of drawing, graphics, dynamic text, colors, rotation, barcodes, QR codes, custom naming, saving, etc. Multiple versions, based on needs.
• Liabilities - Financial obligations of a company. Tracked on the balance sheet.
• Line Items - "Meat and potatoes of a form." Can be inventory items on a PO, expenses on an expense receipt, and invoice sales on a deposit.
• Link - A link could be an actual web link where you go from page to page. These are often used in navigation or drill-downs. A link could also be things that get connected or tied in. Such as an invoice might be linked with a customer or an item is linked with a PO. Another definition for link is an item within a chain of a process. What are the links that it needs to go through?
• Locations - Way to sort inventory, allocate sales tax rates, organize operations in the database. Completely dynamic.
• Lock - A lock usually means that something becomes more secure. It could be locking people out, locking things down, it could be advancing something so that people with lower permissions cannot access or see it. Another example could be a system being put or going on lock down - like the system or a database table. A lock is used to inhibit access. 
• Logout - Function that allows a user to leave the database. Once logged out, another user can log in from that computer. Note.. logging out does not clock out the user.
• Logs - Associated with customers/clients. Area where notes may be kept for historical reference.
• Look and Feel - Basically this deals with what you see. Your interface colors, your color choices, your navigation buttons, your interface layout design, your defaults, your style, etc. The software system allows for all kinds of dynamic colors, fonts, watermarks, graphics, logos, and styling to help with your look and feel. 
• Look Back Date - Usually this means that we are going back in time to look at data or content. Very common for inventory levels, sales, and balance sheet items.
• Loyalty Points - This is the process of assigning points and values (dollars) to a customer or client who purchases from you. These loyalty points can have ratios (how many points for how many dollars spent), date rules, redemption rules, etc. Inside the system, you have to turn it on, but the system will automate this process for you (checkout, accumulation, redemption, etc.). The bigger section is called special accounts and deals with things like loyalty points, gift cards, vendor credits, in-store credits, etc. The use of loyalty points, in the system if built-in, once turned on at no extra charge.
• LPI (Lines Per Inch) - This is a printing term that deals with resolution. Another common one for this is DPI which is dots per inch. Often computer screens and printers deal with DPI where LPI is for professional print shops.

M

• Main - The software application uses the term main in multiple different ways. It could be main homepage, main navigation, main or core logic. The word main might also refer to sub homepages such as main customer homepage, main invoice homepage, main deposit homepage. Going deeper the word main could also mean the starting of the object. Anything that can hold subs is a main. For instance the main invoice details or main element of time. We end up adding sub details, such as line items and payments, to a main bucket, item, or container. It is very common within the application to see the words edit main. This deals with going directly to edit the details required to start or initiate a new object within the system. 
• Make/Model - This is tied to serialized or stock/unit inventory. The make is usually similar to a brand name. Then the model is usually some sort of a sub division within that, that has some known attributes or pieces. In the system we allow you to define the makes/models and the underlying presets that go along with those. These are set up into one to many relationships where one make can have an unlimited number of models.  
• Manager's Time Clock - This is a permission/section that allows a user to oversee time clock records for departments that have been assigned to that manager. Time clocks have three different levels. You have the user level which is easy to add but you cannot edit anything. Then manager's time clock which allows you to add and edit but only at a certain level. Then admin time clock that allows for corporation wide adds, edits, and reports. 
• Mark-up - This usually deals with a pricing model where you take a value and you multiple it by a cost to arrive at a new price. Depending on if you are doing widget (small, bulk) type inventory or serialized (stock/unit) inventory there may be multiple levels of mark-up. Another way that mark-up is used is sometimes on coding language. A mark-up language is where certain things have tags, attributes, and parameters. 
• Media Content - Technically media/content is any kind of file, which could be spreadsheets, text documents, PDFs, graphics, photos, scans, audio files, video files, etc. that may be added to the system. Inside of the application we allow media/content to be added to any of the 12 main items, any of the 12 main player groups, or just generically to the system as a whole. Basically this is your paperless office function. 
• Merchant Processing - This is a general term used to talk about credit card transactions, authorizations, and processing. The system acts as the client side or software piece. It sends transactions over to a gateway which authorizes, confirms, and holds secure data. The merchant part of it deals with converting that data into real monies that will get pushed into the company's bank account.
• Meta Data - This is data about the data. Usually used for database or describing things. Say you have a PDF document. The meta data might be things like the title, the category, the feature it explains or is part of, who created it, the date, the last date modified, the page length, etc. This is just one sample. It is basically any side data that describes or helps categorize the main data. It is used in web technologies all the time. Meta data helps the browsers and search engines know what the page either contains or is for.
• Metrc - This is a state compliance agency that tracks regulated items through the chain of custody and uses their own RFID tags and subsequent system to help in that tracking and training process. Metrc is pronounced "metric", like the measurement standard.
• Mini Conversions - A conversion is where something gets converted into something else. Usually it deals with units of measure. For example gallons of water, liters of water, cups of water, drops of water, etc. The reason we use the word mini conversions is that we are trying to track a semblance of what is happening instead of a full conversion that might be unalterable. These mini conversions are simulating the breakdown or conversion into smaller or bigger groupings.
• Mini Scan Cart - This is a version of the main internal shopping cart. The three main versions are the classic cart, the Kush cart, and the mini scan cart. The mini scan cart is the most flexible and customizable of all of the shopping carts. It has a number of toggle on/off settings, you can rename buttons and even show/hide different possible functionality add-ons. This shopping cart also has a number of touch screen specific options and settings.
• Mix - This could be the mix that you have on your sales floor (what inventory items you have in-stock - example: what's your mix or let me show you my mix) or it could be the act of blending one or more pieces together. Often the word mix is used to mean some sort of combination or process to get a result. Inside of adilas, we often are mixing and blending different business functions or technologies together. The goal is something different than what or where you started.
• Mobile - This could mean mobile as in on a mobile device where the sizing or layout changes based on screen size. It could also mean the ability to carry, transport, or move around. It may also mean the ability to transfer pieces between things - the data can become mobile. The ability of the data to transfer between places such as to different corps, other software, different places in the application, etc. Often you might hear the words mobile app or mobile ready - that usually means a software system that runs natively on android or iOS devices.
• Modal - This is a special popup window that is used in or on a web page. It appears to be a new window, but actually, it is just a layer that sits on top of the other browser window. Without getting super technical, a modal helps show/hide additional information so that the page can remain less cluttered.
• Money Types - Options for making and receiving payments.
• Money Type Settings - List that shows all existing options for making and receiving payments. Boxes may be selected or deselected to customize payment options based on form (Invoice, Shopping Cart, Deposit, Expense)
• More Options - Button provides access to links that are associated with the page in use. At the top of most pages.
• My Cart Favorites - Custom preset buttons that determine how items assigned to those buttons are sold.
• My Settings - This deals with access to user level settings within the software application. This could be anything from password and profile information to default cart types, expense types, Flash buttons, etc.

N

• Ctrl N - This is a keyboard shortcut on windows for creating a new tab in your browser window. Often you can do the same thing by right clicking a tab and clicking new or duplicate, etc. 
• News & Updates - Updates and how to's are posted here to alert users of new functionality within the system.
• Normal Parts/Items - The word "parts" is used to mean any item that is tracked as a group (including labor and services). It is also important to note that the words "parts" and "part number" are editable on a per corporation basis from the corp-wide settings. Specific items are called units or stock numbers (serialized units) and are handled through a different section (usually bigger ticket items). Sometimes the word normal parts applies itself to how things are tracked meaning tracking things in and out.
• Nxtlinq - AI technologies company. The Nxtlinq group helped to make the adilas.biz AI agent "Adi". They are a 3rd party solution in the AI technology space.

O

• One to Many - This is a database concept and usually deals with some main element that may have subs, children, add-ons, additions, or some unlimited number of connections. Some examples could be one customer has multiple invoices or each invoice has multiple line items. We use the concept of one to many to talk way beyond just database things but that is where it came from. 
• One to One - This is also a database concept and usually what it means is a direct relationship. It's the opposite of a one to many. Often a one to one indicates a switch, a toggle, an additional value that may be conditional, an option of being turned on or invoked. 
• Online Bill Pay - This is where a customer would actually get a button, a link, or an email where they could go pay for a statement online using a credit card. 
• Open/Opened - This is a common term that we use to talk about being engaged, active, selected, etc. An example might be open this package, meaning make it active or current. Or open the invoice homepage, meaning go to that page and open it. Or you may hear someone say tell me what tabs you have opened, meaning what do you have showing. 

P

• Ctrl P - This is a keyboard shortcut on windows for printing a certain page.
• Packages - This is used in a number of different ways. Often it deals with batches for sub inventory. Sometimes they are called packages or child packages where you get into parent or child relationship. Packages could get into shipping. Packages could also be used for a certain set of features. For example if you were in a certain industry and wanted to buy the extended package that would be a set of extended features. Sometimes it is also used in the recipe/build area if you are creating certain recipes to create a package, or a kit, or some sort of group. 
• Page Settings - These settings deal with what happens on a single page. As a note there are corporation or world-level settings. There are group level settings such as invoices or PO settings. There are individual settings, there are also these page settings which deal with just how certain pages act, interact, show/hide, react, etc. 
• Parent - This usually refers to inventory and kind of a parent-child relationship. The parent is usually the main element or place holder. We then refer to the parent as the main item and the subsequent children are those related to that parent.  
• Parent Attributes - These are optional but these are classifications and categories that can be associated with different inventory items. These are ways to group and flag your inventories. This can help with sales and filtering of items/products. These are unlimited and often help in categorizing or searching or sub-filtering pieces together. As an example, say you bought outdoor equipment from a wholesaler but you really wanted to make sure that things were known for their brand. Not necessarily the vendor you purchased them from but the brand. This could be one example of a parent attribute but there are unlimited possibilities.
• Parent/Child or Parent - Child - This is a relationship for inventory items. The parent is the main item. If there are differences or a need to track sub data, special descriptions, changing costs, alternate prices, and other attributes, we use child or sub inventory. Super flexible and powerful but does require some additional steps as compared to normal or parent inventory tracking. Not required.
• Parent Inventory - Inventory items. May be sold as is (status active) or may be set up not to be sold (allow subs only) but to act as name holders for sub inventory (see sub inventory). May also be set to inactive if no longer needed for sales.
• Parts - Items or services that are sold. The name 'part' can be changed to reflect the 'widget' inventory and or services. 
• Part Category/Categories - Organizes items into a subset. Technically a part category helps in searches, in your reports, and on your financials. It also helps if you are going to be setting up any sub inventory attributes. Most of your sales reports are done by category at the top level and then by item. 
• Parts Homepage - Main inventory homepage. May search for inventory by vendor, category, or item. Printable views also accessed from this homepage, as well as a multitude of advanced searches.
• Patient - System default is customer- patient is an example of a choice for renaming 
• Payee - Refers to individual or business being paid, either vendor or employee.
• Payments Not Yet Deposited - As invoices are created, payments are applied. This verbiage stands for the state of these payments. They are 'waiting' to be included on a deposit.
• PDF-Portable Document Format - a file format that is used to share data. Many pages in the system may be exported to PDF through the click of a button.
• Percentage Calculator - This is a feature that allows you to calculate a percentage based off of either the cart total or a line total. Once the percentage is calculated, you have an option to alter or change any verbiage that is needed before adding the item to the cart. Often this is done to help cover credit card fees or some other percentage calculation. Normally used as part of the POS (point of sale) interface. Only companies that use this feature need to know about it. Normal retail actions don't use this special calculator.
• Permissions - Over 150 rules that allow or block access to functions within the database.
• Plant Tags - This is a term meaning an RFID tag for monitored items. Usually used in cultivation and harvesting processes.
• PNG Image - Portable Network Graphic- type of image file that is accepted for upload under the Media/Content link located on most forms in the database.
• PO's - This abbreviation stands for both Purchase Order, used to receive inventory and Production Order, used to record and track light manufactured items.
• Post - A post has a couple different things that it could be. One, any time a form is submitted it is called a post in technical terms. A post in accounting usually means let's lock it down and make it tight, also meaning lock it down from lower permission users. A post could also mean when you take smaller details and combine them into a summed entry, this entry can also be called a post. If you are talking about fences, it's the big tall thing. :)
• Presentation Gallery - This is a small web-site devoted to quick sales and marketing slides. The full set is around 50 sides that cover main topics of what we do at adilas. There are sections for essential business functions, application player groups, and core concepts. https://news.adilas.biz/sales-gallery/adilas-advert-index.html
• Printable - View of data that is condensed in order to print more succinctly. Editing is unavailable in the printable view.
• Printer Friendly - This is a term for certain pages and reports. Printer friendly means that minimal navigation or header/footer values exists. Usually, you have to go to that page, say an invoice or quote, and then click a button that says printer friendly. There are printer friendly options for multiple areas within the site.

Q

• Quick Search - This function appears on each page and allows one to quickly search for any element.
• Quote - The step prior to creating an invoice. Can be skipped if desired or created and turned into an invoice.
• QR Code - A two dimensional barcode that holds more data than a one dimensional barcode. 
  
  

R

• Raster Image - This is also sometimes called a bitmap image. Usually what this means is that there are little blocks of color to make the image. If it is blown up to big it can become pixelated. For example, people who work in PhotoShop deal with raster images all the time. The opposite of a raster image is what is called a vector image, which deals with smooth mathematical lines, arcs, and curves. Vector images scale very well because they are mathematically based. 
• Recipe/Builds - Method of selling items grouped together into a 'kit' or 'recipe'. Pulls inventory onto the invoice in set quantities.
• Reflexive Flex Grid - This is a piece of flex grid or flex grid tie-in that goes in the opposite direction. A normal piece of flex grid connects a single record to a source (say one of the main 12 application player groups). A reflexive piece of flex grid does a reverse connection from sub to main vs main to sub. Here is a quick example: Say you have a customer that needs a refund, you could go from the expense to the customer or from the customer to the expense. Either way. The goal is that the items are connected or have a relationship. If you use reflexive flex grid, you only have to make one connection, and the system will do both directions for you. You are trying to tell the story of what happened. Time saver.
• Refresh Queue - A queue is basically a digital line. This could be used for projects, people waiting, people who need to be served, etc. Refreshing the queue typically just means what is the current status or order of these people or things waiting. Some of the pages actually have settings so that the queue will refresh itself at an interval the company has selected.
• Refund - This is the act of returning or giving back an amount for something that was purchased. Inside the system, if you need to issue a refund, you will do a negative quantity (I'm getting something back). Not all refunds deal with items. Sometimes is just money trading hands. Depending on the side of the equation you are on, a refund could be monies going out (someone is asking for a refund) or you could be asking for monies coming in (I was a refund).
• REI's - This is short for a reimbursement. A reimbursement is money that was paid out of a person's pocket that needs to be paid back directly to that person. These are very common in the expense/receipt side of the application. For example, say I was out and bought a new broom and wanted to have the company reimburse me for buying the broom. On a technical side reimbursements in the system must be paid back in full. There is something called a split in the system that you can chip away at an expense and make payments to it but a reimbursement must be paid in full. There are tools in the systems to combine or pay reimbursements in bulk. 
• Reoccurring Elements of Time - Often you will have things that you want to reoccur over and over again such as company meetings, a set/reoccurring due date, even a person's schedule - things that happen over and over again. Inside the system you have to create one primary element of time that exists by itself, then you can tell it to reoccur or choose how to reoccurs. The master needs to be created first and then you can duplicate that master to create the further elements for reoccurring. 
• Reoccurring Expense Receipts - This is some sort of a bill or expense that happens over and over again. This is very common for rent, insurance, draws, auto-transfers from banks, etc. You set up the master and then you can tell it when to duplicate itself and advance it's dates for creating the additional expense/receipts. 
• Reoccurring Invoices - This is charging a customer over and over again in some kind of a reoccurring subscription, or repetitive purchases, etc. Once a single invoice is setup it could be set to reoccurring if there is some sort of constant, regular billing. If the invoice amount changes you may not want to go this route. This is best used for the same items/services and amount reoccurring on a regular interval. Once again you have to have a master invoice and then it knows what to copy. This section inside of the system can do it both automatically and as a manual reminder in case things need to change. 
• Request PO - This PO type is used for ordering, requesting, or getting quotes from vendors. This PO type records all of the main PO info without taking it to the next step (receiving). The PO request may easily be turned into a "Basic Live" PO by switching the PO type. When this happens, the request will hold all of it's original info and becomes received (actual or live). At this point, it will function just as a basic live PO would (inventory counts and payables). This PO type is vendor specific. See corp-wide settings for custom naming.
• Responsive - This has a couple of general meanings. One of the most modern ones is called a responsive webpage, meaning it sizes well for different devices. The layout will change depending on the size of the screen, that is called responsive. Another use of the word responsive is talking about clients getting back with you, vendors, or even the server - such as the server is not responsive meaning that it is not responding to requests presently which could mean it may be asleep or dead for a bit.
• Restore to Cart - This means you are taking something, usually a quote, and putting it back into the flexible shopping cart mode where you can add, edit, change, and use the bulk tools in the shopping cart. As a note, restore to cart is from quotes but there is also an option to duplicate to cart which is taking a completed invoice and restoring it to the cart. 
• Results - This is also a general term. It could mean a goal - what are you desired results. It could mean results of a query - what came back from a search. It could also deal with testing results for something such as new code. Results are also trying to find what you are looking for. What do you get out of this thing that you are looking for.
• Retail - The term retail usually means something along the lines of sales or selling something. Inside the system, retail could be a name of a certain interface or dashboard - retail dashboard, retail homepage, retail interface (POS interface), retail sales report, etc. Retail usually means taxes, where wholesale means non taxed, at the current time of the transaction.
• RFID - Radio frequency identifiers - Used in the cannabis industry to track all inventory and plants. Unique number associated with inventory items.
• Rounding - Rounding deals with the level of accuracy, usually with number. This could be decimals to decimals or decimals to integers. It is also important to know that the deeper you split something apart there might be virtual saw dust or shavings which is referred to as rounding error - trying to get it split apart or broken down as close as you can. Rounding is often used in taxes, discounts, and eventually needs to be equated into money if you are dealing with dollars and cents. Sometimes inside of the system we allow things to be flexible up to 5 decimal points - the term we use for this in the application is the dewy decimal system - this is not related to libraries.   

S

• Sales And Profit - This is a term to show what has been sold (sales) and what the profit or difference between the price and cost are. Sometimes, this is used as a term to mean, how did we do? Inside the system, there are special invoice-based sales report that show this information. The P&L (profit and loss or income statement) also show this kind of information. Sometime the sales are called revenue and the profit is calculated based off of a salesprice minus the cost of goods sold (COGS). Discounts may or may not be included, depending on what you are looking for. Often taxes are left out of this calculation.
• Sales Tax Settings - All settings are dynamic and can be entered on the location homepage. 
• Server (what server are you on?) - All corps are assigned a server that houses all their data. Server number is visible in URL ie. https://data4.adilas.biz
• Settings - Settings are usually some sort of user preferences or default values to help a page or a function configure itself. Inside of the system there are four main types of settings. We have corporation or world level settings. We have group or system player settings - for example invoices, parts, customers, etc. We also have what are called page settings which deal with a specific page function, flow, or process. The lastly we also have a thing called individual or user settings - this is where an individual or user gets to set some preferences such as default types, navigation, other presets and defaults. 
• Shopping Cart - Where sales happen in the database (see also Cart).  The shopping cart is how you sell your stuff. It is the interface between your customers and the entire rest of the system. The shopping cart eventually helps you to create your invoices and quotes. It is literally tied to almost everything in the system. If you took out this piece of the puzzle, not much would be happening. This is the "interface" piece.
• Show/Hide Search Criteria - This is usually a button or a link that helps you collapse or expand search forms. Often pages or reports needs user inputs or filters but showing that right off the bat takes up valuable real estate on the page. So the show/hide search criteria allows you to expand or collapse that when you need to interact with the input, filter, and searching section.  
• Signature or E-Signature - This usually deals with a sales receipt or invoice. A signature is a special written name or approval. An e-signature usually means some sort of digital signature or approval. There are a number of signature settings for invoices, inside the system, including e-signature options.
• Smart Group - Basically, a smart group button is a my cart favorite button that contains all of the functionality of the normal cart favorite buttons plus it allows for pre-set pricing structures (quantities, weights, and prices) to be assigned or connected to one or more inventory items. Smart group buttons allow for both assignments (who gets to play) and rules (how things interact or play) to be set up.
• Snow Owl - This is a look and feel theme or motif. Snow Owl is a series of header, footers, options, settings, and styling for the pages. Originally developed by Russell Moore in 2017. Additional changes have been made. This theme currently has the most modern features, access to tools, functions, settings, and more. Sometimes we talk about Snow Owl in a general sense but this encompasses hundreds of settings, features, and options that are part of running Snow Owl. 
• Software - This is a term meaning any kind of code or program that is installed on a machine. Often software deals with licenses, updates, versioning, etc. Some of it's family members are hardware, firmware, freeware, shareware, and even sometimes vaporware. Even though the system is a web application it is sometimes generically called software. 
• Special Accounts - These are things inside of the system that take on the role of a miniature account of sorts. We use the term special accounts for things like loyalty points, gift cards, gift certificates, vendor credits, in-store credits, punch cards, account balances, etc.
• Special Line Items - These deal with the hardcoded part numbers or "special line items" that are used within the application. Many of them have special uses and special code that is built in to the main application. These are things such as labor, fee, discount, verbiage, other, shipping, trade-ins, and more. Basically these are special parts or items that can be attached to an invoice or PO and some of them even have special treatment on how they are tracked financially on the P&L and Balance Sheet.  
• Special Live PO - PO used to bring in inventory from multiple vendors. This PO type allows the main vendor to be set as the payable (who will get paid), and the line items may contain bulk, generic, or non-vendor specific items. These PO types are used by companies that buy the same item from multiple vendors and don't want certain items to be tracked on a per vendor basis. The items become a bulk or general usage item and are usually maintained under a special internal vendor. 
• Special Parts - This can be two different things, it can refer to unlimited items that don't track quantity such as labor or services, or it can refer to the special built-in application items.
• Special Request - This is the request side of the special live PO's. Very similar to a basic request except it allows multi and mixed vendors. See description of special live PO's above for more info. Once received, all special request PO's will need to be flipped over to the special live PO status in order to show up and become real or live. 
• Specific - Specific basically limits the scope. We use it as a general term and it could mean specific in reference to talking about a specific item or a specific relationship. We also use it when referring to things like corp specific, vendor specific, location specific, user specific etc. Once again it takes that general topic and narrows it down to that scope. 
• Split Cart - Feature that allows user to view shopping cart and my cart favorite buttons on the same screen simultaneously (see M for My cart favorite).
• Split/Splits - This has a number of different features associated with the word splits. This could be split payments - which is typically dealing with multiple locations where you may have to split or divide payments. A general term called splits in the system is a term used for payments that are on account. This is used when you need to pay a vendor and you may owe a larger sum than you can pay right then. You can attribute whatever monies you would like to that vendor's account and it will pay off or satisfy those expenses. Sometimes split can refer to split screen functionality that diverges or splits. If you are dividing revenue sharing you might create some sort of a split.
• Spread - This could mean a spread of what you have (like inventory items or options) or it could be the act of distributing something across multiple areas. The term areas could mean whatever, bills, invoices, payments, security, outreach, etc.
• Start New Cart - Function that allows user to begin a sale.
• Statements - a time stamped report or "snapshot" of who owes you what.
• Status - This term could me a number of things. A status is usually a state of being of some sort. Often, inside the system, a status is either active (use/show) or inactive (don't use/delete/hide). Sometimes the term status could also mean a state of readiness.
• Stock/Unit Cust - A restricted view of serialized inventory. The view is 'customer' friendly, hence the name 'Cust.'
• Stock/Unit Full - A full view of serialized inventory. Includes cost and other info that should be hidden from customers.
• Students - Technically a student is a person who learns. There is a corp wide setting that you can use for your customers and if you happen to be engaged with people who are called students you may change your customer name to student. This can also deal with people who are learning from your media files or procedures. 
• Sub Attributes - Unique information associated with a sub inventory item. This information is driven by sub inventory templates that are created based on the tracking needs of the business (see sub attribute templates).
• Sub Attribute Templates - Templates that carry the unique data assigned to sub inventory items. These are assigned by the business based on tracking needs.
• Sub Inventory - Items in the database that can be sold. Connected to a parent item (parent inventory) which carries the name and some information. Sub inventory is unique and can carry much more unique information (see also Child).
• Switch Corp - If a business has more than one corp they can switch between them without logging out.
• System Assets - Contains all company assets. Deposits, Accounts Receivable, Invoices etc.
• System Basics - Basic permissions and links to preform calculations.
• System Liabilities - Contains all company liabilities. In general all payables that your company owes.
• System-Maintained BSI - Item on the balance sheet that are automatically generated and updated by the database.
• System Maintenance - Section that contains homepages that allow the user to maintain different functions.
• System Management - High security level that allows the user to maintain corp-wide settings and user permissions.
• System Reports - General reports to help you know and understand the company finances, inventory levels and historical data.
• System Time & Requests - Inter company calendar. Used to schedule any 'element of time.'

T

• Templates - Templates are typically grouped settings or presets. It could be a number of settings or permissions that are configured or options that are toggled on and off. Sometimes we use templates in things like sub inventory attributes, elements of time templates (master time templates), we also could potentially use templates to set up corporations on a more global scale - like setting presets for certain industries or jobs, etc. 
• Themes - A theme is similar to a template except it deals with look and feel or what we call a theme. A theme is something that has a reoccurring or overarching premises to it. We do often use this with look and feel and you can see a patter with this, some of these are the classic theme, geometry, Snow Owl, etc.
• Threshold - A threshold is a limit either on the top or bottom of an amount. For example: Say you sell a certain widget item, you may set a max threshold of 50 and minimum threshold of 10. The goal is to stay within your boundaries or thresholds.
• Tiered Pricing - This is the act of automatically applying a price break as the quantity goes up. Inside the system, there are tiered pricing options in the my cart favorite buttons (smart groups) or inside of the parent attributes applied to items for ecommerce sales. Often tiered pricing deals with rules and assignments to different items (assignments) and price breaks (rules).
• Time - Refers to an 'Element of Time.' The object that tracks any data related to time. These are the basis of the calendar and scheduling.
• Time Clock - Time clocks have three different levels. You have the user level which is easy to add but you cannot edit anything. Then manager's time clock which allows you to add and edit but only at a certain level. Then admin time clock that allows for corporation wide adds, edits, and reports. 
• Time Templates - The time templates or master time templates control what the time elements are called. They also control what they allow as far as subs, add-on's, default settings, and functions of time. Think of a time template as a cookie cutter for the actual elements of time. 
• Touch or Touch Screen - Touch can mean a number of different things. It could be an action - who touched my customer log notes? Often, there are system histories to show who touched what parts, pieces, and/or records. It could also mean touch or the act of using a touch screen. This is very common in the POS (point of sale) interface. Certain settings are specifically setup to allow for easier touch options (big buttons or finger related interfaces).
• Transfer - This is another general term. One of the most common usages is what we call an invoice transfer where you are moving product from location to location. Internally we call that a transfer invoice. Another use for transfer is when we talk about a bank transfer - moving money from one account to another account. There may be other uses for the word transfer like transfer of ownership or documents. It generally means something is in movement or there is a change in ownership.
• Transition Invoice - A transition means something that is in-between things. For general purposes a transition invoice is between a quote and a real invoice. We actually allow you to name it whatever you would like. Some common ones might be work in progress, work order, layaway, prepaid invoice, etc. Basically it is something that may not fully be done or finished but we already need to start contributing inventory and payments to the order. On transition invoices some of your normal financial pieces are deferred until it gets changed to an actual customer invoice.
• Try Storming - Similar to brainstorming but with the knowledge that you will be circling back around. You still plan things out, do whatever you are going to do, make your best effort, and then you - on purpose - circle back around. Keep repeating until you have what you want.
• Type - This is a very general term. It is basically a way to organize or flag certain data. A couple of examples might be invoice types, PO types, customer types, etc. We also use virtual chart of account buckets called deposit types and expense types. It is all for categorizing and organizing your data. Another common term for a type is either a category or grouping. Sometimes these can all be used interchangeably and indicate some sort of organization or flagging. 

U

• Universe - Universe inside of the system usually deals with all of the different servers, the different corporations or worlds, and all of the different entities that play together under this larger umbrella. Along this line sometimes we also use the word universal which can mean globally/generally accepted and adapted across the system. 
• Units of Measure - A unit of measure is some sort of a standard way of noting a measurement, a weight, or a length. Common ones might be something like ounces, grams, tons, liters, gallons, dozens, boxes, each, etc. A unit of measurement is assigned to every inventory item. This controls how the items are reduced from inventory and how price is determined in the shopping cart. Units of measure may be broken down further into what are called mini conversions. This is where you have a certain amount of one measurement that creates or equals a certain amount of another measurement. 
• Unlimited Parts/Items - Each inventory item may be specified as either normal, where we count quantities in and out. Or unlimited where we allow it to sell as many as we want, such as services where we don't limit it to an actual inventory value. 
• Update - Update is a general term. Usually it deals with some sort of a database type change where a record gets edited or updated. It is also very possible to update things that are held in memory without hitting the database but usually update refers to some sort of a change, or something new being presented, a feature being updated, or some news and updates letting you know about current or upcoming functionality. 
• Update Cart - Allows user to push new information into the shopping cart during a sale.
• Update Inventory - Function that allows user to update entire inventory via one purchase order (see Update PO).
• Update PO - PO used to update inventory regardless of vendor (see Update Inventory).
• Upload - This is an action. Usually this means a push from one computer to another computer or server. Uploading usually deals with files, images, media/content, or even potential lists of data. 
• URL - A URL is another name for the web address. A web address is usually in the top of your browser and is used for hyperlinks, form submission, and general web navigation. Technically it stands for a Uniform Resource Locator but it is basically just a web address. 
• USAePay - Available merchant processing gateway for internal shopping carts, online bill pay, and ecommerce transactions.
• User-Maintained BSI - Item on the balance sheet that is created by the user and maintained by the user (not automatically updated by the database).
• User Settings - These are settings that are changeable on a per user basis. These could be things like default location, default homepage, a specific invoice type you like to use, if you are paying expenses it could be a certain payment type you typically use, a default shopping cart, etc. Basically they are setting that are changeable to make your user flow more customized and helpful for the user. The number of user settings continues to increase and there are also places that you can setup your own custom navigation, links, buttons, and more to come.  

V

• Ctrl V - This is a keyboard shortcut on windows for pasting a certain selection held in memory. Either Ctrl C or Ctrl X are the ways of copying something to memory. 
• Validation - This usually means that certain data meets or matches certain criteria before being accepted. The system actually uses a number of forms of validation. You can have local validation which happens before anything even gets submitted. You also have server side validation where things get checked on the server before they are able to be used, advanced, or edited. There are also things called validation routines which means multiple steps of validation to help walk through a process. 
• Vendor Catalog - This is a term that is used at an enterprise level. Meaning, a list of vendors that may be added or go up/down the chain for multiple locations, entities, or corporation. It is basically a library of vendor information that exists at a high level and then may be pushed down to sub entities.
• Vendor Credit - This is an amount that a vendor allows as a discount or value that does not need to be paid. For example: Say you bought some things and the items weren't quite right. The vendor may issue you a credit or vendor credit. That means that the next bill or things that you pay for will be less money due to the vendor credit (an I owe you from the vendor). Inside the system, these are tracked as subs of the special accounts functionality.
• Vendors - Any person, business or entity that your company purchases services or items from.
• Verify - Verify usually means a second approval. Dealing with banks on expense and deposits, verifying means that the bank shows that same value. There are tools that allow for what we call bulk verify/verification, posting, etc. A lot of this deals with ways of advancing the ball (data) and saying that it is still good and can move on to the next step. ,    
• View Cart - Shows user current shopping cart information. If a shopping cart exists it will be held in memory and often we use the term view cart to get back to that process. Carts are just saved in memory until you actually submit the cart and create an invoice or a quote. There is usually some sort of button or icon in your header that will help you get back to the cart if it actually exists. 
• View Only - This is a state or status of what is being viewed or shown. The view only status or state means you may look but not touch. Inside the system, there are a number of silver permissions (specialty permission) that allow users to search and view things but not add or edit them.
• View Register - Shows user  current bank information.
• VIN/Serial Num - The unique number/letter id of a serialized item.
• Void Options (all the options) - The act of voiding means you negate or return everything to an original state or a state of zeros. The four main places that things are voided are on invoice, deposits, expenses, and PO's. Once things are voided all of those inventory items or payments are reverted back as if they never happened. Almost every other thing in the system has a status, such as active or inactive, which can virtually be like voiding it or making it go away as well to make something inactive. 

W

• Wholesale - This is normally a sale to another retailer or distributor where tax is not part of this transaction. Tax is attributed on later transactions to the actual customer. Wholesale also sometimes deals in bulk. It has its own special rules and regulations. Sometimes wholesale could also mean a reduction in price or selling things lower than a standard retail environment. 
• Widget - A widget is a general term. Widget could mean a small computer application such as a Flash widget, an HTML widget, a mobile widget, etc. This is also a general term used to talk about general inventory items or non-classified items. For example, you might need to update your widget inventory to show the new prices. 
• With Tax Included - This is a tax setting where the company sets a fixed price out the door and then the system back figures what the tax should be to make the price plus the taxes that out the door pricing. The brother to this setting is called normal taxable and that takes the item price plus the tax which then comes up with a new total. 
• World - This is a general term. Often it denotes some sort of sphere or area that has certain characteristics. Another synonymous term is something like land where we might say eCommerce land, invoice land, or invoice world - denoting when you are in separate areas. Another definition for a world is a corporation or an entity. Often we use this when talking about world building. When we talk about your world it is your business entity. 
• World Building - World building is the act of gathering all of the different pieces and putting them into play in a system that simulates your world. Disclaimer: the term world building is used by authors and those in film to build a world with characters, cause and effect relationships, some sort of trouble or problems, and some sort of a goal that ties these things together. This creates a symbiotic relationship. 

X

• Ctrl X - This is a keyboard shortcut on windows for cutting a certain selection and putting it on the clipboard for future use. Ctrl V is used to paste.
• X-axis - Part of a 3D model. Time is the x axis (bottom or horizontal side to side). Time goes in both known directions (forward and backward).
• X-out - This is usually a quick way to say X out of that, X that, close that, kill that, remove that, etc.  

Y

• Ctrl Y - This is a keyboard shortcut on windows for redoing something that has been undone. It's brother command is Ctrl Z or undo.
• Y-axis - Part of a 3D model. Money is the y axis (vertical or up and down). The y axis may also be referred to as resources. Not all resources are money but they do go up and down as things happen and business flows. 
• Yearly/Year - This is a term denoting the time period of a fiscal year (accounting) or a physical year (general time period).

Z

• Ctrl Z - This is a keyboard shortcut on windows for undoing a previous action. It's brother command is Ctrl Y or redo.  
• Z-axis - Part of a 3D model. Space is the z axis (depth, front to back and/or layering). This axis deals with additional details. What is happening? Are things moving? Are these things part of some other piece? What are the additional details that give more depth and understanding, that make it a rich story.

Going over emails and reading up on Touchstone business advisory recommendations and options. They sent us a list of services that they provide along with some ideas, direction, and fee structure. This would be for selling all or part of the adilas business. Just checking out options. I sent Charlie an email back with some questions.

Fixing elements of time and breaking up bigger URL web links. They, the bigger URL's, wouldn't save as a PDF without running off the page. Small formatting changes. Prep work.

Meeting with Charlie Spickert from Touchstone. Good meeting. He said that he was going to send me some more information and such. Going through the tools and where we are heading. Getting insider information to a specific business vertical and then building out to that level (industry specific skins or business vertical skins). Where are we headed? Helping to get people to buy into that vision.

Working with Shannon. We spent the whole time bouncing between older entries and reviewing recorded chat sessions. Here are some of my notes.

1. The Why (concept layer)
2. The What (structural layer)
3. The How (applied layer)
4. The Mechanics (deep dive layer)

- The timelines help to show what was happening when. That also shows the why, who, how, etc. Time helps tie things together.

- Pulling it all together over time

- Tools that we use - we read over this entry - Web link - time_web_gallery.cfm?corp=371&id=4029

- We tend to talk about features - very feature heavy. What about the other parts such as features, advantages, and benefits. We are only coving part of the deal.

- Maybe circle around and look at the database documentation and UML diagrams. Lots of info and story there.

- Move the vocabulary around so that you can see it more and be able to search it. Maybe even put it into the help files.

- Shannon and I were talking about how originally, I was planning on working on getting some investment monies. That process has slightly changed, and it is getting more of an education type feel to it. Both are still important, I am really enjoying the education part of the puzzle.

- Being "lost" - both virtually and figuratively - how do you find yourself or what do you do when you are lost - maybe pause - maybe try to get to high ground - look around.

- Review

- After meeting with Shannon, I had a few minutes before my next meeting. I went outside and ended up walking (hiking) in the mountains behind my parent's house. They are really steep.

- I am kinda like a digital explorer.

- Deer trail traction - on a steep side hill, you take what you can get and you are so grateful for that game trail or deer trail traction. You may not want to take another person on it, but it helps and works for you as you explore and look for better options.

- I want to smooth out the way for others. That is important to me.

- Educating

- Combining and Mixing

Emails and finishing up notes from last week (3/19/26 to 3/21/26). Light research and reviewing notes.

Phone call with Steve. We had to play a little bit of phone tag, due to connections. Once we got connected, we had a good conversation. The main things that we were talking about were dealing with removing friction and rub on the client side of the equation. Making things easier and easier. We talked briefly spoke about some current projects like Metrc updates, merchant processing, and CardPointe and Clover server issues and threading. Here are some of my other notes:

- One of Steve's biggest goals is to get AI fully integrated into the adilas system. Almost to the point of a simple chat-based system that could handle and process natural language and then be able to help the user do anything inside of the adilas system. Not just navigation, education, training, and consulting, but actual physical tasks. Instead of clicking buttons, navigating, and running reports, you could just talk with the system, and it would be able to help you. That is one of his main goals. It may take some steps to get there, but a cool vision.

- Along with the idea above, of a system that could do anything (AI super system), he was talking about a flow process like this... From left to right... Something comes in, it could be a bill, receiving inventory, doing a sales transaction, whatever... The middle would be the chat window and super simple interface (almost nothing structured). You tell the system what you want to do and it helps you do it. If it needs more information, it would just prompt you and help hold your hand. Then on the right, or the output window, you could get your results and/or confirmation that the task was completed. The results don't even have to be reports that we have programmed. It, the output and/or results, could flex, based on what was asked and/or being worked on.

- I was expressing that I liked the idea, and I could see how it could really help in some situations. This is just me, but I don't think that every person wants that. Yes, it could be an awesome option and could speed certain things up. However, if it was a repeated process, that would be a pain to keep telling it what to do. It might take longer to explain it than it would to click two quick buttons (from a pre-built interface). There are a lot of assumptions being made. One, it (AI) would have to have a super deep knowledge of the system and all of its possibilities. Someone would have to help set things up. We would need to record those instructions in order to repeat those processes. Things change as time goes by, someone would have to be able to edit things, etc. We would also want it to keep learning on the fly. Technically, each person, even across the same business, would have specific needs.

- Without being a "Debbie Downer", I could see something like this being possible as a phase 4 or 5 of working with the AI agents. Phase 1 would be integration and doing simple existing navigation and use of tools. Phase 2 would include education and training on existing pieces. Phase 3 could be where we start letting the AI agent have access to raw data through API's and special AI tooling. Phase 4 we would have to introduce ways of creating some kind of assembly or package for the AI agent to follow (recipe/build type mentality). Then maybe a phase 5 where the system is trained and enabled to help with all kinds of stuff. This could be super deep. Say a person has a picture of something. Do they want to enter it into the system, store info, check something off, etc. It's a little too open right now. This is my take on it... but it would have to be a phase 5 ish type thing.

- As Steve and I were talking, we were talking about AI, bots, robots, agents, etc. Steve was saying that they are all combining into just the AI (artificial intelligence). The words bots, agents, etc. may go away. They are somewhat merging (lines are blurring). There is some mixing going on.

- I loved his ideas on helping our clients get rid of heavy learning curves, manuals, processes, etc. Decrease the friction and the rub. I love that. It just takes time and money and development (and a plan) to get there.

- We talked about the fact that some (most) people don't want to watch a hundred videos or read a huge, big user guide. They want it to be easy.

- Some of what we were talking about might even be the next steps (future) beyond the value add-on core model and/or the fracture UI buildout.

- Trying to listen to what our clients are saying and telling us. That is important. This came from Russell, long ago - Our clients want something that is easy, powerful, and looks nice. If they can get those three things, it will sell.

- I wanted to record these ideas... part of the idea farming stuff that we are doing. We record things, plant them in the ground (sit on them or think about them), and then finally roll around to see if we can make something out of the ideas. Ideally, we get more and more activity on certain things and that helps us know what is being asked for and/or required. Fun process, but it does take time and feedback loops (over and over again).

- For me, when I got home, I scribbled down some notes and drew some funnels, mixing of tools, and even possible stacked or reverse funnels. All of this deals with getting something, mixing it together, using possible tools, and then getting an output (of some sort). Sometimes, once you get an output or result, you have to remix it or send it through another funnel to get what you really want. Break it down, transform it, summarize it, expand it, or whatever... some kind of action to either pull, mix, create, and/or alter something. As a note for me, I have some old graphics that I was working on back when I was doing some developer intern training. These guys had to produce something (desired output or a result), but the starting spot varied. They could use tools and then produce the desired output. I might tie back into that concept.

- Dealing with the concepts for the developers (listed above - inputs, funnels, mixing, blending, and getting outputs). I found some of the old entries. They were in 2/14/2015 and then again on 3/6/2015. If you want, check out these entries and look at the image galleries for expanded visuals. I also added some of the old handwritten notes and scans to this element of time. These entries also include some concepting on the 3D calendar. All playing through around the same time. Kinda fun. Enjoy!

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

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

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

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

Recording notes and doing some organizing and research. Everything is moving so fast. Reading up on some tools that we use. Adila university - entry # 4029. Basically, a ladder of possible tools that all of us use until something breaks. Then we have to virtually go up the ladder to the next best tool. Fun entry.

Working with Shannon. We jumped into some older documentation for the adilas user guide. We were in the financials and accounting section, section 11. We read over the first few entries and then got to the section new school accounting. It was mostly done, but not fully done. We started working and Shannon was asking what do you really want here? We did some quick brainstorming and then I showed Shannon a small graphic from years back. See attached for a copy of that graphic. She then recommended that we use voice to text, explain what we wanted to, and then see if ChatGPT could interpret our babblings. It did a great job! Fun chat session with ChatGPT on some accounting concepts. There are some hidden gems in the comments, after it interpreted what I was saying. Good stuff. As a note, there is a web link to the chat session as well as PDF version attached to this element of time.

https://chatgpt.com/share/69bc3d35-4230-8007-a52d-e6b549493127

Multiple smaller sessions, working on research for roll call accounting and how that plays into the data assembly line. Gathering information, reading notes, looking at scans and graphics, checking dates, and making plans. Towards the end of the session, I had to go in and make a number of changes to the developer's notebook, to fix some formatting and small edits.

See attached for a copy of the information for the adilas user guide, section 11, financials and accounting. Some great stuff.

11 - Financials & Accounting
11.1 - Bank Reconciliation
11.2 - P&L - Income Statement (logic and flow)
11.3 - Balance Sheet (logic and flow)
11.4 - User-Maintained Balance Sheet Items
11.5 - Adilas Theory on Accounting
11.6 - Roll Call Accounting Principles
11.7 - Old School Accounting vs. New School Accounting
11.8 - Vision for the Future

Working with Abby and Russell on the web documentation project. We were doing some code tasks and modifying logos for the new web layout. We were having it (Claude AI) add in some new CSS variables to help with primary colors and highlighting to help tie-in light modes and dark modes better. We added a copy code button to the code block section. This allows us to show something like some text or a code snippet, and then have a quick copy button to help a user copy the content. All of those changes went pretty well. We then tried to get it to help with adding in color coding (syntax highlighting) for the code blocks. It really struggled on that. We just rolled it back and will keep going next week. Fun to see both the successes and the failures. It does take time, but it can also save time, when it works. Fun exercises.

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

Research on the data assembly line, new school accounting, and 3D levels. Found a bunch of old entries that Shannon and I were working on for the user guide. See section 11, for concepts on financials and accounting. Here are a number of links to show where some of the information is.

General adilas notes from back in 2008. This is when Brandon and Steve were working on the balance sheet. This is when the concept of allowing the data to flex until everything is correct or back to a stable spot. Web link - developer's notebook - balance sheet stuff in 2008

Writing out the progression of what we have learned thus far. These entries go forward from 2008 to the end of 2014. These are some notes from Brandon while helping to train some new interns and developers who were helping on the adilas project. These notes will be shown in two sections. One is the general notes from October of 2014. They will show the general flavor of what is going on at this time in history. The other notes will be specifically 10/14/14 where the actual entries hit the developer's notebook. Here are those links:

Web link - October 2014 - General developer's notebook for the month of October 2014.

Web link - time_web_gallery.cfm?corp=371&id=2894 - Specific date in time when the concepts first hit the notebook as a single entry. Progression of operations and accounting.

The next major time period was in March of 2015. This was a different set of developers that had questions and wanted to see how operations and accounting played together. This will have two sections as well. This will have the month of March 2015 and then a specific time when the process was described in more detail, with a slightly different flow, which helped in presenting the ideas. Here are those links:

Web link - March 2015 - General developer's notebook for March 2015

Web link - time_web_gallery.cfm?corp=371&id=3618 - Specific date when the process was explained using a giant Whiteboard at Bridgerland Technical College.

Working with Bryan. He was showing me some of the work with Google Gemini as an AI agent. He is playing with a small chat option to help to use Gemini within the adilas website (certain tasks or to help with repetitive work). Bryan was talking about having a small team spending some partial time on some of these projects (a few hours a week). That would help us make progress and eventually getting things done on the trickle affect (drop by drop or drip by drip). Talking about the sales engine and pushing on projects that will allow other people to help sell adilas. Showed Bryan some of my AI chat messages.

Web link - time_web_gallery.cfm?corp=748&id=12760

Adilas Key Contributors:

Steve Berkenkotter - Main owner and business partner - original ideas, concepts, and training - sales, relationships, dreamer, visionary, custom code, coordinator, builder of the first industry specific skin, and the list goes on. Huge player in the adilas story and timeline. One of the original owners in Moring Star Automotive - where the system came from. There are three known Steve's in the system notes. Most of them are this Steve (99 out of 100 times). He won't admit it, but adilas was his brainchild.

David Berkenkotter - Steve's brother and business partner in Morning Star Automotive. David was a system user and helped us create the adilas quick search. He liked using that feature, the quick search, but it only existed on one page originally. He wanted us to put it on every page. That ended up being in the header. He was also one of the original partners in adilas. Power user in the system. Sadly, he passed away due to cancer.

Shari Olin - Commonly known as "Shari O.". She worked in the accounting department back in the Morning Star days. She has been somewhat of a mother hen to help all of us crazy chickens keep going. She helps with customer support, training, payroll, bill collection, and tons of backend office functions. Major power user. Just being silly, but she can have the mouth of a sailor but the heart of an angel. Part of the adilas admin team and a great friend.

Craig Leitner - Also part of the original Morning Star team. Craig was the automotive floorplan and bank guy. He is a power user in the system and does a lot of bank reconciliation and other tasks. He currently works with Steve and asks as the adilas controller (money flow guy).

Cory Warden - Originally an adilas rep and consultant. Cory become part of the team after being a rep for quite some time. She helps with customer care, client support, project management, and keeping the team on track. She also does all of the news and updates and other training material. Cory does tons of oversight type services for our clients. Power user and part of the admin team.

Sean Carlton - Sean was a manager at a Cannabis dispensary in Colorado that used adilas for years and years until they sold. Steve recruited Sean to help with sales, deployment, and training. Sean brings lots of usage experience. Often, he is one of the helpers if we need to send someone onsite to help with a deployment or training session. Power user.

Brandon Moore - I'm one of the guys that writes most of the developer's notebook entries. Originally, I was hired by Morning Star, the automotive dealership, to help with data entry, accounting, and website stuff. I ended up being one of the main adilas developers and architects. I build content, write code, help other developers and team members, and help with training. Helped start the project back in 2001 under the Morning Star name.

Chris Dunsey - One of the first adilas interns (developers). Helped with a number of projects. Ended up being somewhat of a consultant later on.

Shawn Curtis - Kinda a funny story. He was taking a developer's class at Bridgerland. He knew my brother Russell. He asked to join our developer class and became one of the first interns along with Chris Dunsey. Shawn ended up helping with payroll and other projects. Some of the photo galleries in the system came from Shawn's help. He also worked on the media/content (file upload) pieces. Later on, he did more payroll work and acted as a buddy to Brandon and did some consulting work. We worked together for years and years.

Russell Moore - Russell is my younger brother. Originally, he was added to the group because of his graphic skills. He ended up being a great backend developer and project manager. He has also acted as a trainer and mentor for Brandon along the way. Much of the current system came from projects and efforts that Russell was involved with. He has also been Brandon's AI tutor in recent years. Great help to the system. Huge contribution.

Chris Johnnie - He is an entrepreneur who teamed up with Russell to help create a company called "Adilas For Business" or "AFB". Eventually, both Russell and Chris sold their pieces back to adilas. They were honestly the first ones to really try to run as a white label of adilas. This was back in 2015 and 2016. Chris really helped to push the product to the next level along with Russell's help.

Danny Shuford - Longtime friend of Steve's. Danny helped with some website design, sales, and videos for adilas. He even got into creating custom PDF labels for clients. Light development work.

Marisa Shaw - She is Danny's daughter. Danny brought her to an adilas training event in Denver, CO. Marisa was the star student. She ended up helping with some graphics, flyers, marketing material, teaching, instruction, and planning. Power user. Very helpful.

Shannon Scoffield - Shannon is Brandon and Russell's sister. Her maiden name is Shannon Moore. Huge help and virtual assistant to Brandon. She has helped with training, project management, and content creation. Most of the major content sessions were or have been with Brandon and Shannon working together. When they, Brandon and Shannon, were traveling, Shannon was one of the primary adilas instructors. If she was teaching Brandon was taking notes. If Brandon was teaching, Shannon was taking notes. Power user.

Cheryl Moore - Cheryl is my mom. What an asset. She owns a small business and has owed a few different ones. When we were doing training sessions, she came to every one of them. She asked wonderful questions and was a great supporter. Sometime, I would use her as a test subject - can my mom do this? If yes, we are good. If not, we may need to keep tweaking it. Thanks mom!

Wayne Moore - Wayne is my dad. He was my hiking buddy and more than willing to talk about ideas and concepts on our walks and hikes. He helped out with video stuff and was a great coordinator for making other connections. He worked at Bridgerland (technical college) and helped us get setup with classrooms, computer labs, and other great connections. Huge cheerleader! There is another Wayne, Wayne Andersen, he is a backend developer, systems guy, and database guy.

Wayne Andersen - This Wayne lives in Portugal and helps with all of the backend security, server, and code testing. Major skills, writes code, helps push all of us to new technologies, partially retired but loves to play with tech stuff. If you search for Wayne and it deals with concepts and coordination stuff, that's my dad, Wayne Moore. If you search for Wayne and it sounds like a master backend guy, that's Wayne Andersen.

Alan Williams - One of the lead developer's at adilas.biz. Alan joined us in 2015 and quickly came up through the ranks. Trainer, CTO, team lead, master developer, prototyper, and system architect. Alan has helped with many projects and features over the years. He also helped Brandon with some of the prep work for the adilas lite (fracture) plans and project. Sometimes called "Dr. Alan" by the other developers. Example: This might be a project for Dr. Alan.

Bryan Dayton - Bryan has been one of the most versatile guys on our team. Originally, he joined a development class out of curiosity. He and Brandon live in the same town and know each other from church. Bryan has done more custom code or small system projects than almost any other developer. He also joined the team in 2015. He helps with sales, custom projects, pushing on projects that he thinks will yield a return. Lots of work on the adilas lite and fracture project. Very hard working and versatile.

Dustin Siegel - Developer who helped with numerous cannabis and cultivation type projects. He worked directly under Steve to help with that business vertical. Many of the original pages that Steve built were taken over and remade by Dustin.

Eric Tauer - Developer and custom code guy. Originally, Eric knew Steve and lived in Salida, CO. As a note, adilas is Salida spelled backwards. Eric has a background in database work and data warehousing. Eric has done tons of custom systems for clients. Often, Eric would pioneer certain features or logic, as custom code, and then we would bring those features into the main adilas application.

Garrett Kirschbaum - Adilas intern and then full developer back in 2015. Stressful time of building and expansion. He and others helped run the adilas shop with Brandon's help. Garrett was a great developer and helped us standardize a number of tools and features. He was the first developer to work on sub inventory, back in the day. He also did other projects and helped with some developer management stuff.

Charles or "Chuck" Swann - Charles was an instructor at Bridgerland for web development. He builds custom websites, does amazing mock-ups, prototypes, and is a CSS master (styling a website using code). Chuck worked with Russell to help with redesign work, projects, and vision. Chuck worked fulltime for a number of years and now works and coordinates work done by a small hand-picked design and development team. Anything that needs some design loving gets passed over the Chuck and his small team.

Steve McNew - Friend of Steve Berkenkotter's. This Steve helped prep some whitepaper documents to help with getting adilas standardized and some internal audit type stuff. Mostly white papers and putting things down on paper. He ended up getting hired by the local school district and wasn't able to finish the process, but he got it started. He asked some great questions, and we had some good conversations.

Abby Elkins - Abby is Brandon's daughter. Her maiden name was Abby Moore. Abby, when she was little (10-12 years old) helped with some of the original concept artwork for adilas. Later on, she helped with content for the presentation gallery and then the adilas lite plans (fracture). Currently, she is working graphic artwork for different adilas pages. She's now in her mid 20's and has some awesome art and content skills.

Aspen Moore - Aspen is Abby's younger sister and Brandon's daughter. Aspen helped Brandon with some planning and counseling (mental help). Aspen also did some general business consulting with her dad Brandon.

John Maestas - Developer, backend server guys, and designer. John came to us through Dustin. John was uses as a jack of all trades on the backend and frontend. He did numerous projects, documentation, payroll, and page redesign projects. John was also very help to Brandon in working on the notes and comments on the SWOT analysis document. Many other projects as well. Good vision of the future.

Kiva Berkenkotter - Steve's wife. She helped Steve with various projects and planning sessions. At one point, she was in charge of paying commissions and collecting monthly reoccurring payments. Huge supporter to Steve!

Heather Moore - Heather is Brandon's wife. What a trooper. Cheerleader, support, ideas, and consulting. Huge asset to Brandon (me). Thanks Heather!

Jonathan Wells - Designer and mock-up guy. He helped to map out the system and created a number of deep mock-ups for adilas lite (fracture) projects. Great job catching the vision and putting those pieces into a visual representation. We still refer to his work when talking about fracture (future project for adilas).

Jonathan Johnson - Business consultant from Epic Enterprises. Met with Brandon and Steve in end of 2019 into 2020. Really helped us see some needs and opportunities. Later, helped Brandon with some other consulting when trying to define the fracture plan.

Calvin Chipman - Windows software developer. Calvin also did a bunch of web-based work, database stuff, label printing, and API socket stuff. Calvin was the first developer to use the adilas API's to create a native mobile app for a client. He also built a number of special developer tools used by some of our team to speed things up. He's the tool guy!

Cody Apedaile - Bryan Dayton's cousin, Cody helped with a bunch of JavaScript code and changes. He also spent some time working on the UML diagram for the adilas database. We didn't get things finished, but he was working on a new build your own interface (custom to you) for adilas. We ran out of funding. We want to get back to that project at some point.

Dave Forbis - Dave was the official "high tech gofer". He did a bunch of things. Graphics, project management, brainstorming, planning, sales, and helped with managing developers for the adilas shop. He was another great student. He came to a number of training courses and brought so much to the courses. He was also a big support to Brandon during some rough times.

Josh - There are three Josh's. Josh Wheeler, Brandon's friend and developer. Josh Sagert, developer and adilas user (worked tons on the discount engine), and Josh White, Steve's friend from California. Josh White has brought us a number of bigger leads and bigger players, like franchises, and other higher-end clients. Anything recent is Josh White, from California. He helps with networking, sales, and dreaming of new things.

Suzi Distelberg - Sales, training, and deployment. She also worked with some custom projects and doing step-by-step user guides. She has helped with all kinds of projects and even gone onsite for setups and training. Great asset!

Kelly Whyman - Kelly is Dustin's wife. Kelly was single handedly the best independent sales rep that adilas had. She did training, consulting, and sponsored a number of custom projects. Kelly helped Steve and Brandon with reports, functionality, and other things. She got so good at things, state contracts snagged her up to work at state and multi-state level stuff.

Molly Hennessy - Molly was another independent sales rep and consultant. She had numerous clients and got into doing SOP's (standard operating procedures) and other high-end documentation and training. Molly was an entrepreneur and even started creating some of her own product and services. If you search adilas on google, some of the other results are from Molly. Super creative and a great consultant.

Hamid Karbasi - Developer - He has worked with Brandon doing small websites, training, and small tasks. He currently is a manager at a retail store and brings some managerial type skills to the table. Willing to talk about concepts and how they apply to retail and other environments. He is also lightly helping with some planning for fracture.

Gene Spaulding - Friend, entrepreneur, and businessman. Gene is an old college friend. We had a number of friends in common. He has been a small mentor to me over the years. Way back, before adilas, he helped me get my first business loan for a project that I was working on.

Sharik Peck - Friend, entrepreneur, public speaker, physical therapist, and businessman. Good influence and mentor in ways. Sharik and I used to exercise together back in the day. Many of fun walk, run, and weightlifting session. Learning some conference and training skills from him and his wife. They have done really well pushing their product lines and doing some marketing. Trying to get some ideas.

Bridgerland Technical College - Use to be Bridgerland Applied Technology College. Not a person, but a huge help. This is a local technical college in the Logan, UT, area. Brandon's dad, Wayne, worked there. Tons of assets. They provided classrooms, training options, computers, and even an small incubation spot (starter office space) for the adilas shop during the startup phase. Huge asset!

McCorvey's Pro Shop - Also known as Bowling World. Client that had multiple locations. The started out with around 30 and grew up to the 90+ location level, all using adilas. Long time client.

Emerald Fields - They were the first client that wanted their own fully dedicated box and server. They had multiple locations and requested some custom code, reports, and features.

Beaver Mountain Ski School - Client that we helped them track their ski school (snow sport) lessons. Students, instructors, classes, and schedules. Custom interface dealing with elements of time and flex grid.

Bear 100 - This was the first event or annual event client that we did. They used the system for about a week each year. They had 350+ runners and their families that would be on the site for multiple days straight. It was a 100 mile running race with 13 aid stations and a small social portal for the family and friends to watch their runners. This one was special as it had custom input options to upload CSV files to populate the database vs normal HTML form field entries. Records were sent in batches from remote places to adilas for storage and race progress.

High Valley Bike Shuttle - Online ecommerce and scheduling client. They also have a cafe and small retail store. Fun online scheduling and bulk flex grid projects.

Herbo - Mike Roundtree, owner of Herbo, was the first company to do a small white label of adilas. Mike has been a great asset to Steve and the two of them have worked on projects, plans, and dreams. Herbo also has a custom payment solution that they are trying to market and get rolling. Mike has been a great supporter for years. He is also a certified CPA and that credential helps us and him. We would like to get other CPA's on board as well. Thanks Mike!

Nxtlinq AI - AI assistant. These guys really pushed us to get an AI agent inside of adilas. Tons of development took place and lots of prep stuff. We wanted to do a 3-part plan for integrating AI. 1. Teach it how to navigate using the AI quick search (check - done), 2. Teach it all things adilas. and 3. Teach it how to be clear up at the consultant type level. We only got the first phase done. Lots of other plans and such, but we ran out of funding.

Grok AI - Steve loves using Grok. He has built a number of image generation options inside of adilas. He is also working with Grok to feed it data to help with analytics and AI insight. This is not finished yet, but we may end up using Grok as an AI assistant inside of adilas. We have simple and emerging connections available right now but need to really polish things up before going live with the AI assistant options.

ChatGPT AI - We have started using ChatGPT to help with code, explanations, explore resources, planning, and help with training and flow for people and other AI bots. Currently, Brandon, Steve, Bryan, Alan, Josh, Russell, Chuck, and Wayne are using AI in either ChatGPT chat sessions or some other form of AI. We have some using Copilot, Gemini, Claude, etc. AI is actually helping in many ways. ChatGPT is a big one for use. Anyways, they are earning their place in the adilas key contributors list.

There are so many more that I can't list. Developers, users, power users, reps, consultants, trainers, clients, accountants, friends, family, and even critics. They have all helped out the idea farming process and progression. Good stuff! We couldn't have done this alone. It takes a community to do what we are doing.

Emails and then putting together a document of main people who have helped with adilas (key contributors). This is people who helped build it, define it, use it, requested certain features, paid for certain things, and people and businesses who have been an influence for good in the building process. See element of time #12769 in the shop for the list of key contributors and such.

Working with Shannon. We were talking about how much there is to do. She was saying, maybe doing things lightly vs jumping in full tilt and trying to do everything. We spent most of our time working on some master menu items with ChatGPT. Reviewing the chat document and then pushing it to the next level. Some great new progress and ways of showing things.

We worked quite a bit on results and desired outcomes today. The new chat session covered some new topics like the adilas knowledge tree or knowledge map, the adilas universe map, multiple engines (people engine, business engine, data engine, AI engine, knowledge engine, AI engine, and results engine), the adilas value flow model (1. People, 2. Actions, 3. Data, 4. Insight, 5. Results, and 6. Learning), the adilas universe model, adilas galaxy map, and my favorite part - business function to result indexing or result mapping. Great session.

Here is the ChatGPT chat session link: https://chatgpt.com/share/69b8cb40-042c-8007-bd59-9631c92d2137 - As a note, the first request contains a list of HTML menu list items, if that looks scary, skip that part, the rest is in plain English and has some great information. See attached for a PDF version of the chat log.

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

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

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

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

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

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

Emails and feedback to Chuck on some adilas pricing stuff. He sent us an email saying that some new pricing stuff was live and online. Small page review and sent him a few small changes to make.

Online sales build with Oscar of ChannelBox

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

Back on 3/12/26...

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

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

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

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

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

--- General Outline ---

Master Category
Adilas Strategy Hub

Branches
Messaging
Adilas 3-Part Pitch

Community
Adilas Community Strategy

AI
Developer Notebook AI Training
AI Training Roadmap

Strategy
The Adilas Value Formula
Deep Dive Strategic Topics

Future
Future Projects & Concepts
World Building

Infrastructure
Data Assembly Line

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

Working on back-ups for elements of time. Light clean-up of some of the older records. Some of the older records were quick copy and paste stuff from emails and other documents. When they were directly copied, the resulting records still had some other or outside formatting on the records. That made them look different or funny, compared to the other normal typed or entries.

Recording notes and pushing up some images from Abby.

Back cleaning up developer's notebook entries. Pushing up some images for Abby. See the jellyfish model page for new images. Then back to saving back-ups and cleaning up older entries (changing some formatting and removing long links).

Working with Russell and Abby. We jumped in and were talking about a small mock-up that Russell is working on for a budgeting app. The first part of the meeting was a mini layout critique of sorts. Here are some of my notes.

- Talking about AI, what it can and can't do,  and getting some good ideas. Often, it helps creating a good starting place or places for your project. Depending on the detail level, it may do the first part or the whole thing.

- Talking about context windows (what it can take in and apply to the current project) and how to keep things consistent along the same lines.

- Russell was showing us some character animations and what they are doing to help AI keep things straight. Realistic references - consistency - character drift - you need a reference from almost every angle. Also mixing both text (prompts) and images, keeping it consistent.

- Russell was asking Abby about basic flow, just based off of what was being presented in the visual. What is next and where can I go? What should I do? Getting input and feedback. Basically, user feedback tests or UX tests.

- We talked about tours and walk throughs. Sometimes helpful and sometimes not. Ways to help the user get oriented.

- As we were talking, Russell was gleaning information from the us (his fake users). You have to record that feedback and those ideas. No way that just one person could think up everything.

- Being intentional in your decisions.

- Talking to people about your product, using mock-ups (visuals and flows), vs just building it. Good design and planning go a long way. That is huge.

- Making decisions based off of user input.

- The interfaces changes and only tells you what it has to (just in time interface changes - single page apps - SPA's).

- Taking the time, up front, to get the design, flow, and training nailed down.

- You can make things that look good, but eventually, you also need to be able to code it and/or get help coding it.

- Narrowing it (the scope or project) down to the specific needs and requirements of that project.

- Getting a valid sign-off based off of mock-ups and design flow. Russell was saying that if you increase your skills to do quick mock-ups, that helps solve things before you ever go to code. Helping people walk through it. Letting them taste the vision or selling the sizzle. Everybody gives their opinion, signs offs, and everybody is sold on it, even before it really exits. Talking about emotions in marketing.

Switched gears and started working on the content management system that we are working on. Talking about helping others and spreading the love. Helping to teach others, use that as a learning and a growing philosophy.

https://github.com/RussellMoore1987/code-doc - This is the GitHub repo for the content management and documentation template that we are working on. It will end up being the underpinnings of the presentation gallery. That, the gallery, will be the top few layers (visual fluff and key bullet points) and then we will use this content and documentation template as the meat and potatoes for the real screenshots, videos, text, and other content. I'm excited about it. The project will be big, but I also feel like it will help tremendously.

Working with Abby on graphics. See attached for some of her progress.

Working on back-ups of the developer's notebook entries. Lots of formatting and light clean-up of some of the older entries. Bouncing between sites to help with the clean-up process. Somewhat sweeping the floor on some of the older projects and elements of time entries.

Working on the developer's notebook and doing some back-ups. Saving some back-up PDF's of the developer's notebook entries. These may be used for directly feeding things into AI as well. Anyways, saving out some PDF documents with time and notebook entries. As I got into certain months and years, I had to edit quite a few web links. They were too long to allow for the 8.5 x 11 inch PDF format. Changing things in all three of the main sites - Adilas, adilas shop, and adilas university - depending on what needed to be done.

Emails and then meeting with Shannon. Rereading some of the content that we are working on. Shannon was saying that due to AI, some people are lamenting the "loss of effort" by using AI too much. Shannon and I were talking about asking AI to help me summarize certain topics. I have a ton to do. Help break it into chunks. Small not on marketing - it is presenting things in a way that solves their problems (our clients). We also talked about helping AI to catch the vision so that we can share that vision with others. Fun session.

Recording notes from the past few days 3/5/26 to 3/9/26. Recording some expenses.

Phone call with Steve. We were talking about the current load and how much is going on. It's hard to keep up. Steve is feeling pretty overwhelmed. He and the other team members are running the ship while I am off on the side trying to work on plans and investor stuff. It's pretty rough. There is also some underlying tension from a miscommunication and overstep on my part. See EOT # 12731 for some back story.

Here are some of my notes from the meeting with Steve:

- We started out and I read a post-it note full of some things that I think Steve has issues with - my personality traits. See attached, if you want for the post-it note. We are all working hard, but we have different opinions on what will help and where to focus. Similar but also somewhat different directions. Neither one is bad, just different approaches.

- He is busy taking care of business and paying clients. He is trying to only work on funded projects and projects that have ROI (return on investment).

- Trying to fill in the blanks (needs of whatever is needed).

- Steve is shooting for full AI projects - code, planning, fixes, etc. Steve is heavily leaning on AI as the backup or fallback. He is totally going in the AI direction for as much as he can.

- He showed me a small website that a guy built using just AI. Here's the link. I pulled it up. It looks great. It is pretty impressive. It doesn't have any real content, just a shell, but it looks amazing. We talked and chatted about that for a while. There is some fear that some of these guys are going to take over and build what we have built over the last 20+ years. Basically, a question of what is stopping them from taking the next step and building it out on their own? I see it, what we have and offer, as way deeper than that, but there is some worry and unknowns.

- He is seeing or thinking that people don't want any real interface... they just want a simple chat type interface and AI will do everything for them. I was telling him that our full interface and existing pieces need to still be there. There is value there. It is nice to be able to do anything that you want (say an AI chat window), but there are also times and places for a quick and easy button or link. We need both. Our interface is not our real product.

- We talked about how Wayne is working with some AI agents to work on the database and some database updates.

- Steve is feeling a little bit of panic mode. He watches and reads a lot of tech news. Huge changes are happening all around us.

- Only working on funded projects.

- Relying on Craig for all money type decisions (controller level control for funds).

- There is an urgency to what we are doing.

- AI is going so fast, it is scary. He is scared.

- Small talk about IP (intellectual property) and how we can't stop AI. If they want to do something, they can just do it, change it a bit, and run with it.

- He wants me to look into complex binary (tech stuff). He is planning on doing some more research there. Basically, skipping the code and going right to binary level commands.

- Brief talk about how people interact with things. He was saying that people don't want to do any data entry. They just want the AI agent or system to do it. Something like this, I have a document, I upload it, I then have the AI agent enter it into the system. Thanks, all done. AI does it all. As a side note, there may be some automation things that we can do, but don't think that everything will be like that.

- Talking about taking care of the business right in front of us. I don't deny that... and I know that there is a need there. We have been doing that for the past 20+ years. It is also a small trap, in some ways. It keeps us from breaking out of our form or container. We are somewhat maxing out our current model.

- If you read between the lines, he and the team are busy, with paying clients. There is a demand for what we are doing.

- We finished up the meeting, and he was going to go jump into another project that is needed. He is working super hard. He is trying to fill in the gaps as best as he can. I'm super grateful for that.

- After the meeting, I was talking with Heather (my wife). We were talking about an analogy of a malt shop or ice cream shop. Say you have a line out the door, small rush, tables need to be wiped, and dishes need to be done. Everybody is busting their buts, except for one guy in the back who is dreaming of a better way to do it. That doesn't fly very well. Sad to say, I'm that guy. I'm not trying to hurt anybody, and what I am doing is super important, it just gets judged pretty harshly. I fully understand. I have been in there busting my but as well, for years and years. I just know that there is a better way. The story above changes when you say, this small rush has been going on for years and years. We have all been pushing on things. It is not just one night, where things get busy. That longer timeframe makes a big difference.

- Tying this back to adilas (above ice cream shop analogy). We offer custom code. That is awesome and totally part of our model. However, we get so tied up in doing custom code that we can't finish what we really need to. We end up getting stuck in that scenario, kinda like the malt shop. There is a balance. You have to have the money to keep going, and that is super important (work right in front of you). You also need to look to the future as well. I heard a guy say one time, there is a difference between working in your business and working on your business. We need both. It's a fine line and tough balance.

A number of follow-ups and emails. Sent an email to Adi, Adilene Dominquez, about some of the new SWOT stuff that we were uncovering. Also sent an email to Jennifer Murer from Harris Computer about the same SWOT analysis stuff. There is so much more than just SWOT analysis stuff in that document. I can't wait to start harvesting some of the content. Heather, my wife, came in and we went over some stuff as well. Some of it is way too technical for her but we can split it up and make it more consumable - based on audience. Emails and paying bills.

Meeting with Dennis. I told him where we are at as far as readiness and that we should have a decision for him in a week. He wants to help us do some go to market planning and readiness stuff. I really think that it will help. Here are some notes from our quick meeting:

- If I am pitching the idea to Steve, show him the savings and the benefits of what we are planning on doing.

- He was asking, I have to think that something is wrong with the model or the business if you are stuck at a certain revenue amount per year. How can we help you break past that number or value?

- We are a business support service entity - his terminology for what we do.

- At some point, we may really want some outside help and opinions (consulting and ideas).

- Light talks about the contribution margin of each customer, each employee/owner, and each service that we provide. Really looking at the data behind the numbers.

- Sometimes you have to take a step back to see what is really going on.

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

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

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

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

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

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

But what we actually uncovered together was:

The Adilas Story

The One-Page Overview

The Strategic SWOT

The Value Add-On Core Model

The Big Picture Map

The Explanation Ladder

That's basically the foundational narrative of the platform.

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

Changing all of the servers and the time zones. There is a special table that deals with time zone offsets per time zone. This was for daylight savings time.

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

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

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

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

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

Meeting with Hamid. He is going to be building out a new webpage to help with the API homepage. We are going to call it "play at the wall" (PlayAtTheWall.com domain). If you want, here is a small hand drawing of the client/server model that shows the term play at the wall. We are just in the process of doing some planning and gathering information to help him get started. We talked about AI code creation and learning in those processes and environments. We also played around with some screen or text to voice page readers.

Working with Shannon. Talking to Shannon about coding with AI, just a different process. Start general, build functionality, commit and iterate between things, test first - then read code. We also talked about high-level precision bug fixes and changes. Multiple different processes. We briefly looked at the presentation gallery and where we are hoping for things to head. We talked about budgets and how we could blow through $100K in a month, without even blinking. Switched over to working on the content for the other business plans. We worked with ChatGPT on doing a SWOT analysis stuff. We are not yet finished, but making great progress. Super fun session. Here is the link to the chat session.

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

Recording notes for the day. Pushing up some new graphics and concept artwork from Abby.

Working with Abby to get her new graphics up and online for real. See the jellyfish model page in the adilas lite (fracture) plan to see some of the new graphics.

 Meeting with Russell and Abby. Russell is working on building a web app. He was showing us a small demo of his camera photo picture to budgeting app. They are still working on it (he and Chuck). We got off into some general world topics. As an ideal, the world would be awesome if we all just helped each other. That would take quite a bit to get there. Talking about some general sharing and community type concepts.

Switched over to working on the deeper documentation options for the presentation gallery. This will end up being the backend behind the presentation gallery. Imagine the meat and potatoes with tons of documentation, screenshots, step-by-steps, and small context related videos. It should be super cool. Anyways, we started with a small review. We were going over moving from the initial plan, to AI prompts, to AI code building, to small manual changes, to GitHub storage, to making updates and having them be tracked in GitHub. It takes quite a bit. Watching his screen and going back and forth through iterations. We liked certain changes and we didn't like other ones. A little bit of picking and choosing. Watching a series of manual tests (at this level, based on the AI changes). We were getting into deep linking and URL routing for pages and sub sections. When it is all done, it should be really cool!

Working with Abby on her graphics. I took a number of screenshots. See attached. We also started to add in images to the actual page where they will go. We ran out of time and finished that up after our other meeting with Russell.

Various emails, text messages, and phone calls. Touching base with some of the team members. Physically on the phone with Shari O, Bryan, and Alan. Texting others.

Emails and recording notes from the day. Recording expenses. Crazy day.

Talking with Josh. He has a bunch of work and possible deals, they are just waiting and wanting some development done. We talked about using AI to put some finishing touches on some things. We are close. He has a small wish list of items that he wants help on. Things like email campaign stuff, payroll optimized and sped up, custom dashboards, etc. He is really trying to push on things, the only problem is that everything takes time and costs money to build. We can do it, we just need the time and the money. All part of the picture.

I told him that we are scared to just keep building... We have been bitten hard there. We have done that for years. Not that we won't get back to it, we just need to figure out a long-term plan and then do it. We probably have some deep trauma that needs to be dealt with... :)

Meeting with Dennis from the BBOP Center, out of California. Our last meeting was meeting and sharing some brief outlook to help with some business planning. See EOT # 12702 in the shop for details. For our meeting this time, I scribbled down a few notes.

- When describing what we do, Dennis was saying to use the term "Business Support Services".

- We need to really identify our profit zones, traffic zones, and how best to focus our resources.

- He wanted me to think about doing a contribution margin (what do they bring to the table) for each member of Adilas, LLC as well as contribution margins for each service that we offer. What does that picture really look like.

- He was saying that we have to show our value, get some testimonials, and basically promote our bragging rights - we helped so and so do such and such... you get the idea.

- How do you get this product out and help it to scale, keyword scale?

- Talking about doing a business tune-up type approach for working and coaching.

- He was going over some red flags and things that he sees that could be improved. Some of them were tightening up our business model, limit the team down, pulling back from offering so many services and things, and other things. This was just his opinion, looking in from the outside. Not that these things are bad, they could just use some refinement.

Talking with Alan about projects and AI use cases. We spent some time talking and going over things. We showed each other some of what we are doing. Alan is working on multi-threaded stuff for merchant processing different gateways. I have been working on some pricing structures for the main adilas website.

Jumped on the meeting with Shannon. Only had time for just a quick hello and how are you doing. I got a phone call from Steve. I told Shannon that we would need to reschedule. Then working with the banks to reverse a draw on the line of credit. Multiple phone calls, emails, etc.

Checking on subscriptions and other software tools. Checking on the GoToMeeting account (online meetings). Also checking on the newest version on TechSmith Snagit (screen capture tools). Going through tons emails. Checking on antivirus stuff.  A bunch of odds and ends. Recording some deposits and expenses for some funding from a line of credit. Lots of little things today.

Phone call, texts, emails, and signing up for a line of credit with a company. We already have one (a line of credit), but this was a better deal. Small switch-a-roo on some light funding.

/////
Some new notes added on 3/10/26 - the rest of the story...

Small back story. I got an email from a business funding company (cold email, no prior connection). This was early to mid-February of 2026. I was actively looking for some business funding and investor type deals. I replied that we weren't interested in any loans, but we were looking to do a capital raise. I sent him a link to the investment options for adilas. The guy got back to me, we chatted, he said that he had a supervisor that dealt with investment type stuff. Anyways, the guy ended up giving me a number of leads of either banks and/or investor type people. We went through a number of possible options. Pretty good leads.

At one point, I texted the guy and asked him if he would ever work on commission to help sell adilas or get a commission if he helped with a capital raise. He replied back that he was on salary but thanks for the offer. We aren't buddies, but he was actively pushing on things. Cheers to him. I was impressed.

It's now Friday, 2/27/26. Multiple weeks have gone by, dealing with the guy and some of his leads. I have them all documented in the developer's notebook. There were some loan options, line of credit options, etc.

On Fridays, I am normally up at the local ski resort. I'm a snowboard instructor and have been since 1995 (long time). I go up every Friday. Anyways, I taught a 2-hour private lesson, made a number of runs on my own, and stopped for lunch. I decided that I had a ton to do back home, so I took off early to head back to town. When I got back into cell service, I saw a text from this guy. Super simple, give me a call when you can. I then gave him a call. He had another lead for me. Nothing new, similar to what he had already done. The guy said that he could beat our current line of credit. He then asked if I was interested? I said yes, I was interested in seeing what he could do and how they could beat the current rates. The goal was just to see what he had to offer.

Back a couple of weeks ago, I had to provide them some bank statements to meet with one of the guys. That is pretty common, no big deal. That's how the banks see what you can qualify for. At that point, they were trying to see what we would qualify if we got a loan. I had looked up the company, and it was totally legit. Anyways, I get connected with this other guy, some sort of an admin/supervisor who worked with this other guy. They were calling and texting me and seeing I was interested in using them, instead of our existing line of credit. Our other line of credit had a huge interest rate, so I was interested in checking it out.

All of the sudden, if felt like that, they were offering me a line of credit, and I could get it today (start the draw and funds would hit our bank in a couple of day). I think that they were trying to close some things before the end of the month (fill out some sales goals - last Friday in Feb). I just had to do a pull or a draw on the line in order to set it up. I had enough time, in between other things that I was doing, to look up what else we owed and how we might be able to use this small advance on the line of credit to wipe out other debt (debt consolidation) and even get some to help moving forward (lube the wheel). That was the goal. This could work out slick.

My bad, I did not communicate with Steve or anybody else on the team. I signed on the deal and requested a draw on the line. This whole thing, just sort of fell into my lap. It seemed like a great deal, I was looking for something like this, I had already had numerous interactions with this guy, and it felt good. It was just my name on the line of credit, and I really thought that it could help. So, I did it.

Fast forward to Monday, 3/2/26. I sent a text to both Steve and Craig that a large amount may be showing up in the bank and that I would get them some more information. By end of day on Monday, the amount had showed up in the bank. I then wrote an email to both Steve and Craig Monday night about what it was for and my plans. The email went out late on Monday night. Once again, my fault, and no or minimum communication. By early Tuesday morning, excuse my language, but all hell had broken lose. Emails were sent, texts were sent, and a cussing and screaming phone call had taken place by around 10 am on Tuesday morning.

On the banking and funding side of things, we had to stop things, back things out, and do a lot of phone calling and talking with banks and the financial institution that had given us the line of credit. It turned into a crazy mess. It got really ugly.

It is now just over a week later, and things are kinda calming down. My bad, I overstepped my bounds. It caused a ton of stress, bad feelings, pressure, cause and effect decisions, etc. I did not communicate. I know that. I was honestly trying to help.

Multiple sessions working with ChatGPT on adilas pricing structures and such. Getting help with prices, plans, add-on's, and other options. Shannon and I started the session earlier this morning. I then did multiple other sessions throughout the evening to finish up. We had left out activations, setups, 3rd party solutions, and other industry specific stuff. We also added in some notes to help us account for upcoming changes to the adilas value add-on core model, adilas marketplace, and the adilas cafe. All part of the new future and where we are headed.

Steve challenged me to work with ChatGPT to actually build out small samples and pages. We went through three different versions. Once we finished, I sent an email out to Chuck (designer) with the temp files and instructions. ChatGPT was very helpful. Recording some notes from the day.

Here is the full chat link of our session - 5-6 hours in total - https://chatgpt.com/share/69a0a070-3778-8007-a998-ebf29c864809

Working with Bryan. He had some questions and such. He is working with some accountants on some things. He would like to create a QuickBooks alternative for users and accountants. Help them easily switch over to adilas. He had some plans mocked up and is lightly working on some ideas and options.

We then looked at some other questions that he had. Towards the end, we talked about other full-service options to help people do all of the backend stuff, using our system and helping them run and do what they do. Imagine something like they have an adilas account, but they use some other mini app (scaled down) and it helps them push data into adilas without using the main adilas user interface. Adilas would then just become the storage engine, in a way. It still exists, but it would be used and consumed differently. Skipping the main user interface (UI) and helping with custom data input and then providing custom output reports. So many options. I told Bryan to keep catching the ideas, even if we can't fully build them out right now. We need to keep catching the ideas and plans.

Meeting with Joe from Nassau Street Partners. Pretty quick meeting today. We chatted for a bit and then I gave a small counter proposal, and they said no thank you. Joe was very kind and explained how they can't change any of their structure and how that affects their investors and expectations. No harm done, next.

Phone call with Alan, touching base. Talking about payment gateways and future plans and changes. His daughter is doing better. She is still in the hospital but doing better.

Working with Shannon. We looked around at what is happening and then jumped into some of the stuff. Lots of moving pieces, all over. I explained what I did with Abby yesterday and we looked at some graphics. We then jumped in and talked about what we did with Russell and how we used AI to help build out a basic teaching and documentation project. Supper cool. I didn't have anything really to show, so I drew what it did. I will get files from Russell later on.

We talked about what else we have in front of us, project wise, and where we need to focus. We then spent the rest of the session going over pricing stuff with ChatGPT. Super fun session and we really tried to give it some good information and ideas. Here is what we came up with.

https://chatgpt.com/share/69a0a070-3778-8007-a998-ebf29c864809 - ChatGPT chat link on adilas pricing structure (prices).

Sending Wayne some information on adilas percentages. Emails and follow-ups. Recording notes from the day. Also pushed up a number of images from Abby that I got in an earlier meeting.

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

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

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

Working with Abby on her graphics projects. I took a bunch of screenshots. See attached. Great little session.

Meeting with Wayne Andersen. He's our main server guy. Going over logs, session values, query of queries, server loads, going over his papertrail logs, alerts, etc. Talking RAM memory, servers, timeouts, and ways to searching things super quick. We also briefly talked about adilas percentages. He is doing a great job!

Meeting with Greg from Calder. Talking about the benefits of doing a business valuation using Calder and their team. He is going to send me over some stuff. We spent some time talking about education and other things that help along the way.

Meeting with a business funding banker from Canada. We chatted and talked about options. They would like to help us fund things, but they want to do it through direct loans and debt financing. This is our least favorite type of funding. Anyways, he is going to send me some information, and we may reach out to him if we can't find other options or solutions.

Emails and follow-ups.

I got this back from a guy, I thought that it was pretty good. Talking about adilas.biz or Adilas, LLC:

The all-in-one ERP positioning, combined with 60% margins and two decades of product evolution, places you in a differentiated bracket, particularly given the absence of institutional capital to date.

Given your profitability, product depth, and clear commercialization inflection point, I see alignment with patient capital groups that prioritize durable cash-flow businesses over short-cycle venture exits. The key here will be structuring this opportunity to emphasize capital efficiency, vertical expansion through Fracture, and AI-readiness as a modular advantage. 

Emails and recording notes. Added the video link between Brandon and Russell, discussion on the white label investment options to the adilas investment opportunities page. It is kinda raw, but covers some great questions and answers. Here's the history, on 2/11/26 Russell and I met to go over some training. We recorded the video on that day (eot # 12683). Then on 2/23/26, yesterday, I reviewed the video (eot # 12718) and made a few more notes. I asked Russell and he said that I could share it. I thought that it had some good content in it.

Quick Microsoft Teams meeting with Chantz from NewtekOne. Talking about some business financing and possibly getting some working capital to help with a bigger capital raise or capital round. We were talking about percentages, requirements, etc. Just for my notes, I got an email from Isaac Scheffler with top lending USA - I then got referred to Alek Sierra from ECP Business Capital and then ended up talking to Chantz from NewtekOne. Kinda round about, but maybe part of the game.

Working with Shannon. We started out by reading over an email from Wayne (backend server technician for adilas). He is proposing some tech changes and code restructure stuff. Pretty in-depth changes and plans. It all plays into our adilas lite and fracture plans. I really want to help and support him in his decisions. We spent the whole time going over his plans and documents. If Shannon didn't understand something, I would draw or explain what I could. The plan had priorities, phases, cautions, and even pages that needed attention, based off of usage and page stats from one of the servers over a 3-day period. That doesn't show the whole story, but it give us a good idea. Pretty cool!

Reviewing a video from a meeting with Brandon and Russell, from a couple of weeks ago. As a note, Russell is my brother (younger), but we have worked for years together on training and projects. Russell sent me the video, but I was too busy to go back over it. The goal was to get some of the Russell's questions, from the video, and then address those questions in order to be more prepared for future talks and chats with investors. This video was originally part of a practice session about pitching the white label investment option for adilas. See element of time # 12683 for the original notes.

Here are my notes after rewatching the video.

- Question from Russell - what am I going to get for my investment of X? I don't care about owning it, I just want to make sure that I get the tool that I need, in order to sell it.

- What about future availability and being able to change or fix things in the future?

- What's a good flow so that I can sell it to my customers? I am willing to play for that. I don't need it perfect, but I do need to know that it can do what I need it to do.

- Possible matching funds - say something like $10K them and $10K us

- Salesman like to promise things (known fact)

- White label skins are part of the master plan

- Part of the plan is helping them, our clients, see that it is up to them to pitch and sell this thing (what we create). We help with the plans, the backend tech, and getting you a product that you can sell.

- People want us to build, build, build - our plan is not to do that, meaning for free. We don't mind building and building, but we can't do that just based off of promises.

- We already have 75%-90% already done. We help you get what you want and then you go from there.

- It goes back to that plan and what can we do? - Sell me on it

- Read over the document to get the idea of the rules and how things will play out (link to the investment options pdf).

- How are we going to find these partners, entrepreneurs, and angel type investors? - Work with other entities

- Russell went back to his "flow" stuff. That was really important to him. If he can get that working, he is good with everything else. After the flow is set, then we talk pricing.

- Figuring out a benchmark (features and pricing) and having whatever is needed for the industry. Then making sure that he has all of that plus other important stuff. He was talking about reselling the services on a mark-up. - Making your own package, and then selling that package, etc. - Wholesale costing.

- Make sure that you can find those people - If they can sell it, get the flow down, and make it really rock, then game on - It has to look good, function well, takes care of my customers, or I can slide it under (meaning price it better than my competitors), then I will invest. I need to feel secure that I can make this work.

- Get into some of these investor groups and see what they say - Making the pitch and then getting some feedback - Ask them to put me through the ringer of education - I want to know what investors are looking for - Get involved with people in those sectors.

- Russell said that he is more interested in white labeling vs straight investments.

- Talking about levels of control - control of the company vs harnessing what we already have - often, buying in means I want to take control - There is a difference between normal investing vs white labeling.

- Russell wanted to make sure that his stuff is protected

- Audience - Bringing code and visuals to the audience

- Planning and coding - Plan well and hit the mark - Projects need to be 80% planning and 20% coding - We plan and then make exactly what we are shooting for.

Meeting with Joe from NASSAU Street Partners out of New York. Small chat and light introductions. We talked about a potential commercialization round of funding. Basically, getting the product more fully out to market. He is going to request some information and then we will go from there. After our call, I spent some time just doing some other emails.

Phone call with a business consultant out of California. We chatted for about half an hour. He just wanted to get some information about me and our business. After the meeting, I sent him a text with some info, contact stuff, and a small elevator pitch of what we do. It was similar to the other elevator pitches that I have made but I reversed the order and added a little bit to it. Here is what I wrote him:

We offer all kinds of operational business tools. We also help companies with the accounting side of the puzzle, if they choose. We are web-based and do all kinds of services that support our platform. Our clients can get started using our system within 24 hours. If they need changes or custom solutions, we can do that as well. Very diverse.

Here are my other notes from our conversation.

- Get your go to market strategy setup up first.

- Figure out your 30-day execution plan or playbook.

- Make sure that your packaging is ready to go (the business plan and/or pitch deck - for whomever the audience is)

- Do some simple process mapping. Where do things start, where does it go from there, where will it end up? That is kinda like a roadmap for your clients to know what to expect and/or plan for.

- Look at what needs to be automated and how can you gain from efficiency changes?

- What role does AI play in your rollout? Look for ways to help with creating improvements.

Light prep for the day and some of the meetings. Pulling up websites and looking around a bit. First one (meeting) was a no show. I jumped on the zoom meeting but never got let in. I messaged the guy, but it didn't happen. We are looking at possible other dates to reconnect. Doing emails and other small things while I waited.

Emails and checking in with Hamid via text. We pushed our meeting to next week. Signed up for the Adobe ColdFusion conference in June. Recording notes for the day.

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

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

Quick phone call with Alan to touch base. He is helping with his daughter (newborn) and doing some hospital stuff. She got sick and has to be in the hospital for three weeks. We quickly chatted about our projects and where we are headed. I'm going to call him again next week.

Emails and follow-ups. Cleaning my desk and work area a little bit. Getting organized. Adding a pointer cursor to some buttons in the API section. Backing up files from laptop to an external hard drive. While waiting for files to copy over, looking over some template pages in the-project (CSS theme that we used for snow owl inside of adilas). Tons of emails as I was doing other clean-up stuff. I have a bunch of appointments for Monday and Tuesday of next week.

Emails, follow-ups, and booking some time with a business consultant out of California. Recording notes and pushing up images from earlier work sessions today.