Emails and reviewing notes from the past three months (11/1/25 to 2/2/26). It has been a world wind... here we go! Reading through entries, day by day, starting in November of 2025, and then rolling into the other months. This was over 4 hours of reviewing the plan. So many ideas, suggestions, needs, wants, guidance, and direction. Keep chipping away at it... Start there!

Emails and requesting a few main website changes from Chuck. I wanted a few new link options from the main header, under the adilas world menu option. I wanted to add the presentation gallery, fracture - adilas lite plans, investment opportunities, and a link to the adilas API. Quick phone call with Bryan. He found a couple of pages that needed some CSS updates. Small quick code changes on the classic cart. Working on the form field CSS stuff for the classic cart. Ended up going through each of the cart options to help with look and feel. Pushed up the new changes.

Missed this call. I was thinking my time zone, and the meeting was listed in eastern time. I'm in mountain time. I missed it. Sent them an email. We will reschedule.

Recording notes from the day.

Working with Hamid. We started out and Hamid was talking about quality over quantity. Sometimes we get stuck in different cycles. I told him about some of the switches that we are making internally. We ended up talking about the adilas API sockets and helping to make that section (web pages and external tools) look more up to date, usable, and ready for new outside users and developers. I was explaining a lot of things and going over concepts and flow for the API's. I did a lot of drawing and used a number of existing pieces to show what goes where and how things look. He is going to start working on a new website for the API socket area. We are going to call it the "play at the wall" website (see this graphic for the play at the wall section). It will help with information about the adilas API sockets and endpoints, help files, samples, documentation, visual tools, and other API related stuff. Good meeting.

More planning, thinking, and refining ideas. My mind has been racing. Just trying to record a bunch of the thoughts and ideas. Even if I can't finish everything, I'm hoping to at least get the thoughts down in writing. That feels like part of my mission.

Meeting with Alan. I was showing him some of the changes and where I am heading (notes from the past few weeks). He then showed me some of what he is working on. He has been playing with continuous development pipelines and playing with other more modern frameworks and such. Sharpening his skills and showing what he can do. He showed me a quick demo. He's been working on a small app in some other languages and frameworks. We also chatted about what the future might hold and where things are going. Good conversation.

Lunch meeting with Bryan. Talking about goals, direction, and what we are seeing. Some of our conversations were talking about our team, the next vertical, and what are our plans to get there. Where do we want to be in a month, two months, a year, etc.? Great conversations. I gathered that Bryan has been out selling this thing (adilas software) for the past couple of years here and there. Not fulltime, but he has been hitting the streets. He has some good information and things that I could glean from his experience.

As a side note, what if our next business vertical is selling our kick butt business engines to entrepreneurs or outside parties and helping them skin it and market it. That is right in line with our value add-on core model. Let's do that. We have a generic business tool, on purpose. Now let's start putting the industry specific skins on it. Build out the API, build out the ways to do the custom skins, etc. Go in that direction. Keep finishing up the MVP (minimal viable product) for a full-on business engine. Go sell the engine.

As a follow up - as I was driving home, I had a few thoughts. I sent Bryan a text saying that our next business vertical could be selling our business engine to other parties. He wrote back and asked, who would be our competitors? What language would they write it in? Are you thinking open source or something different? Great questions. I wrote back and said... I'm not sure. On the language question, if we build it, we will code it, using the languages that we use, and then put it on our servers. If they used an API, they could host it and use any language that they want. Some good questions, we might want to look into this a little bit deeper. Fun lunch meeting and fun to think about ideas and options.

Working with Shannon. We reread time id # 12645. Tons of talking, side tangents, drawing, using calculators, and trying to refine things. Working on the overall picture. Where are we headed and what are the rules that we want to setup to get there.

Watching a video on the QuickBooks Enterprise Suite. I haven't looked at QuickBooks very much. This was a client request for us to look and see what they are doing. I watched the video and then sent an email out with a few observations. I thought that it was interesting. Nothing that we can't or don't do, just a different style. Some of it just comes down to who is funding what and what are the needs. Good stuff.

I know that I am bias... but I'll stick with adilas!

Light review of some leads and contacts. Looking at and reading their websites. Recording notes from yesterday.

Meeting with Russell and Abby. Lightly going over some existing graphics and flyers. I was showing them where we are heading (mixing some of the old adilas flyers as part of a 3-way pitch). We then turned into practice mode. We picked a website and then started to do a mock-up on that website. Working on layout and design stuff. Talking about what we like and how to start using the mock-up. Russell was grabbing images from online, cleaning them up, and then having ChatGPT to make things similar. Most of the session was a practice session. It was fun.

Emails and light follow-up.

Recording notes from yesterday and today. Things change so quickly. It's hard to keep up. Pushed up some videos for the adilas lite plan showing the interview with Brandon, back in 2013 at Bridgerland. If you go to that page, go to the section labeled interview to see the video links.

Back working on Cory's little deposit status tool. Also made some small CSS fixes to force a minimum size for text fields. We had some users that were squishing the screen sizes down so low you couldn't read anything. Now, most of the form fields have a minimum size and it won't go below that. Changed quite a few files. Pushed up new code.

Quick phone call with Bryan. He has a kid's group that just needs a super small kid friendly interface for simple POS (point of sale) functionality. They are a potential client. We talked about tracking things by location (booths or tables or what they call themselves, if they have a brand or store name) or by person (kid's name). Super simple. Just add an item and have it flow into an invoice. Maybe allow for discounts, if they want, but nothing fancy. No inventory tracking (using unlimited items) and be able to take cash and cards (checkout options). Easy setup interface and then populate the store and quick buttons based on what they setup in their mini store. Be able to give them some simple reports. Super simple stuff. Great ideas.

Small fixes for Shari O. on some payroll forms. Looked around, sent off a text to Shari O. I might need her help. The fix deals with an alignment issue and I don't have the originals. She wants me to move some of the form fields around for perfect printing but I'm not sure how much to move them.

Started working on a small piece for Cory. She needs a special bulk deposit status clean-up tool.

Work session with Shannon. Going over tons of notes from last week. That was fun and insightful. We reread a bunch of the elements of time (entries) from 1/19/26 to 1/24/26. As we were reading the entries, we made a few small fixes and added some more information. Just trying to refine things. Lots of moving pieces, daily. It's crazy how fast things can change.

We talked about some new concepts and topics. Shannon was talking about "lean" and "just in time" options. Everything seems like it is getting into super scaled down versions. We know that many of the adilas users would love something like that. We are trying to get there. It feels like we have to break it down into a few smaller pieces, so that it can dynamically conform to what we want it to be. In English, we have to make it more technical in the background (splitting or fracturing into smaller pieces) to make the interface seem simpler. Everything needs to be configurable (permissions, settings, and templates).

Some other topics were simple step-by-steps, easy SOP's (standard operating procedures), and quick focused training. Another topic was helping people to participate in something great. If they want to buy in, they have to feel like it is something of worth and something great. Shannon and I were talking about showing them, any interested party, what we have and how and why things work. We talked about setting up a time to be available, once a week, for questions, demos, and touching base. Leaning towards one night a week, over the GoToMeeting session (reoccurring meeting).

As a note, we left off, reading through element of time # 12645 - we only got halfway through it.

Paying bills. Then reviewing a number of small videos from the Bridgerland (BATC or BTech) interview back from 2013. These are videos 3 and 4 of a 4-part series. The audio is fine and we cover parts of the system. Some of the video quality is not the best. They were recording the laptop monitor as I was doing a live demo. Anyways, it still gets the main point across, just a little fuzzy on the screen display.

BATC_video_3.mpg - Video 3 - almost 10 minutes long - going over a quick cart and invoice functionality

BATC_video_4.mpg - Video 4 - 19 minutes long - live demo continued - bouncing around to different sections - writing checks, printing barcodes, etc.

Jumped on the GoToMeeting session with Steve. We went over his email that he sent out to all of the guys. Kind of a pivot type email. We talked about different options and where things are going. I then spent some time pitching him on where we are going and what things are looking like. I was doing lots of drawings, talking, and explaining. We went over ideas and options. Towards the end, he was giving me some advice and what not. We talked about capital gains taxes and things to think about on legal stuff (selling percentages of adilas). I am very grateful for his advice and thoughts. Here we go, new chapter.

As part of this new chapter, I will be putting the next two months (hourly wages) on the adilas ship B side (fracture and adilas lite - recorded in the adilas shop) side of the puzzle. Adilas (normal adilas or ship A) owes me some monies. I will be drawing on that as I do a 2 month push to help get some sales and funding. I will not be adding in any new bills (hourly invoices) to the main adilas system during this upcoming 2 months. I'm planning on a 3-way pitch. We will show an introduction (who and what are we), our current offerings (where we are at and what is available right now - sales), and plans for a future buildout (investments). We are going to see where it goes!

Reviewing the first two (2 of 4) videos from the Bridgerland Technical College (BATC or BTech) from back in 2013. This was an interview about adilas and what are story is about. The first two videos are about 10 minutes a piece. Good audio and the videos were mostly of myself (Brandon) talking about adilas and some of the journey.

BATC_video_1.mpg - Video 1 about 11 minutes

BATC_video_2.mpg - Video 2 about 9 minutes

Small meeting with two guys from Crewe Capital. I met with a Nick and Jesse from Crewe. Pretty big firm. I was kind of a small fish for them. They said that most of their clients like to write 25 million dollar checks and higher (bigger fish). They listened to what I was saying and gave me some good ideas. They thought that a good corporate attorney (corporate counsel) would be a good place to start. Help protect yourself and get in with people who are dealing with that type of stuff all of the time. They said that the kind of money that we are looking for may come from venture capital (VC guys) and smaller family offices. They said that they would send me an email with some names and contacts for people here in the mountain west area.

I had a few fun ideas over the weekend. These are mostly dealing with a transition to pitch and sell what we have. Often, I keep looking forward to this view of the future where certain things fall into place. I hope that I'm right, but I think that I need to roll with what we have, right now, and then see if that can help us get to that future vision. I tend to prep and prep and prep and maybe even some more prep... Part of my personality. I want it to be nice, awesome, and tight. For now, we may have to roll with it a little bit, vs trying to cross every T and dot every I. Here we go... :)

Here are some of my notes - these are from 1/25/26 and 1/26/26:

- Be honest about what we are doing. Tell it like it is vs just paining the picture of the future. We have come a long way.

- Be our style - emphasis on "our" style

- Think audience - small to medium - for clients, investors, and entrepreneurs

- List out the investment options - show the whole gamut (scope). Think all of the business functions, sub parts of the adilas lite (fracture) plan, and the known areas for investment opportunities. Say someone was interested in education, AI integrations, POS (point of sale) functionality, CRM, CMS, ERP, ecommerce, scheduling, custom code, industry specific skins, marketing, sales, etc. List them all out.

- Point them (interested people) to the web for more details.

- Explain the push window (date range for trying to raise capital).

- Ask them to share with friends, family, and known acquaintances - we are looking for those beginners and lower intermediate investors.

- If they join in, become part of the family, we could give them view only access into the adilas backend. Make sure that they can see what they want to, but also keep and make it safe.

- Big fish vs smaller fish - we want to keep some of our culture.

- Light history about where we came from and what we have been doing.

- Small stats on what we are doing right now... monthly reoccurring revenue, accounts receivable (A/R's), team size, accounts payable (A/P's), etc. Let them see the picture.

- Why the push... explain the why

- What is our culture - explain a little bit about our culture

- What are the goals and vision

- Grassroots and community oriented

- Introduce yourself - this has been my career for the past 20+ years - what do you love and why

- Trying to build a community where others can share and participate

- For me, on the community funded projects - open it up more - clean it up - flag and tag projects to certain key categories - maybe even reopen the actual donation and payment options. We had shut that off due to security and hackers. We could spend some time and tighten that up. That would be fun.

- Reread my church notebook from 1/25/26. I took some good notes and there were some good talks and discussions.

- One of the songs we sang today was hymn 237 - "Do What Is Right". I like that song and it hit a little bit different today. If you aren't sure what to do, do what is right and let the consequences follow. Great message.

- I saw a cool flyer at church today. It was well designed. I was looking at it and trying to get some ideas (layouts and designs). Maybe a fun side with some good whitespace, a nice design, and a simple message. Then the other side could have more information.

- This was huge for me... use existing pieces and artwork - graphics from the teaching gallery, main website, and the presentation gallery - tie it all together.

- If I were holding someone's hand (virtually)... what would I say or tell them? Go in that direction.

- Building a house - analogy - you prep, you plan, you build the outside (earlier versions), and then you work on the inside and do finish work. That is basically what we are doing with the adilas.biz project.

- 3-part pitch deck - introduction, current offerings, and future plans and future buildout

New notes from 1/26/26

- See the text message that I sent to myself. My dad and I were grabbing a breakfast burrito. He was rattling off a bunch of names and possible contacts. That will be a great start.

- Post the BATC interview videos - maybe some other ones as well - just a thought - link to Google Drive adilas videos

- On a call earlier this morning... I mentioned that the adilas part or the software that we were building was the only thing that survived the downturn (recession) in 2008/09 from the old Morning Start Automotive, Inc. business (used car and trailer dealership that Steve owned).

- I reread some notes from yesterday... I liked these ones... people - the plan is people, the purpose is people - and bringing people to Christ and helping people to the next step

- On profitability - we are saying 40% cost, the rest (other 60%) is currently being dumped into development and R&D

Quick phone call with Andy Garza from Calder. I was thinking that we were meeting at 12:30 pm, so he had to call me. Oops. Anyways, he had some quick questions, and we chatted for a few minutes. He said that he would contact his client and get back with me. I had responded to an email about a client looking for a possible ERP solution.

Recording notes from 1/20/26 to 1/24/26. Also added some graphics to the EOT # 12624. Some new concept artwork from Abby Elkins (my daughter - used to be Abby Moore).

I got up and started doing some planning and brainstorming. I was just planning on doing a little bit and the ideas kept coming, so I wrote them down. Here is what I got.

- Do some 1-pagers (one-pagers). Maybe even 4 or 5 of them. Quick reference stuff that could be used alone or used together as part of a group. This could be for sales, intros, quick guides, showing pieces. Make them all simple 1-pagers.

- Include the elevator pitch on one of the 1-pagers

- Show correct web links on the flyers or 1-pagers

- Link to the plan - fracture or adilas lite

- Old adilas GPS core image

- Old adilas formula flyer

- Old adilas map or interactive map flyer

- Maybe update some of those older one-page flyers

- Link to the presentation gallery

- Talk about ways to invest - 1/10th of a percent, 1% (full percent), 10% - show some levels and options

- 75% of the company (adilas, llc - adilas.biz) is available for purchase

- We are doing a capital raise - Looking for 2 million to 10 million for a new buildout

- Setup some small rules - this would be for investments and raising capital for the new buildout. Straight prices, don't worry about taxes (basically with tax included). Simple 1-pager, you get x percentage for y dollars. Super simple and cut and dry. No promises of future value. Basically, if you buy in, you then own part of the company. In the case that it sells, you would gain from that sale. There are differences between buying a percentage and active funding of projects. Maybe make small 1-pagers per section with some super simple rules. Add links to the web site for investment options.

- Talk about options for commissions - 10-20% - leaning towards 20%

- White labeling - minimal starting investment of $100K - buy in at a percentage (could be small), then do a plan and figure out the scope. Detail things out. Then figure out the plan from there and how complex the new white label is going to be. The initial $100K pays for the kick butt engine and the detailed scope and development plan. The rest will be determined from that point. The goal with the white labeling is geared towards future revenue and rolling things out in scale (future reoccurring revenue from multiple clients or business verticals). White labeling is an investment and plan for the future. If the project feels like less than $100K, we may push you in the direction of custom code vs actual white label.

- Dealing with white labeling - This is something that gets built on top of the adilas engine, ideally built by our team for a 3rd party vendor, that 3rd party vendor would then run the marketing, billing, tech support, etc. for their clients. We would most likely host their white label on our servers, and let it ride on top of what we have. It could even limit access to the underlying pieces. If someone wants to host it themselves, code it themselves, and just use API's (backend connection sockets and such), that is different. That would be a 3rd party solution and would go through the adilas marketplace.

- Talking about scope, timelines, feature creep, and change orders. If the plan changes, in any way, we need to be able to adjust (change orders). That could affect scopes, timelines, deliverables, budgets, milestones, etc.

- For me, think about the trystorming type approach with a known need to circle back around and refine things

- Contact info on the 1-pagers and in the packet(s)

- Old graphics about ecommerce, system players, choose your skin, show your stuff, etc. See image.

- Ideas - You could go around with some flyers and do some seeding...

- Get people to go door to door in neighborhoods and/or in business districts

- Promotion codes and lead tracking - tie back to commissions and affiliate programs

- Social media influencers and people who push products - sometimes people trust these guys/gals/people

- We start with the main adilas MMLLC (multi-member LLC) - then we open it up into the other MMLLC's - adilas.biz, adilas shop, adilas university, adilas marketplace, adilas cafe, and maybe adilas funding or adilas management - there could be others - adilas employment, adilas staffing, etc. Along with that, allow for investment options of 1/10th %, full percentages, and bigger percentages (say 5 to 10% and above).

- When ready... maybe a small glossy folder with a few key 1-pagers in it - small packet

- We need to do some market research on the pricing. This will help us be more confident in our pricing. We have to follow the market value. There is an optimal range.

- Most credit card processing fees are around 2.5% of your credit card sales per month. We are pricing adilas around 5% of your total sales (cash and card) per month. Also remember, most companies are doing the mash-up option and paying for multiple systems to make up the whole. Paying 5% for one integrated system, is great!

- Small samples on pricing... Basically, take a monthly sales number and times it by 5% or 0.05. Samples for some starting numbers: Monthly sales from $0-$400 x 0.05 = $20 (smallest monthly fee). Then show values for $1K, $5K, $10K, $20K, $40K, $60K, and $100K - using the same formula. Make a note about multiple locations. Simple math. If one or more of the locations are at a different size (sales volume), no problem. We can set those values. Once a monthly is set, we can hold that number for six months, and then we may review it if needed.

- In sales, if there are custom needs, we are willing to talk and chat about quantity discounts, franchises, seasonal usage, clients not using the sales features but using other parts of the system, etc. We can provide special quotes and structure deals. We can't go lower than 2.5%.

- $1,500 starter package - list it out - setup, turning things on, and up to 15 hours of training. Monthly fees are separate. This is just the starter package. If you don't need the training hours, it is $500 for a one-time setup. You have to have a prior system to just do the new setup fee as a standalone.

- Get the flyers done professionally - make them nice

- Use a temp service to help get the word out - get them the information and/or packets and let them manage it

- At some point, we will need an internal training meeting for our team members

- Make some new page (web link) redirects - some of the files and places have longer web addresses - make a number of smaller redirects - folders and path stuff - links like the adilas lite or fracture plan, investment opportunities, and the presentation gallery.

- Fix the adilas pricing page - show some other options - line it out a bit. It is pretty simple right now.

- Help work with Bryan on his sales channels - Finetech (merchant processing) and Host Huskie (web hosting). We could do similar things over and over again as needed.

- The existing software package (adilas.biz) can handle 75-90% of any business - out of the box.

- Just a thought - what if I put all of this into AI to see what I get - that would be cool. Maybe wrap it all up together.

- Get out of the way!

Meeting with Hamid. We did some work on the number fields (existing form fields) and allowing decimals vs just whole numbers. We went over some code commits and how the code repository worked and such. Small bug fix while doing some teaching and learning session with Hamid. Two birds, one stone. Good session.

Meeting with Cory. Going over some questions on vendor credits (special accounts). Talking about the balance sheet and how those vendor credits are tracked. She then had a small list of things that need to be changed. Light tech support stuff. She also requested a couple of code changes to some pages and new custom tools to help make her job easier.

Quick GoToMeeting session with Alan. Trying to figure out plans and where we are going. Talking about sales and different companies. We both reported on some things that we are working on. Also, what is in the near future - projects and features. Quick touch base.

Phone call with Bryan. I was driving home from meeting with Gene and got a call from Bryan. I'm really proud of him. He is chasing the dream and really trying to find a way to tap into existing sales funnels and lead generation sources. He is trying to work with Finetech (merchant processing company) and also Host Huskie (website and web hosting company). They both have needs and clients that are looking for software solutions. Trying to get a good sales engine going and functioning. Our goal is to work together to finish up some industry specific skins and get them out there. I really like his direction. I told him that I would help him where possible.

I went out to Gene's house. He gave me a sweet tour. Fun place. We then talked shop and options. He was very helpful and helped me see what we are trying to offer. Gene loves motor sports (motorcycles, snowmobiles, etc.). We talked about the fact that adilas.biz has built an awesome software engine. Okay, now, how you market that? How can we get other developers and entrepreneurs to see that advantage of using the kick butt adilas engine?

We talked about levels of risk and taking calculated risks. He was also recommending that I basically "find my seat on the bus" and then stay there (in the correct seat). I tend to bounce around. I believe that he was quoting from a book called "Good To Great". We all need to stay in our lanes... :)

Great meeting. I really appreciate his time. He is going to reach out to some of his contact and make some introductions.

Working with Russell and Abby on mock-ups and layouts. Russell gave us an assignment and then we spent the rest of the period working on the design. Working on mock-ups. See attached.

After Russell left, I worked with Abby and doing some critiques on some images that she is working on. See attached for some of the current concept artwork.

Yesterday we met with Steve, see element of time # 12620 for details. Today we were working on where can we go and what can we do. I was showing Shannon some options for outside control of the funding. Lots of drawing and showing flow and possible flow and control. Here are some of our other notes.

- From yesterday's chat, Shannon was talking about Steve not wanting to declare bankruptcy (closing things down) and me not wanting to go back to being alone. Both of us were trying to protect ourselves from super painful past experiences. Very interesting.

- Current ROI vs future ROI. We actually need both.

- Lots of talk about repeating patterns

- Avoiding pain, this seems to be a trend and natural reaction.

- Shannon and I reread over some notes from a business consultant meeting from back in the end of 2019. We called it "our rejecting of things" discussion (EOT # 5295).

- Our people are wanting more structure - see this PDF for an internal adilas survey.

- Helping to frame the pitch to build on top of an existing engine vs building something from the ground up - riding on top of our existing software and team - white labeling a custom skin on top of what we have... fund that... you could get a fully funded and finished system so much quicker - tapping into existing infrastructure.

- Play the game with the massive tools that we have... quick add-ons

- We really enjoyed rereading that full element of time from the business consultant (see link for # 5295).

- What makes a mom-and-pop shop... vs a bigger business? It is mostly about what they choose to do.

- We then flipped over to the element of time # 5296 - this one was a few days later from the previous one. Another business consulting meeting.

- We may need some interplay between the jellyfish model and the value add-on core model (either way - they are tied together)

- Reading over the adilas value add-on core model (see link above) - reading section by section

- Focusing on the industry-specific skins angle - getting investments here at this level.

- We become the underlying engine and let the other companies push and sell things.

Prep work for the 1096 yearend payroll form. This is the annual summary and transmittal form for what was submitted. Pushed up new forms and code pages. Called Shari O. to let her know.

Shannon and I were going to jump on and do a work session. Steve was on the meeting. He and I ended up chatting for the whole time. After the meeting, Shannon and I went over some of the topics. I didn't take notes during the actual meeting. Most of these are from Shannon and I talking after the main meeting. Here are some of my notes.

- Steve was saying that he is planning on shutting down adilas or at least start tightening things down. He only wants to work on ROI type projects (return on investment). We tend to get pulled in many directions and don't always get paid by people who we do things for.

- Shannon was listening and showing compassion - I thought that was awesome. I was trying to follow her lead on both the listening and showing compassion. Steve is feeling pretty alone and beat-up by clients, outside parties, and even from internal sources. Software development is and can be a tough gig.

- Only funded products and projects. We have to make a switch.

- There is gold (tons of potential) but we have to remove the overburden (what is covering the gold)

- Cash flow and paying bills - even non people bills - like servers and other tech stuff and loan repayments. Steve hates debt with good reason. Back before the 2008/09 economic crash, they were quite extended for an automotive dealership floorplan. The debt became a crushing reality after sales dropped by well over half. This was back in the Morning Star days.

- Reoccurring monthly fees or revenue is the main thing that investors are looking for. We have some one-off stuff (custom code), and they don't count storage or other reoccurring fees. Especially if they go away or may go away (decreasing) - Investors are looking for monthly reoccurring revenue.

- We took some time and went over some history. We have been doing this for years and we really have been trying to do our best. It's been super tough.

- Repeat patterns - we have seen certain things over and over again. It has to be a different approach forward.

- We talked about options to scale back and then build up

- There is value in what we are doing (but we need to stop)

- The home base (golden goose) is going down... what do we need to do to save that? Steve was saying, it (adilas) is in the ER (emergency room), on life support, how do we tend to that?

- No fun to do what he did (Steve - talking to us and bringing us the bad news)

- Having skin in the game (who is invested)

- Steve said, the gun is pointed in my direction, meaning if things go south, he is the primary percentage holder.

- Staying up late, losing sleep, working weekends, etc. It has been crazy!

- SBA loans and other debt... crushing - long term - we are in a hole

- He really wants things to switch to hourly work and monitoring how much is being paid and who is doing what.

- Supporting each other

- Looking for a future vs saving what is there right now (saving the patient)

- Both Steve and I have had to chat with each other over the years - talking each other off the cliff (wanting to bail out)

- Tons of pressure for paying non-negotiable bills - everything is on auto withdrawal.

- He already went through this... meaning shutting down a company. It hurts.

- Shannon and I were talking about roots and branches and how those need to be graphed in at times to help save the whole.

- I was saying or telling Steve that I make decisions based more on gut feelings, promptings, and impressions vs straight logic. That's who I am.

- We talked about being led - spiritual stuff - getting divine help and trying to listen to what the spirt is saying.

- We want to mix things up. Talking about existing pieces vs following what feels right.

- Fundamentally different ways of looking at the situation (logic vs feelings)

- Compromise and bending but still pushing forward - mixing things together.

All in all, a good but hard meeting. I really want to keep pushing forward, even when pure logic says no. I do feel driven to help, let's see what happens. After Steve left, Shannon and I chatted and will try to mix and blend the different pieces where we can. We have to keep pushing.

Paying bills and recording notes. Meeting with Bryan. We were looking at some of his restaurant table assignment stuff. This is new functionality with saving quotes and assigning flex attributes to the quotes and invoices from within the shopping cart. He added some new functionality and we walked through things. Small code review.

Emails. Small bug fix for a client. Pushed up new code and sent a small email to let them know that the new file was up and live. Emails and text messages with Cory to setup some work session times for later in the week.

Recording notes from 1/12/26 to 1/17/26. Fun to go back through things. It's been a busy week. Lots of meetings and some great break throughs - planning and direction wise. Entering things on the adilas side. Paying bills.

Working on some CSS changes for files with loops and output tables with form fields in the tables. Basically, some of the bulk tools. We made some changes to the CSS the other day. These were some pages that needed some small adjustments on the field sizes (either too big or too small). Pushed up new files to all servers.

Small CSS fixes for Cory. Fixing some of the production stuff. Had to go in and force the field size widths and make some CSS changes.

Working with Bryan. Small CSS changes. Going over his MVP list for restaurant style management. He is working down his list and only has a few more things on the MVP part of the list. There are still some other things, but he is getting much closer. I'm proud of him.

Quick meeting with Alan. Touching base and both sharing where we are heading and what we are working on. Rescheduled another meeting for each week in January.

Working with Shannon. We reviewed the jellyfish model page, made some small edits, and then jumped into the adilas questionnaire summary page. Reading over those documents really helps us see where we are heading. This has been years in the coming... As an observation, Shannon was saying that us not having reps (independent salespeople) has cut off some of our sales stuff. Not only sales, but we have cut off the education and support arms as well. Those reps used to provide that supporting service as they worked with our clients. We are trying to get things under control, but it has stopped the inflow of new leads.

As we were reading, it was just making more and more sense. We need to stabilize the main adilas team and provide some more structure while still keeping the adilas culture and flavor. That could be interesting - lots of work to get there. We are getting there, but it still needs some love and dedicated action. It was fun seeing some of the ideas and concepts connecting and basically seeing the dots come together (connecting the dots).

Working on some more global CSS changes for snow owl pages (adilas CSS theme). Mostly working on form fields and formatting for text, numeric, text areas (bigger notes fields), selects (drop-down menus), and other form fields. Pushed up new code.

Meeting with Bryan. He wanted to do some planning on the Finetech and host huskie projects. We looked over some of his notes. He is gathering some little bites, chunks, and getting a number of recommendations from ChatGPT. Harvesting some of our user's feedback and recommendations. That is huge.

Meeting with Russell and Abby. Russell is using notion (online software solution) to push up some portfolio pieces. He was talking about using their existing tools and just a free hosting spot to show his work. He was saying that you are basically selling your work in a way that they, your clients, feel confident that anything that you do will work and be awesome! These are some lines from a video he was showing us, from some guy on YouTube. I didn't get the name. People do not read. Write with your heart and edit with your brain. Anyways, some key phrases from a YouTube video.

We then switched over to update some CSS for the adilas form fields. This was huge. I asked Russell about it, and I was going to go in and practice. He built the original snow owl them for adilas (based on the project CSS theme). Instead of just doing some small in-line changes, he pointed me to the main or master CSS file. We spent the rest of the session working on the CSS. It was more than I could have done on my own. He was a huge help. That was awesome. We didn't launch it, but we got it pretty close. I still have to browse a ton of pages and make sure that we didn't screw up anything. These were global CSS changes.

Meeting with Abby and doing some graphic editing. She is doing well and working on some new graphics. She was getting stuck on certain layouts, ideas, and options. She is doing great. You can tell that she is new at it, but doing exceptionally well. Fun session. We went over a bunch of things. Even Heather jumped on with us and gave her some feedback on her graphics.

Working with Bryan on some ecommerce changes. Small bug fix.

Recording notes from past few days. Also went and did some checking on the videos in the adilas lite (fracture) page. I changed them from the adilas content server to a folder on a Google Drive storage location. They should play much better. Here is the link to that page - https://data0.adilas.biz/lite/adilas_lite_videos.cfm

After I finished those videos. I started helping to convert other videos from the adilas content server to the Google Drive folder for quicker downloads and access. See element of time # 12617 in the shop for the links to the new videos.

Emails and recording some notes. Then jumping on a meeting with Shannon. We spent a little while going over new changes. Lots of moving pieces. Then did some work on the glossary. Finished up the D's in the glossary of terms. We finished up with going over some plans and then rehearsing some of the possible actions that are needed (small practice session).

Joke from Shannon - She said that an accountant was giving a talk. He was talking about some crazy stuff that they have to do. He then asked the audience, what is 1+1? Of course, it is 2. If you ask an engineer what is 1+1, you may get some technical information, but it still ends up being 2. If you ask an accountant, what is 1+1? They look and around and then ask you, what do you need that to be? I thought that it was kinda funny.

Joke - I heard this one on my hike this morning with my buddy. These cannibals wanted to join the corporate life. The corporation wanted to diversify and fast tracked them in for an interview. At the end of the interview, the HR person asked them directly about being cannibals. They promised that they wouldn't eat anybody. All went well for about six months. Then a janitor went missing. There was a big investigation and what not. They pulled the cannibals in and asked them about it. They said that they didn't do it. After the meeting, the head cannibal asked his people, did one you guys eat the janitor? One of the guys sheepishly raised his hand. The leader then said, you fool, we have been feasting on middle managers, team leads, and project managers for months. Why did you have to eat someone that they noticed? Anyways, it was kinda funny and helped the hike go along better.

Meeting with Bryan. He was showing me some AI chats and discussions that he has been having and talking about direction going forward. He was showing me some stuff on his restaurant and table management stuff. New features inside of adilas.

Good meeting with Steve. We went over tons of different things. Here are some of my notes.

- Fixing the Grok AI Agent. It is available but not yet trained. We have it hooked up, but hidden... Just us can play with it right now. It will be an ongoing project. We made it so that we could push it up live but, once again, no one knows about it and we don't want them to know about it yet. Steve wanted it to show some people that there is some potential (seeding the discussion).

- Lots of talk about sales and generating revenue. Steve wants to work with people who are willing to talk to anyone and then when they want a demo, he and Sean can step in. He doesn't want to train them on everything, just a simple salesperson who can generate leads. He wants our team to do the demos.

- Steve was asking about Alan. We jumped in and looked around at both the system (timecards) and bit bucket. I reported that I had met with him and it was a great meeting.

- We talked about adilas and expectations. There are a lot of undefined rules and assumptions. We are planning on refining some of that as we go. It just is what it is right now.

- Steve is doing tons of small mini projects for Cory. He is really busy doing all of the little things. I would say he is getting buried. I have been there so many time. I feel for him.

- We talked about a couple of possible partners and outside businesses that have expressed interest in what we are doing. Currently, there seems to be lots of demands and not much show of support so far. It is just starting out, and we aren't sure where it is going. We want the leads, the customers, and the work, but so far, it hasn't really produced.

- We are trying not to waste time and energy, but we really don't know where to go. We are basically, trying to follow the money. Picking up the pieces.

- Steve and I talked about options in sales and also trimming down our current team. We have to cut some costs. It is rough sometimes.

- We spent some time talking about payment processing and how they do their billing. They, the payment processors, usually do a percentage of the monthly credit card sales. We would like to do something similar but instead of doing just the credit card processing, we would like to do a small percentage of the total sales per month. We are thinking from 1% to 1/2 of a percent. Somewhere in there. Trying to figure that out.

- Steve was talking about robots and even payment processing is becoming more automated and even mobile. He was talking about advancements in robots and other technologies. He reads a lot and likes to keep up on that stuff.

- We would like to get our Grok AI agent up and working. We feel that we may be able to control that better than having an outside party program and control it. That is still a lot of work. Steve really feels like if we don't embrace the full AI wave, we will be left behind.

- Bryan popped in for a minute. I told him that I would text him when we were done. We were spoused to meet but Steve and I got started late.

- Bryan is working with some CPA's and trying to get them to see the vision of what we are doing. Long ago, that was Steve's vision. He wanted to fly around in his plane (he's a pilot) and go see all of the CPA's and show them how adilas works. Funny but cool, old memory. Still a possibility.

- Steve has been around a lot of salespeople. He was sharing some of his experiences. We need people in places where there are a lot of other people (businesses). We don't have anything right now, as far as a salesperson or a sales team.

- Sales is just a game of numbers. You also have to be willing to be told no. Not all personality types can do that. Steve was mentioning that we have started a bunch of people but they haven't worked out. This may not go here, but I'm going to add it in anyways. Steve and I were talking on Monday, 1/12/26. I had a meeting later on Thursday, 1/15/26, with Shannon. She made an interesting observation. We used to have a rep type model, where the rep, an independent, would go pedal and push our product. They would then get a commission and also be able to get monies directly from the client to help with anything that the client needed. That was very successful. They, the reps, would max out and eventually stop, but each one could handle a certain number of clients. We had some reps that were making great money. Because it wasn't super organized, we decided to pull that back internally. Due to budgets, we have not been able to fill that same role that those reps were providing. We have way more control over what is being done, but we don't have anybody out there pushing on things. Interesting observation.

- Back to the meeting with Steve. After we talked about sales for the first little bit, I changed gears and did a mini pitch to Steve about focusing on people and trying to stabilize the team. That conversation always comes back to funding and where do you get the money from? This has been a common theme over the years.

- I was drawing and showing some ideas. We have focused on features and functionality so much. We keep building lists and slowly clicking through things. I really feel like we need to change the focus to people and the team vs the next cool thing. The sad part is, we have done this for years and years and years. We keep thinking, when we get such and such done, it will all get better. We get to that point and then there is always something more. I honestly can't even see the end of what is wanted (feature or functionality wise). It feels like a perpetual or ongoing list of wishes and demands.

- We jumped in the system and were looking at sales, numbers, trends, year over year totals, etc.

- We may want to allow the developers to go back and bid (put out estimates) on custom code projects. That's what they used to do, back in the day. We tried to pull that all under the main adilas roof as well. That was super expensive. We may need to figure out a hybrid and see if we can make that work. We don't want a full wild west again, but we may need to bring some of the independent pieces back in. It just costs too much for us to fully support a full staff of full time developers. We'll figure it out.

- Our costs are around 40% (roughly). So, if you had a system sell for $100. We would use $40 to pay for servers and other small things. The other $60 would be profit that could be split and/or divided to create some sort of incentive. Steve is trying to see if he can get anybody to play that way. We just have to get more clients. He was pitching a 50/50 split of the profit. So, for a $100 deal, that would be $40 overhead (costs), then split $60/2 or $30 per entity that is helping with the sale.

- We were talking about setup, activation, and selling systems. We are seeing a growing demand for enterprise level functionality. They, our clients, just expect us to have it all built. They really want it, but it is only partially done, not all the way yet. We end up getting stuck in the middle, footing the bill, and not being able to just sell what they want. We already have vendors, customers, and items on the enterprise level. We just need so much more. Well, you have to start somewhere.

- Steve was talking about 10 free hours of training and then rolling into $65 per hour after that. We can help with anything that is needed, whether that be training, data entry, bank reconciliation, inventory help, balance sheet and accounting work, etc. We offer a lot of services. Basically, what do you need? We can help.

- Steve wants to find some power users and see if they would like to work for us. We have had great success by hiring people who were once adilas users and then bringing them in and onto our team. They already know and love adilas. They tend to find a good home with us. It just comes down to budgets again.

- As we were talking... I was pitching things and it kept getting met by something like... We've tried that... We need to do something different. I don't feel like that. If we did try things, the timing may have been off, the wrong person, or it wasn't really tried. I don't want to just keep randomly trying things. I think we need to focus on people, talents, skills, and personalities. If we can get the right people in the right places, and get them trained and supported, it will work. I know it!

- We may need to try things again! Lots of things are changing and been changing over the years. We have been doing this since 2001. Adilas became a real entity in 2008. We need to circle back around and focus on people.

- The topic switched to AI. Steve wants us to use AI to build code for us. He thinks that we can reduce our tech needs by 60%. He uses it tons and tons. I use it as well. We want to get our other developers up and going on it. It's not that they aren't... we just need to keep going. We need to look at it as a tool, not the only answer. It does have pros and cons. It definitely has its place. Certain things still need the human touch.

- We ended our meeting by him telling me that I could look around and work on a plan and then bring it back to him. We have to make some changes. That is for sure. I just don't want to randomly do things that may hurt us in the long run. It takes me so long to train new people. I hate to see them just go away. We have a team, but yes, they are kinda tired. We have been running hard for years and years, almost without any breaks. That is rough. We will figure it out. That's the new goal. Figure out how to make this work and stabilize the team.

Working on video links for adilas videos on Google Drive. Testing links and watching videos.

This note was for me... old videos - on the content server - moved them to a new folder on google drive.

sample_demo_site_adilas_cafe.mp4 - on Google Drive
https://drive.google.com/file/d/1Jv7tMngLLc7jrqnsj61DWzclBWkoImi5/view?usp=drive_link

adilas_cafe_nav_layout.mp4 - on Google Drive
https://drive.google.com/file/d/1wPrEMuzAdvwepdZ9tveV5DXRxIVFGnge/view?usp=drive_link

education_mode_overview.mp4 - on Google Drive
https://drive.google.com/file/d/1j2676h5toUDtOONAMQsadzl-1vStsyIe/view?usp=drive_link

adilas_quick_search_demo.mp4 - on Google Drive
https://drive.google.com/file/d/1it3AUgl-IQ3yFVcncbFOAETVo_on4CxP/view?usp=drive_link

invoice_dashboard_overview.mp4 - on Google Drive
https://drive.google.com/file/d/1kDY_a19KXhtfq_j3jLa7Gy0p6NoATX4I/view?usp=drive_link

invoice_dashboard_overview_2.mp4 - on Google Drive
https://drive.google.com/file/d/1OUUKzt7GhUB-Jeb1c5bsYVCH9t6VwMoW/view?usp=drive_link

internal_shopping_cart_r1.mp4 - on Google Drive
https://drive.google.com/file/d/1l7bFK0J7n9fYtHgjoc313EiTC5nBqgGG/view?usp=drive_link

fracture_adilas_lite_interface_tour.mp4 - on Google Drive
https://drive.google.com/file/d/1fLhyMVdsVUo1gLQZInYI3j7bwllRLDjB/view?usp=drive_link

fracture_style_guide_demo.mp4 - on Google Drive
https://drive.google.com/file/d/1QHUjD-fkWRoSVkDHInQxikWQ_991NxNb/view?usp=drive_link

mapping_out_the_application.mp4 - on Google Drive
https://drive.google.com/file/d/1C0iD6hBEQsyfKIvY-iiw3ZQ1XDTtCwAY/view?usp=drive_link

adding_timecards_in_the_adilas_shop.mp4 - on Google Drive
https://drive.google.com/file/d/1u-AJLFZJLIAPuurWQWG22abwM4_cNPca/view?usp=drive_link

the_knox_report.mp4 - on Google Drive
https://drive.google.com/file/d/1tA3ZuTcIM2vZGyHF4VGz5Qo-N3c2-7Ev/view?usp=drive_link

cart_touch_and_discount_options.mp4 - on Google Drive
https://drive.google.com/file/d/1r-R5g-KR5CqytGZfCggsT7YQfo4wnCBw/view?usp=drive_link

intro_to_vendor_credits_part_1.mp4 - on Google Drive
https://drive.google.com/file/d/1iYb-BthJaAQnKeBs8-1qVR1luxpNXOo1/view?usp=drive_link

intro_to_vendor_credits_part_2.mp4 - on Google Drive
https://drive.google.com/file/d/14bk8JVH1HJSfO2eQ3DrJ4L6CNkjUM_7d/view?usp=drive_link

custom_horizontal_time_view_demo.mp4 - on Google Drive
https://drive.google.com/file/d/1zuY3BjU1jK9UbVCPzZF8PzixaVbc-2eK/view?usp=drive_link

There are notes from this morning... 1/12/26 - these notes may seem personal - they are what happened on Sunday 1/11/26 - I recorded them on Monday. They play into the mix as this is the backing for us trying to do what we are doing. It is personal, but still super important (to me at least).

- I was fasting yesterday - good session - had a great "download" (term from my mother) session and filled out some post-it note pages. See EOT # 12616 for details.

- I spoke in church on Sunday - I had fun - hopefully it went okay - I tried to follow the spirit.

- I also enjoyed some of the other meetings at church - Lee Lower gave a fun thought in Bishopric meeting about a guy and some healing and mending relationships - really good message.

- In the next meeting, young men and young women leader training, Reese Hulbert gave a great thought on Satan and how he tries to make us run and hide - then talking about overcoming that fear and following the Lord - how can we dispel that encroaching darkness, shame, fear, and negative thoughts - super good message.

- I was praying - as I finished, I was looking at a quilt on my bed - the diversity is awesome - all of it fits and lays together to make the whole - so fun.

- During sacrament meeting, Lilly Atkinson spoke on cheering each other along - she ended with a challenge - "take one more step" and "bear your testimony" - I really liked the take one more step challenge. Sometimes, that is all we can do.

- Heather gave a great talk in church as well. I took a bunch of notes in my church notebook - great message - moving forward with joy - becoming - "be" & "coming" - breaking things apart - we all get to be part of His work.

- Plan as if for year - act as if for years - D&C 50:17

- In priesthood meeting, Ed Herrmann, was giving the lesson on new beginnings from Elder Kearon from the October 2025 general conference. Jesus went about doing good - At the end of the lesson - Ed was talking about an action strategy that they use in the military - It was...

1. Intel (info or gather info)
2. Plan
3. Rehearse
4. Execute
5. AAR - Pause (after action report)

- Small note... I was typing these notes and got to the note above this about the military action plan or action strategy. I was able to use that little piece in a meeting that I had with Shannon on 1/13/26. That is awesome. The timing was perfect. I just finished typing it before the meeting and then I had to use it. Small mini miracle and blessing. My notes were able to tie into another piece that I was looking at on Monday night (1/12/26). We were helping our daughter do some goal planning for the new year. In the pamphlet, it kept prompting for putting your goals into this format: Discover, Plan, Act, Review - As I was working with Shannon, I was drawing a parallel between the child goal setting strategy vs the military based strategy. They are very similar. They use different words and the military one has a whole section for rehearsing or practicing before doing the actual event or action. I thought that it was very interesting. I was telling Shannon that she was technically helping me do some planning and rehearsing for where we are heading. Good stuff.

Back to my notes from Sunday, 1/11/26 that I wrote on Monday, 1/12/26... I got side tracked

- After church (on 1/11/26), I spoke with Bryan Dayton and told him that I was planning to talk to Steve tomorrow (Monday) about pushing forward - gave him a few small insights into my plan from my shaving session on Sunday morning - see other notes.

- Came home, played a game with Brooklyn

- Super yummy meal after breaking my fast - potato soup and corn bread

- Made chocolate mousse

- Played a game with Heather and Brooklyn - Heather won

- I got a blessing from my dad - we talked and chatted for a bit and then I got a blessing (father's blessing) - I have had many of these - Lots of great love, advice, inspiration, and remembering my worth - I doubt myself sometimes - Here is some advice that he gave me: Take care of yourself, your family, your church calling, and then your profession. Even though profession is forth on the list, that doesn't mean that you give it a forth rate job. He also felt that I should go and meet with Steve - face to face - really try to help - even help repair the relationship. It has been super stressful. He also recommended that I read a few poems (motivational poems) - I have those in a different notebook.

- On the going out to Salida to meet with Steve, I was thinking, maybe we have a team meeting - in person - to go over plans and such - going back to what Ed said (military strategy - intel, plan, rehearse, execute, AAR (pause - after action report) - focus on the plan and rehears sections.

- I have been in so many meetings... tons of training - that is an asset (meaning church and business meetings)

- Quick 1-pagers - Bishop Shawn Smith loves the quick - at a glance - what is going on

- I saw Reese Hulbert use a few quick - at a glance - one pagers for a training meeting. They really seemed to help.

- Contact Gene to see about getting some funding for a big push. Sent him a text on 1/12/26.

- Graphical homepages

- Finish up the MVP list - Estimating somewhere between $500-$750K to finish up that push and those pieces.

- Work as if for years

Emails, paying bills, reviewing notes from over the weekend. Planning for a meeting with Steve. Reread some great poems that have a great message. Click this link to see the poems (on a different entry from a couple of years ago). Pushing up videos to a new folder inside of google drive.

Translating from post-it notes on 1/11/26

- Sunday morning - I was shaving, getting ready for church. I had a flood of ideas come into my head.

- We go for it on 4th down (football analogy)

- Reinforce the team - goal 1

- Goal 2 - We make sure that keeps working (meaning goal 1)

- Morning meeting at 9:30 am (get some communication stuff going on)

- Let people (our team) run... minimal on the micromanagement

- We focus on people... there will always be more projects and features

- CSS on forms for classic looking forms in the snow owl theme

- Look and feel to snow owl - help fix internal and existing pages look good

- Training - could be internal training, AI training, or external training

- Presentation Gallery - Keep pushing on that project

- Images for the adilas lite plan and the investment opportunities

- Abby - Talk to Steve about getting her involved

- Work with the design team - Chuck, Piper, Sarah

- Move key videos to Google Drive vs on the content server. It just can't serve them up quick enough.

- On the AI Agent - Use what we have - Set it up so that it tells people "I'm good at nav" - Polish the 350 existing prompts and tools.

- Suzi - Step-by-steps - small documents with information and instructions. She is really good at that.

- Sean and Cory - General Training

- Prepare for 100+ new accounts - What would that take?

- Open things up!!!

- If needed, we have others who can help - Dustin, Eric, and John. There are others as well.

- Shannon - She has been such a great helper to me

- Let Alan lead out - Help him succeed. He can do so much more than code.

- Get out of the way

- Leverage debt - put all of the adilas shop or adilas lite stuff into adilas as real payables - bring it out of hiding - true costs and costing

- Co-owner Advocate - possible new title, if needed

- Mini bank accounts for each person and/or department - help the team feel safe, supported, and funded

- Be in someone's corner - believe in them

- Overcoming fear - Satan wants us to run and hide

- Simple 1-pagers (one-pagers) - at a glance

Recording notes from a couple of days ago. Also paying some bills and uploading some receipts.

Working with Bryan. Looking over the new changes for the smart group rules and being able to do tiered pricing based on quantities and custom sizes. We looked over some of the code. Light clean-up. He is going to turn the branch over to me and I will do some testing and fix some merge conflicts. Talking about circling the wagons and touching base (communications and watching out for each other).

Meeting with Alan. Going over existing AI trends. Talking about our existing model. We logged into the Nxtlinq backend dashboard and looked around (current adilas AI agent backend). Lots of chats and what not, going back and forth about ideas and options. Alan was saying that he has been looking up what customers really want from an AI compliant ERP system. We chatted about that. We then did a small session showing what we are doing and how we are using different AI pieces and projects. I got into VS Code and showed Alan around a bit. We jumped into ChatGPT and looked at how it is helping as well. We chatted about some new ideas and where to help take things, going forward. We also setup a time to meet next week.

Working with Shannon. We spent more time on the glossary of terms. Most of our work today was in the D section. We also spent some time at the beginning talking about changes and how AI is affecting our worlds, in both good and bad ways. Very interesting. It is just a tool and has both pros and cons.

Abby came up from Ogden, and we spent the afternoon working on graphics. We did some small critique stuff and talked about what we like and how that could play out. She has been doing a bunch of training and practice files. She has a couple of new graphics started. They still need a little refinement, but making progress. I have a need for graphics in the adilas lite website and fracture plan, the investor opportunities, and the adilas presentation gallery (graphics for the modals and more information sections). 

Steve canceled the meeting for tonight. He wants me to finish up a couple of projects that have been hanging out. They did send a small update via email. This is what I got from Thomas:

We have updated Adi global context training with all the arsenals, including but not limited to increase context limit, RAG implementation that minimize up to 75% less token consumption, GPT5.2 update and more.  Looking forward to Brandon getting back in adi training mode.

Formatting and checking new 2026 federal withholding values. Working on a new database update for the 2026 federal withholding values. Checking and running the new update code to set the 2026 federal withholding values in the database. Pushed new files up to all servers. Running and cascading changes on the different servers.

Working on new 2026 federal withholdings and payroll tax calculations. Pulling data out of the Pub-15-T document for percentage method values. I spent a couple of hours with ChatGPT to help me get the correct values. I was pushing up PDF files and tables, having it read and format the SQL insert statements that I needed. Here is the link for the AI session.

https://chatgpt.com/share/695d9c3a-87fc-8007-ae5e-eada5f629dea

Internal tech support. Emails out to some of the guys in the field about images and bulk upload options. Catching up on recording notes from the past couple of days.

Working with Shannon. Going over glossary terms. Finished up C's and started into the D's. Good session.

Phone call with Alan. Touching base, sharing, and swapping some ideas. What is working, what we are doing, and how things are going? We spent some time and chatted about AI and thoughts and ideas. We are going to get together in a couple of days and do a little show and tell session. See what little tips we can work on and share.

New changes for tax year 2026 - new withholding values and look-ups for federal payroll tax calculations and withholdings.

Bryan has been meeting with some accountants and getting their take on modern accounting and such. He is seeing where they have needs and wants. Sounds fun. We then switched over to do some code review on his branch with new tiered pricing rules and assignments for selling things by size. After we looked over some of his new changes, we then flipped to a different branch that was dealing with flex attributes for shopping carts, quotes, and invoices. We looked at a bug and got it fixed. He is going to tighten things up and we should be able to do the final code review next time.

Recording notes and paying bills. Reading and sending out some emails. Looking over some code for Piper. Fixed a merge conflict.

Paying bills and recording notes. Cleaning up and getting organized.

Spent the first 2.5 hours working on the Grok AI agent and getting things tied in there. We are just starting out there and tiptoeing through that process. We are using Grok as the AI agent, for this new one, and then using ChatGPT to help us know how to code the stuff for Grok. Kinda funny. Anyways, we had a great session. We were in deep rewriting code. We were asking all kinds of questions and testing those changes that we were making. I was happy with the session.

The last half an hour, we were looking at the code from Alan and the new CardPointe stuff. We need some new code and changes but were not sure of the status of that project. We looked at his branch and poked around for a bit. I will give him a call. He and his wife recently had a new little girl. I imagine that he has been completely pulled into that mix (life in general).

Working with Shannon on doing some definitions and glossary terms. Started working in the B's section. Finished up that section and got part way through the C's. Good session.

Recording notes. Flipped back over to the year-end payroll forms and updates. Pushed up new files and forms. Sent an email out to the team. Did some work on the new 2026 withholdings and downloaded new Pub-15 federal tax documents. Those are my favorite... 70 pages of PDF tax info and tables. So, fun... :)

Small bug fix on the cart top mini gram controller page. We had a variable that was getting overwritten. Removed the conflict and push up files for testing. Small email to have them do some testing. I didn't have access to the sites that were in question. Pretty small change.

Small tweak to the attributes page on the presentation gallery. It was skewing the background and images. I removed that feature. Hopefully that helps. Switched back over to year-end payroll forms and tax updates. Working on small changes for the 2025 1099 NEC (nonemployee compensation) form. Cascading small changes through the year end pages.

Work session with Shannon. Working on the adilas glossary of terms (element of time # 4030 in the adilas university site). Finished up the A's and started into the B's. We have a long way yet to go. Fun session today.

Reading a large email from Wayne. He has been working on some system stats and running comparisons. He is optimizing speeds and processes. He gave us a couple of new links for pages and resources. Looking around and checking things out.

On with Bryan for a code review session. Working on his dynamic rules for tiered pricing using something other than quantity. It is pretty deep. Lots of logic changes and tweaks. We still need it to be a little bit tighter. It's getting close.

Working on yearend tax and payroll forms. Checking form fields, tab orders, and layout stuff for new W-2's and 1099's.

Meeting with Bryan. Looking over some different projects. He is working on two main projects right now. Most of our work was looking at his changes to the my cart favorite buttons and the smart groups (tiered pricing). He is working on some code that deals with changing the rule type from normal tiered pricing based on quantity to rule types based on other dynamic fields or settings (like sizes, diameters, or something).

He is going to refactor a few things and clean it up a bit. Our plan is to meet again later today or tomorrow to do a deeper code review.

Meeting with Steve. He is working with Grok and ChatGPT to help him code some things. One of his projects is working on some ecommerce sales by category specific settings. We flipped over to working on the Grok AI chat bot inside of adilas. We setup a scratch file and were working with it to see what the responses were. We changed some paths and did some light debugging. Our next joint session will be again on Thursday afternoon. He may work on it as he gets time. I pushed up all of the changes to his branch inside of bit bucket.

At the end of the session, we were chatting about other developers and other projects. Light catch-up stuff.

Emails and recording notes from last week. Research on JavaScript fetch commands and looking over code from Steve's Grok AI agent project.

Working with Steve on his Grok AI agent. We had to play around with it and get into the JavaScript stuff. He is going to push his branch up and I'm going to pull it and play around with it. We started getting deep in the weeds. I really need to play with it locally to get it going and connected. He is making great progress. I'm impressed.

New custom email settings for a client. Created them a custom email template to use while sending adilas invoices from their corporation. Added some custom branding and light work on some look and feel stuff.

Every year we go to the IRS website, download the new forms and convert them into the correct adilas forms for payroll and yearend reporting - W-2's, 1099 Misc, 1099 Nec, 1099 Int, and form 1096. We take what they give us, flatten them, remove all of their existing code and fields. The files are password protected, so flattening them strips that off. To flatten the files, we actually trick it. We open the normal file and then say print. We select the print to Adobe PDF option. This allows us to flatten them and resave them. Somewhat of a work around.

We then overlay our own form fields so that we can talk to them through code. We do both blacks (data and physical output) and reds (data only). The reds need to be done on special documents with magnetic ink, so we just do a data overlay, with no output other than the form fields. All part of the process to offer some payroll functionality.

Small data fixes for Sean on the data 4 server (part category stuff). Recording notes from the past couple of days.

On a meeting with Bryan, looking over some new rules for smart group buttons and tiered pricing, based on sizes, vs quantities. He is making good progress on that project. He has a client that wants to bulk price things based on some sizes.

After the meeting, I made a small custom email change for Shari O and Applejack RV Park. Made changes and pushed up new files. Sent Shari O. an update email letting her know that everything was good to go.

Working with Shannon on glossary terms. We were in the "A" section. Going over some the verbiage and doing some light clean-up. It may be a while, to get through all of them.

Towards the end of the meeting with Shannon, Shari O. jumped on. I was helping Shari O. out with some changes for a client (corp-wide settings and custom invoice stuff). I showed her how to do some light HTML to add some bolded items and some line breaks to a disclaimer. We chatted about other stuff that is going along as well. Good catch-up session.

Working with ChatGPT on the round 2 plan for helping to train the AI agent model. Good session. Here is the link to our chat session:
https://chatgpt.com/share/69462819-9640-8007-9f14-948f203349b9

Emails. Light tech support to help Shari O. out with some rules and regulations for an RV park. They wanted these rules as part of their in-line disclaimer for their invoices. Recording some expenses and uploading images. Recording some post-it note ideas from last week.

These are a few ideas that I scribbled down on some post-it notes from last week. Sometimes, I'm not at my computer, or things just come into my head while I'm thinking. Post-it notes (pen and paper) are some of my fastest tools.

Notes from 12/16/25 - post-it notes

- Run through some scenarios with the AI agent. See how it is doing.

- While on my hike today, I was thinking about training the AI agent on how to do our style of accounting (following the data through the different processes).

- Train both human and computer

- Document everything and keep it public facing

- I kept thinking about a kid who presented his code project, with a known bug, to get feedback and get advice on how to fix it. That was bold and inspiring. Sadly, I like to have my stuff together and I'm scared of presenting things with bugs or huge known issues. I would rather hide and work them out. I may have to get over that... That may be a challenge! :)

- On the meeting with the AI guys (tonight 12/16/25), Ted was trying to push us to get SOP's, flow charts, processes, good documentation, walk through the reasoning, and even solicit our clients and see if we can get their SOP's and documentation. We, as a company, know that some of our clients have paid big money to get SOP's made for them. I'm not sure how that will go over, but worth asking.

Notes from 12/17/25 - more post-it notes

- On global context... either use an internal API or mirror certain information over to that server. Which way would be the most effective?

- Standardize the output

- I have data in EOT's (elements of time), media/content tables, photo galleries, subs of time, and flex grid. All of these are database tables and have content that I want for global context stuff.

- Create a new mixed mini API - pull from help files, elements of time, subs of time, photo galleries, media/content, and the new global context database table. Dump it all back as a JSON file through the mini API.

- Adilas University - All global context should go there. This was a small break through for me. I have it all over the place. Then I was thinking about where it should go. The thought came up about using the adilas university (site that already exists - with full adilas database functionality) and using that site or corporation. That will work slick and perfect.

- On the media/content, photo galleries, and subs of time stuff - only pull from things that are publicly facing - keep private, private

- On the database side, maybe duplicate or mirror certain pieces - main control will still be from inside the system (based on normal corporations, users, pages, and permissions). Keep the control stuff on the normal corp level. That is already built in. If we need more help, in the adilas university site, we can assign users and give them instructions and permissions where needed.

- When gathering content, look under the my docs folder and my personal folders on my local computer. I often save things to those spots. It may make it easy to go there and scoop things up. There are other folder where I stash things, per person, based on what we are working on. If we are really gathering content, maybe look there. Sweep the floor, turn over rocks, and look under bushes (virtually).

- On the mixed mini API results - maybe be careful for the term adilas - be white label sensitive - we want to pitch and sell our stuff, but part of our plan is allowing rebranding and white labels. We may have to do some global find and replace stuff. Maybe just do it normal first, then circle back around.

- Model the data - do some samples and look at what we want to get back - do some prototyping and mock-ups, just like other database or code projects. Design the outcome or output.

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

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

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

Quick graphic change for a client. Light tech support and light clean-up. Only took about 15 minutes.

Spent the rest of the session recording notes from 12/12/25. Ended up having ChatGPT help me convert the hand-written notes into text. We then explored some more options as to the full plan of where we are going.

Here is the link to the chat session that I had with ChatGPT - basically, a planning session with ChatGPT on our round 2 for the AI agent training.

https://chatgpt.com/share/69462819-9640-8007-9f14-948f203349b9

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

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

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

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

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

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

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

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

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

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

Working with Shannon. I was showing Shannon my notes from the past week. One of the entries had some notes and my spiritual experience (planning and brainstorming on training the AI agent). See element of time # 12527 in the shop for more details. Going over the power of the plan - reinforce, recruit, and then share it. It feels like a mini parallel to God's master plan. Another part of it deals with helping adilas get ready to go out to the world and be a tool that could be used.

We spent some time going over concepts and showing her what the context window was (concept) and how to help make it function at the appropriate level. She then helped me as we talked about using the CMS tables on adilas university (the corp inside of the adilas application called adilas university - corp id # 371) to create and make the global context records. CMS stands for content management systems. All of adilas is basically a giant CMS type application. We will use our media/content database table for those global context pieces to help train the AI agent and our users. It is perfect, it already exists, and has been being used since 2013. We will just repurpose a small portion and use it more heavily from within the adilas university site and corporation.

Switched over to working on the white label section on the fracture (deeper development and system code) build out. We finished up that section. Yeah! After the meeting, I sent Steve a text about using the media/content database table as a CMS system for adilas university and global context stuff. That will be super cool, and it is already done and functional. What a blessing.

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

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

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

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

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

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

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

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

Recording notes from 12/8/25 to 12/15/25. Also spent some time editing AI agent chat logs.

More AI agent training. See element of time # 12542 in the shop for all of the documentation (saved chat logs and starting global context files).

Quick edit for a client and reformatting some rules and regulations for their in-line disclaimer (inside of their corp-wide settings). Sent an email off to let them know that it was finished.

Working with Bryan. Going over one-to-many relationships for parts and items. He has some special pricing issues and questions for one of his clients. We talked about existing options and where we want to go with things. Currently, we have parent to sub items, parent to flex grid tie-ins, or smart group rules and assignments. These are all special one-to-many pricing options.

Going over which one would work best and what we need to change to make that happen. For his current scenario, we spent some time talking about the rules and assignments for smart group buttons. Currently, those rules are based on quantities. We were talking about doing some rules or rule types for sizes or some other characteristic. Good discussion.

Planning and doing some AI agent training for the adilas private model.

See attached for a starting place or file for the Nxtlinq AI agent. This is what it was able to gather to date. I made a few changes... See also the chat log for the new training session.

GoToMeeting session with Steve. We were talking about natural language processing (NLP). API issues (with our current model). Trying to overcome some memory problems and help it use our mini API's. Behind the scenes, the LLM's are getting faster, better, and cheaper. Going over models and options. Lots of talks on different subjects. Talking about API's and where things are heading. Information is becoming more and more easily to get to. Steve is seeing an increase in 3rd party AI tools. People and companies wanting to build out an integration with their AI tools and features. Steve and I have done a ton of 3rd party integrations... We don't really want to keep relearning the same lessons. Currently, he is saying no, vs yes. We've got to get our product fully to market before we do a bunch of new 3rd party solutions.

Recording notes. Prep for a meeting with Steve. We have been working on this AI agent stuff since August of 2025.

Here are a few elements of time that have some plans for where we are heading and wanting to do:

EOT # 12286 - Normal element of time plus media/content - more advanced prompts and tools

EOT # 12392 - aliases and stringing multiple prompts together - interface ideas - deeper prompts and navigation

EOT # 12497 - ideas on training

EOT # 12527 - other plans and global context

Bryan and I met up to look over progress for the restaurant and simple food service functionality. Bryan Dayton has been helping to chip away at this for the past year or so. We did a small review session and took a bunch of notes. Bryan then had the idea to take the new notes and add them to the old notes. We ran them through ChatGPT and it did a great job summarizing things up. We then read over those notes and talked about next steps. Here is the link to our small discussion.

https://chatgpt.com/share/693c91f3-a6bc-8007-a331-7ea33d2b84f2 - notes from Bryan and I from ChatGPT - restaurant and simple food service functionality

After going over plans and notes, we switched briefly over to some other projects. We will meet again on Monday to get into some other projects. We also briefly looked at some hours that have been recorded over on the ship B (adilas shop) side. Both Bryan and I (and others) have been banking some hours on projects that don't have full funding (yet) but we know that they will be needed.

Reinforce
Recruit
Israel (Zion)
Babylon (World)
Reveal & Interpret

---- Notes from a brainstorming and planning session (see attached)

So, just for fun, I had ChatGPT convert my notes into text (OCR style). Here are my notes in a typed form.

- Working on some planning to help with global context & AI/Human training

- I've been gathering some post-it notes for about a week. The electricity is out so I went over to my in-laws house. I'm converting notes from my post-it notes into notes in this notebook.

- 3 notes from 12/6/25: (see below)

Teach the AI agent how to delete or make things inactive - We had some chat messages where a user asked & the AI agent didn't say the right things. We just need to help it out a bit. Coaching...

Teach it how to get to stats & totals. The user asked some basic questions & the AI agent sent them to a decent/okay page, but it could have been better. Once again, more training

Fix & fill in the gaps

------------------

I had a couple of papers (post-it note style) from 12/8/25. Here are those notes:

- I have been thinking about stuff. I will be laying in bed & my mind is going & racing along.

- Make a plan... what tools & options do I have? Use what fits for each situation. It is okay to mix it up & adapt to what works.

- Plan as if for years - I can see some short patches and fixes - plan as if for years, meaning what is it that really needs to be done?

- I have this card & it talks about doing things "Glacier Style" - Carve your own path, go slow, channel your strengths, clear the way for others, stay cool, avoid meltdowns - I really liked that!

- Feed in the glossary - take your time & even add more as needed.

- Look at the prior plans - I've been working on this for months - Sometimes, I get going so fast, I start skipping things

- Work with what you have - that is a great base - you can always make more.

- Use one AI model to train the other ... That could be very useful. Harness the strengths of each model.

- Use voice to text to help with editing - where it fits

- Help the system learn - Take some of the chats & show the request, the response, and any suggestions - maybe help it by giving the answers a rating - just an idea

- Offering to save something for the AI agent - giving it some memory - How would that work? What would that look like

I took a few more notes on 12/10/25 - see below

- Build a small chunk specific tool - include meta data options

- Think in terms of small templates - I want this, this, & that for X - I want this, this, & that for Y - Try to stick to it - for consistency

- Spend some time training the little one - meaning the private AI agent for adilas

I also had some more ideas last night in the middle of the night, and early this morning on 12/11/25 - see below

- On the glossary items - add some terms like: AI, AI agent, AI context window, big data, BI or business intelligence, Knox report, mix, spread, delete, status, Nxtlinq, global context, meta data, vendor credit, special accounts, loyalty points, gift card, threshold, mini scan cart, refund, CardPointe, Clover, go mode, AI quick search, signature, e-signature, printer friendly, bulk add, bulk edit, bulk transfer, AI tools, cash counter, fulfillment, AI image generator, touch or touch screen, modal, retail, dashboard, flex attribute, KPI or key performance indicators, due date, tiered pricing, vendor catalog, delivery, age verification, view only, cultivation, metrc, percentage calculator, sales and profit, Adi, harvest, plant tags, data table, label builder, fracture, chart of accounts, reflexive flex grid, direct deposit, parent/child, try storming, and half baked

- When adding global content what about default sort orders for tools & glossary items? Expanded topics, etc. see next page for a huge list of what we may want to store

- Build a new tool for the AI agent to get at the data - think about a sliding window (AI content window) over tons of data - we only want it to pick up what it needs to

(sliding window diagram text skipped but referenced)

- Brainstorming on types of data that we may want to collect & organize...

- general or global
- help files
- glossary
- tools
- developer's notebook
- ideas
- brainstorming
- documentation
- R & D (research and development)
- extended topics or deep dives
- chat messages
- news & updates
- history summaries
- emails
- tech support
- special tools
- business functions
- application players
- core concepts
- FAQ's
- tutorials
- step-by-steps
- Screenshots
- graphics & visuals
- sales marketing materials
- internal
- admin tools
- AI summaries
- user stories or scenarios

For me - add links, references, sources - document things at different levels

- Recruit help!

- Send an email out to our team - looking for (fill in the blanks)

- Send content & information to me & I'll enter it into the system (at first or for the first round)

- When we are ready, and if they (our team) wants, we can help train them on how to add, edit, & view the global knowledge base stuff

New notes from 12/12/25

- Small note or context - I was doing some scripture study and looking up some information about being alive & times & seasons - It took me to 2 Nephi 25:25 - then started to look at some verses both before and after that - Some of that was talking about scattered Israel (like in the Bible) I had this thought about adilas... and what I am working on. (see below)

- Things are all there... they are just scattered - we need to gather them & help them to be more organized - once they are gathered and organized, the goal is that the knowledge & information will continue to grow & thrive - help gather and organize!

- On training the AI agent I may have to tell it something & then tell it what I told it - light review & reinforce the key points

- I want to fix and fill in the gaps... That is awesome - At the beginning, anything will help - there aren't gaps, there are holes - just start

- We can always circle back around & refine, fix, patch, polish, and/or rebuild - like try storming, we plan, we do it, we see how it works, & we plan on circling back around again & again - small feedback cycle - build & break, build & break

- Terms (words) that I was looking up... alive or living... learning, growing, being used, purpose

- I do a lot of trail building and maintenance - it is quite the process... We have to scout things out, explore, make mistakes, flag, clip brush, do dirt work, build walls, bridges, crossings, bank retention etc. Then we need to use it (traffic), get others to use it, & then circle back around again - very similar to the try storming concept

- What does it take to become a master? What a process that is...

- Repetition & context... experience, learning & applying what you know

- Times & seasons - everything in its time

- Small side note... when I don't know how to spell something, I will enter it into Microsoft Word & have it help me with spelling - I already had the words reinforce and recruit. I couldn't remember how to spell Israel - Like gather Israel, from the Bible

- Anyway, I right clicked on the word Israel to see if it had any synonyms - It said Zion as one of the synonyms - I then had: Reinforce, Recruit, Israel (Zion) - Wow, I had a fun spiritual experience - it was awesome & it hit me - I don't know the full meaning, but that hit me pretty good - kinda like a mini outline of the plan of God

- Recruit help from others - old power users, reps, consultants, clients, trainers, etc. - If needed, reach out individually to see what you get back.

- I'm loving the deeper connection(s) like pondering inspiration & revelation - for me, help others tap into that source or channel

- Help create the rich, context specific environments, and make it possible for others to pull from the source

- We are gathering

- We are gathering, even in our choice of models -

(drawing of two models with text)

Other systems - mashups & using a bunch of different systems to run your business

Adilas.biz - systemizing the application & bringing business functions together

- We are organizing

- We are learning

- We are being led

- I am so grateful!!!

- Little by little, line upon line, here a little, there a little

- Like Daniel & King Nebuchadnezzar (had to lookup that spelling), king of Babylon (or the world) - In Daniel chapter 2 - Daniel had to both show (reveal, uncover, expose, disclose, tell, show) the dream & interpret (understand, explain, clarify, read, decode) what it meant - both reveal & interpret

- Stone soup - Bring what you have got & throw it in the pot - We are making stone soup - mixing & blending different pieces together over time

- I sure enjoyed my learning & connection session - It meant a lot to me - Hours of rich connection & inspiration - I love it!

-----------------------------------------

The above is the end of the notes. A few days later, I took the original notes over to ChatGPT, I plugged them in and we had a small chat about where we are headed. If you want, this is a follow-up discussion that we had on 12/19/25 - https://chatgpt.com/share/69462819-9640-8007-9f14-948f203349b9

Small change to the developer's notebook pages. Made it so that the page number gets passed along for pagination (if there are multiple pages per query). Made the change and pushed up new code for testing. Switched over to more planning and grabbing information off of post-it notes for my plan for training the AI agent or agents (plural). Great little session. Thoughts and inspiration were just coming to me. I loved it. See notes on element of time # 12527 for details.

Went over to Heather's parent's house. A construction company was fixing the road by our house. We didn't have any electricity. I brought my laptop, a bunch of old post-it notes, and a notebook. Spent some time going over my notes and transposing them from post-it notes to a physical notebook. I'm kinda glad to slow down for a bit. Rewriting the notes, it is helping me really internalize them, meaning my notes. I want this to work vs just a quick fix for the AI training.

Quick phone call with Josh to touch base on the training and where things are going.

Doing some planning on setting up a new database table to get and hold the AI global context. Brainstorming and light research.

Coding the help files to use the centralized global content database vs the individual databases per server for help files. Pushed up and merged in the new code.

Meeting with Russell and Abby. We started out and Abby did a show and tell on both vectors and photo editing (some of the things she is working on). Then Russell was showing her some cool links and some samples. Here are some notes from Russell:

- Keep practicing and challenge yourself.

- Take your challenge and then look-up how to fix it and how to improve.

- Russell was showing us how he gets inspired and how he goes in and grabs pictures, graphics, websites, animations, and then makes all kinds of collections and such.

- Fighting towards the goal.

- Helping people see your best work - when they see it, they say - okay, you're hired.

- Go find inspiration, energy, and emotions and then build or create it.

- Selling people off of the sizzle.

- Taking something that you like and molding it into something else.

- Keep getting better at things. Build lots of things.

- Inspiration helps you go beyond your own boundaries.

- Talking about styles and being consistent.

- There was some great advice for Abby and myself. Keep going... you are smashing it.

- Transitioning from design work into code work. Good path and good stuff.

Meeting with Greg from the Calder Group. We did some catching up, chatting, and shooting the bull. We then talked about some of the new happenings inside of adilas. Greg wanted to hear a little bit about our story... we had fun going back and forth. Greg did a bunch of accounting in school. We chatted about that and how things have changed and progressed over time. I also briefly talked about some history inside of adilas and how things grew and became to be. I sent him the link for the adilas lite (fracture) master plan. Good meeting.

Created a new help files table on a global context database. This should help with updates and making one standard place for AI training and content. Sent an email out to the guys who need to know.

Quick phone call with Steve. He is going to try to use Grok to do an AI agent. We are just experimenting. Working on new global context table inside of adilas to help with AI global context stuff.

Quick meeting with the Nxtlinq guys. They were showing us a new compare feature in the backend dashboard. That should help. They wanted some feedback but I have been working more with the main ChatGPT vs the mini private model. It takes time.

AI training inside of adilas. I was testing it, trying to see what it would retain and giving it some new information. I also logged into the backend and uploaded two PDF files. See chat session 9 (see attached).

On a GoToMeeting with Steve. He had a small question about some new settings. We did some debugging and got it working for him. He is working with a client that is using an ATM and then paying for invoices and giving change due back to the user. It's a special payment option from inside the cart. Basically, a new button, if turned on, that allows you see the invoice total and then a series of buttons in increments of $5 up to $250. The change due is calculated and the invoice is stamped with the correct information.

Steve and I also spent some time talking about AI training and using ChatGPT to help train the mini model.

Back working with ChatGPT on some training and PDF creation stuff. It is helping me create documentation for quick searches and special keywords and prompts. Working on inventory and operations functions like purchase orders, parts and general inventory, stock/units, recipe/builds, etc.

Working with Bryan to look at some future development for a school that tracks native american students and some of their goals and progress. Going over plans and talking about ways to setup the one-to-many relationships that they need. We briefly went over some document management (custom documents and assignments) and connecting to custom paperwork options. We also talked about stepping away from the computer to do some planning. Sometimes that really helps. Otherwise, you get distracted.

Working with Shannon. Showing her the progress with the AI agent training. Then jumping into new changes like the add bulk po line items. She wanted to see some of the new features and such. We then switched over and worked on more content for the adilas lite or fracture buildout. We are getting close. We only have one more major section on the fracture page to finish up our first-round planning for that page. Today we finished up the lessons learned, the life cycles and maintenance section, and started working on the white labeling section of the plan. See the fracture page in the adilas section for details.

Emailing the team about the new functions for bulk adding PO line items (mini reverse shopping cart functionality). Small email to Wayne about a possible global database for helping to train the AI agent. I would like his opinion and thoughts. Spent the rest of the time working on a training plan to help train the adilas AI agent. Spent time working with ChatGPT to make a plan and start rolling it out. Towards the end of the session, I was having ChatGPT help me generate some PDF's to help with some of the adilas quick search functions.

As a reference, here is the share link for the AI training session that I was having. Some good stuff there. Light elevator pitch, a few small PDF files, some help files, and making plans. https://chatgpt.com/share/69377fb0-4594-8007-81af-a48edbc72690

Emails and paying bills.

Finished up the add bulk po line items logic. Merged the new code into master. Hopefully this new feature will help. It is kinda like a mini reverse shopping cart and allows for multiple line items to be added to a PO at a single time. You can also sub filter the items/parts and only the ones that get a valid quantity will be added to the current PO. We have wanted this feature for a long time coming.

On the GoToMeeting session with Abby. We were working on graphics and doing some practice. We started out doing some vector graphic stuff and then moved over to photo editing and making combination images or composite images from multiple sources. Little bit of mixing and blending. After Abby jumped off, I merged in some code for Bryan. Small bug fix.

Working with Bryan to fix some bugs on his local box for flex attributes. Once we got that fixed, he went in and made a small edit to the advanced invoice search with flex attributes.

Working on the add bulk PO line items project. This is a sub portion or part of the partial PO project. Working on the action page to help actually do the bulk add. Mostly working on validation and prep loops.

Working with Steve and Cory on some harvesting and production stuff. Small changes on some pages. We also had to go in and remove some older pagination stuff for one of the processing pages. It was stuck on the older version and couldn't handle numbers above 2,000 plants at a time. The new code allows for whatever number is needed. After we finished, we briefly spoke about possible other options to queue up bigger batches to help ease the page and server load.

Paying bills and recording notes from yesterday (12/4/25).

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

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

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

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

Working with Shannon. We spent the whole time working on the fracture plan about lessons learned from doing 20+ years of work on this project. Shannon and I were drawing a bunch, going over concepts, and brainstorming on what we want things to look like. After our meeting, I did a little bit of research and read some of the other content that we have been working on. On the lessons learned section, we didn't quite finish up, but this is what we were coming up with... content to this point.

One of our most encouraging lessons is that we are successfully creating an application that we've dreamed up and worked for. It is totally possible. We are systemizing business functions into an integrated platform that other companies have been separating into multiple different applications. We have been doing this on a garage budget, with limited resources, for 20+ years.

We have built up this application by prototyping features and functions to meet various needs. Many of these needs and wants have come directly from client input and requests. To summarize what we mean by prototyping, our process starts by determining a want or a need. Then we do research and brainstorming and figure out the plan. This could include trying to use new techniques or doing things that would further the product along. Where possible, we tend towards permissions, settings, and templates. Then we build it out and let others use it. They beat it up, and we make any revisions that are needed. Once it is being used and our clients are loving it, they often let us know what they want for the next steps. This pattern has occurred over and over again. This prototyping process has allowed us to build out the entire adilas application over the years. The result of this is a robust, revenue producing, and versatile system that is meeting the needs of our clients.

Our approach going forward is to continue following this pattern. If we do receive more funding, we will adjust our approach accordingly. This may include building out a more detailed master plan, using teams, hiring specialists, and other development techniques. If no additional funds are available, we will keep dreaming up new ideas, doing research, experimenting, prototyping, building, and moving on. This is what we do! If you want to see an overarching view of our master plan, please see the value add-on core section.

With 20+ years of experience, there is no way that we could fully put into words all of the lessons learned. However, we have documented the whole process through a section that we call the "developer's notebook". This notebook has been a running log of ideas, concepts, lessons learned, and other notes that we have collected over the years. It has been a great resource for us to refer back to as we continue to build and improve adilas. Just as a sample, if you go to that page and type in the word "fracture", you will see a number of notes and ideas that we have collected over the years that relate to this new buildout. There are over 200+ entries just on that subject alone. If you want to checkout the developer's notebook, you can find it here: Developer's Notebook by month and year or search the developer's notebook by any subject, use this link and associated form.

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

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

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

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

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

Working with Shannon. Going over new changes. Looking around in the Nxtlinq backend application (AI agent backend dashboard). It looks like we can edit things and upload documents now. That will be awesome. I haven't played with it yet, but good to see progress. That should help us with training it and helping certain pieces of global context to stick and be available to all users.

Shannon and I then went into our work on the fracture (adilas lite) plan. We were working on the section about lessons learned over time. We are wanting to show that we have listened to clients, done tons of prototyping, and are actively building out the master plan. We have captured tons of this process in the developer's notebook and are excited to really put the whole master plan together and go from there. We truly have experimented and prototyped numerous pieces of what we plan on doing for the whole fracture project. That is super cool.

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

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

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

These are just some ideas to help with the AI agent training that we need to do.

- Use ChatGPT to help with the training

- Ask it questions about what might be missing - ask it to ask me about that? (Helping us to find what might be missing)

- Use it to train other AI engines and models

- I'm thinking about a general layout and organization structure (for a master adilas document) similar to the adilas presentation gallery. Help that go even deeper and deeper to show the different parts and pieces. That would include business functions, application player groups, desired outcomes (coming - currently called attributes but we want to redo that section and rename it to desired outcomes), and core concepts.

- See what it can pick up by crawling the site. Then help to feed it specific information and help put things into context and additional details.

- Take your time, not too much info at once, and then pause to make sure that we are good to go. The pause is important.

- I would love to do some of the training in levels... intro, beginner, intermediate, advanced, and deep or expert level training. That would be really cool!

- We are on purpose a general business tool, help the AI agents know and understand that.

- Fill in the gaps, let it do what it knows how to do.

- On help files (existing files), re-read them and make sure that they can be used as standalone pages. Add a small mini blurb or description at the top. Don't assume that people know what each help file is for... They may get to it from a different source vs naturally navigating to that page based on normal page flow or business processes.

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

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

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