Earlier in the day, emails and helping Steve with some domain names and routing stuff. Sent an email off to Wayne, requesting some new domain and sub domain routing for the new website. Then later on, recording notes from the past couple of days.

Working with Hamid. We spent the whole time working on our CSS mock-up page (practice session). We ended up getting some help from the AI inside of VS Code. We were close, just missing a few small parameters and values. All part of learning. Good work session.

Putting together a small budget and capitalization plan. Had ChatGPT help me put it together into a small sharable document (4-pages) to show some rough budgets. Went into the system and saved some new year to date P&L and balance sheet documents for adilas. Did some other gathering and small details about banks, current payables, current receivables, long-term payables, etc. More of the story behind the numbers stuff. Sent out some numbers and such to a banker friend. See attached for a couple of files.

I got a link from Steve to show the new adilas website that he and Josh have been working on - Web link - new adilas site - As a note, I will also upload a multi-page PDF document with some screenshots of the new website.

Emails and responding to requests. Went and read a website about an entrepreneur who was asking some questions about adilas. Jumped back into working with ChatGPT on budget and capitalization plan.

Went into Bridgerland to be part of a discussion on the use of AI in software development. We also talked about how BTech students can leverage their knowledge and skills in a changing world. Part of a board or committee meeting for the software development department. Good group discussion and interesting to hear from other vendors and employers in the valley.

Recording notes and then working on some budget stuff. Rereading a prior ChatGPT session (web link) chat on budgeting and capitalization planning. I was pulling out pieces that I liked or that had meaning to me. Prepping for a more simplified capital plan. See attached for some of my highlights from the bigger chat session.

Reviewing some new adilasAI (adilas AI) videos on YouTube. They were done by Andrew. I watched a couple of them a few times. Emails and other research. Here is the link to the videos on YouTube (Web link to YouTube). As a side note, they looked good on the phone but a little bit grainy from my laptop (size and quality). Regardless, they looked good.

Emails and recording notes. Spent a little bit of time cleaning up post-it notes, getting organized, and light review of where we are heading. Working on a small budget, connecting files, and developer's notebook entries, and then back to more email stuff.

Working with ChatGPT to get the entries from 2009 finished up. I had left off with October 2009. I was partway through that month and had to stop. Picking it back up to finish a few things and provide some clarification and context. I then finished up the rest of the 2009 historical records.

Historical overviews for 2009 - chat links with ChatGPT to create monthly summaries:

- January 2009
- February 2009
- March 2009
- April 2009
- May 2009
- June 2009
- July 2009
- August 2009
- September 2009
- October 2009
- November 2009
- December 2009

- Annual Summary for 2009

Emails and recording notes from the past couple of days. Spent some time expanding some of my notes and adding screenshots to elements of time # 13134. This has some notes from a phone call between Steve and I. The new screenshots are for a theme called APEX by adilas. I added 21 screenshots to that element of time.

After that, I did a small session with ChatGPT about the Intel chip inside concept. Basically, how do we want to sell adilas and what role do we play in the bigger picture. Ideally, we would like to be somewhat behind the scenes and be the Intel chip inside of the application. Let the other companies sell and brand things like they want to. We just want to be the processing and the backend data engine.

Here is the chat session link: Good stuff - https://chatgpt.com/share/6add5193-4ebc-83e8-b779-ba14e25c9118

Just for fun, here are some small branding sections from the new APEX by adilas website. I thought that they were pretty good. Just a small sample:

- A new way to run your business. Sales, inventory, customers, accounting, all in one native system. Backed by twenty years of adilas experience.

- Everything you need. Already connected. A great sale is just the beginning. Make checkout feel effortless. Keep the customer, the inventory, and the numbers connected long after the receipt prints.

- Make every customer feel like a regular. A simple online order, a timely message, a reward that brings them back. Create a connected experience that keeps your business in the conversation.

- See what matters. Know where to go. Get your locations, your numbers, and your next decisions into focus. Start with connected business data. Build toward useful, accountable AI guidance.

- Your kind of business. Your way of working. Start with the workflows that matter to your team. Connect more of the business as you grow.

- Your kind of business. Your way of working. Start with the work you do. Shape the platform around the people, locations, and details that make your business yours.

- Dream it up. We'll wire it up. Your process. Your terminology. Your next big idea. Start with a connected platform, then shape the interfaces, reports, and workflows around the way your actually operate.

- A few things you might be wondering. FAQ's - Is APEX a point-of-sale system? Can I manage more than one location? Do I need to replace everything at once? What does the platform cost? Is AI Auto Pilot available today?

- One business. Everything connected. Your sales, inventory, customers, people, and accounting belong in the same conversation. APEX brings fresh experience to the connected adilas foundation.

- Follow the work. Keep the context. Every sale has a bigger story. Know what's moving. Give your team a place to work. See behind the numbers. Keep the relationship going. The detail and the whole picture.

- Connected records. Useful context. The foundation keeps the relationships between everyday transactions intact, so your team can follow the work instead of rebuilding the story.

- Connect the office and the online customer. Keep the rush moving. Every channel. One operation. Go beyond the storefront. Follow what you make. Give the job a connected home.

- Custom solutions - Dream it up. We'll wire it up. Your business doesn't fit in a box. Your software shouldn't either. Start with the connected core, then shape the details around the work.

- Start small. Make it useful. Bring a current form, spreadsheet, report, or repetitive process. We'll review configuration first and identity where custom adds value. Build around a real need.

- AI & insights - Less busywork. More possibility. Connected records make useful assistance possible. Explore the direction for easier receiving, clearer navigation, and evidence-backed next steps.

- People stay in control. Show the work behind the answer. Respect the environment. Make the next step deliberate. See your work in APEX.

- A clear scope. A useful starting point. Platform - Your operating environment. Implementation - Get the team ready. Specialized needs - Scope the work that yours. Build your conversation outline.

- Login - A new way to run your business. Everything you need. Already connected. Real-Time insights. All-in-one management. Build for growth.

- Let's connect - Bring your ideas. Let's find the possibilities. Show us your everyday work. Bring a better way of working. Find your next answer.

- Resources - A world of knowledge. Within reach. Explore the feature library, learning resources, support, and documentation behind the platform.

- The APEX story - A new experience. A proven foundation. APEX brings a modern way of working to the depth of adilas. Fresh interfaces and focused workflows, backed by two decades of real business operations.

Signing documents and uploading signed documents into adilas. Changed percentage ownership and uploaded all documents that were needed. Put Andrew in as a 1% owner in adilas.

First thing in the morning, helping Cory with a client data request. Small update to a purchase order on the data 9 server. Then reviewing a 12-page document from Steve with updates on what he has been working on. See attached for that document.

Later in the day, Steve and I jumped on an hour-long phone call. I took a bunch of notes and was browsing around on some of his changes as we were talking. Here is what I recorded.

- APEX by adilas site - Steve and Josh are working on a new theme for adilas called APEX. The by adilas is a sub note and light mini branding. The main thing that they are starting to work on is the APEX skin and theme. Adilas is just the backend platform or engine behind the whole thing. That is awesome. This is where we are wanting to head. Kinda like the Intel chip inside of a computer, adilas as the backend engine for any interface. See attached for a couple of screenshots.

- Currently, we have three major themes, with a few small sub themes. They are classic, snow owl (snowowl), and APEX by adilas. Each one has served a purpose and has people (clients and users) who like each theme for different reasons. The APEX by adilas theme is the newest one, just being released to the public within the last couple of months. As a note, when I first saw the new theme, I wasn't very impressed. It was kinda all over the place. I was much more impressed while browsing around while Steve and I were on the phone. I went into a play site and was playing around. I will try to do a better review and send them some ideas. It really is coming along. I was impressed. Lots of potential.

- I mentioned to Steve that Wayne has been making a number of fixes and has been going over some of his system error logs. Along with that, Steve was saying that maybe we need to point AI towards the error logs so that it can see what is going on.

- As we were talking, Steve was telling me about certain things that they are updating and changing. Instead of being fully done, it is more like a mini construction zone and enter at your own risk. That's part of his style. For the most part, this works fine. Only certain people and clients even know about the virtual construction zones inside of the site. He is trying to keep the main paths clean and clear.

- We started talking about play sites and demos. He is using AI to go in and populate some of the demo sites and play sites. Creative.

- There is some new stuff out in the balance sheet area. Apparently, Mike Roundtree, really wanted Steve to work on some GL stuff (general ledger or balance sheet stuff). I haven't had a chance to go in and look at it yet.

- Steve helped AI build in an automated scheduler. We have done this in the past, but it has mostly been from the server (actual box) level. This is a frontend scheduler for AI type tasks. I'm not sure how deep it is, but there could be some great potential there as well.

- We covered this earlier, but it seemed to be on Steve's mind... We switched over to AI agents updating play sites and demos. He has a small list of tasks to go through and they simulate a real user, doing certain tasks and what not based on a list of things to do.

- Light talks about testing and watching it go as it tests (semi live ish)

- AI is removing clicks from processes.

- This was sort of interesting, but Steve was talking about using your own AI, whatever model you use, and tying it to the product. Almost another virtual assistant and/or seat inside the system. I'm not sure how deep this is yet, but I can see how if someone has direction access to their own AI, that would help with context, training, and making things more specific.

- Josh and Steve are working with an insurance agency. Along with this, Josh has been mocking things up using AI and then Steve helps to wire them up. Seriously, approaching the you dream it up, we'll help you wire it up level of coding. That is really cool.

- Tons of new dashboards done by Josh. He has even been building websites and such for clients. Along with that, Steve was telling me that inside of adilas, we now have a number of client website settings. Not a real hosting environment, but a mini virtual hosting environment for each client, if they want it.

- This is for me... go in and look at the play sites - go in and look around... there is tons of cools stuff. I was having fun navigating and browsing around inside a couple of the sites.

- Breaking eggs to make some omelets - sometimes you have to break things to really get it to work how you want it to. We talked about limits and calculated decisions, but sometime, you have to kinda push it to the breaking point to see where the next fix and/or piece goes.

- I was exploring for a bit. I saw a bunch of new payroll stuff.

- Cory is getting good at making fixes. She has been helping with tech support and project management/coordination for years. If the changes are small, Steve has her setup to help make changes and then Steve merges them in. Very interesting.

- I have seen this with my work... When I was first starting, Steve allowed me to make some mistakes and take on things that were bigger than I was ready for. That really helped my skills and also knowing when we take it too far. You have to find that edge.

- Talking about different AI models and versions - paying and feeding it tokens - Codex and Claude. Other LLM models as well. Lots of options and choices. Figuring out which ones do best at what task and/or assignment.

- One thing that we still need is getting eyes on the different pages. This is a form of hardening and making sure that things are working (user tests and user testing).

- Steve wants me to check out the public facing website options (new settings). He was mentioning a thing called themeskin (new website themes). I'll have to check it out.

- Crossing AI's (between people) - sharing and collaborating - use technology.

- Talking about security

- Reworking old projects, even things that we only partially finished (like create your own screen or interface). Steve, Josh, and Cory are circling back around to projects that were partially done and having AI look into them and finish them up (to a point). Interesting. As a side note, Steve was saying, remember when we had Cody work on that section for creating your own interface, we jumped back in there and had AI finish some of that up for us. Very creative.

- Steve kept saying, we are trying to use the system and AI to fulfil our general mission statement of helping the company succeed.

- Even sending the AI back into our older stuff.

- Steve's style is to try things and be willing to circle back around - 1st thing... fly the plane - deal with the current (right in front of you) and then worry about the other stuff as you can.

- Talking about meeting with Cory. Steve said that he used to meet with Cory for hours a week, to go over projects and such. She would gather it all up and basically transfer it over to Steve or whoever to work on. Now she is doing some of those small things. She is picking and choosing. The time in meetings has been cut down considerably.

- As I was talking with Steve and browsing around, I told Steve that I think that he is doing great. I am going to stay out of his (their - Steve, Josh, Cory, Andrew, Sean, and Eric's) way. I'm going to keep doing the things that I am doing. Those others are doing a great job and it is looking better and better all the time. Knocking the corners off of the roughly rolling ball.

Meeting with Hamid. Going over CSS layouts and doing a small practice session on a dashboard mock-up. We had a small simple image and were trying to build it, our page, to match the graphic. Basically, a joint practice session of sorts. Good stuff!

Emails and checking some files. We got a report of a couple small bugs and misspellings. Running local database updates. Checking on the data 0 server box. It was up and down a couple of times.

Recording notes from yesterday. Switched over to work more with ChatGPT on the adilas history stuff from back in 2009. Lots of fascinating pieces, projects, and history. This whole project has been an amazing story. Got into some deeper discussions on corp-wide settings, up to five levels of decimal accuracy, image galleries for main items, and seeds for ecommerce. I will share the links as soon as I finish up the 2009 year. I am currently partway through October 2009.

Working with Russell. We started out and he was researching some possible web vulnerabilities for an application that he is working on. Then more work on the API's and how to use them. These are a new API framework that Russell is creating to eventually use with some adilas data. Somewhat of a mixed project of adilas API's, PHP, Laravel, and a given database model. We are experimenting with what would this take. Working on creating a bunch of upfront rules and organization. This prep work helps the entire reset of the application get laid out correctly (structured).

Part way through the meeting, we were talking about AI and some of pros and cons. We were talking about Wayne (our server guy) and him being a janitor vs a developer or system architect. He is spending tons of time sweeping the floor, cleaning up other people's bugs. We may need to let the developer's see what it takes to do the cleanup. Sometimes that process is somewhat hidden. Maybe reach out to Wayne and see what he thinks. Maybe a solution like - even sending an email every day for a week, showing what is being cleaned up. Let the developers know.

We flipped over to making changes and then submitting those changes to AI to make sure that things were tight (back on the API framework project). It was helping us be consistent, making suggestions, etc. Good workflow. We would then take the new changes and/or alterations and make it into something official.

Talking with Russell about the value of learning things from scratch. The learning itself has a value. The value comes because, I, have trained myself to recognize good and bad. That is really important. Question from Russell... how do you know the difference between a real dollar bill and a fake dollar bill? You know, if you have spent time with the real dollar bill (time and experience).

Emails and responding to some investor related questions such as cash runway, spend budgets, pre and post valuation values, etc. More work with ChatGPT and doing overviews and breakdowns of adilas history from the developer's notebook for 2009.

Here is a small sample of some of the content we are generating (between ChatGPT and I):

Historical Context - Building Towards the Dream and Flying the Plane

May 2009 illustrates two complementary philosophies shaping early Adilas development. The Flex Grid began as a practical need to extend relationships involving purchase orders and invoices. Before implementation began, however, the concept expanded into a much larger 10 × 10 × 10 architectural vision.

This reflected a recurring approach the developers called "build towards the dream." The team was willing to explore, learn, and design for possibilities years into the future, frequently without knowing the full development costs or eventual complexity.

At the same time, Steve Berkenkotter emphasized a practical principle drawn from his experience as a pilot: "Fly the plane!" The immediate priority was to keep the business functioning, serve paying customers, and concentrate on functionality over appearance while continuing to build toward larger possibilities.

The May 21 presentation was an early internal Adilas demonstration, attended primarily by members of the Morning Star Automotive team. It occurred during a period of severe economic pressure that would eventually contribute to Morning Star's partial bankruptcy around 2010. Adilas, originally developed to serve that business, would become one of the surviving assets.

Together, these events capture the tension between ambitious software development, immediate business survival, and the uncertain future of the company.

Just for fun, here is the full chat link to that May 2009 chat session - Web link - https://chatgpt.com/share/6ada59fa-1ffc-83e8-b485-5ea46670fa20

More good stuff to come.

Recording notes and pushing up older assets into the adilas data treasure room. See link below. I also spent a bunch of time working with ChatGPT on some adilas history breakdowns and reviews. We did January through March 2009. I will add the links, once I finish the rest of the year.

Here is the link to the adilas data treasure room - I added in a bunch of older recorded meetings (new videos). Web link - Google Drive

Working on historical documents from back in 2008 for adilas history background. Lots of data from the adilas developer's notebook. As a note, 2008 was the year that Adilas, LLC - adilas.biz was established. Multiple sessions throughout the day working on the history project.

Historical overviews for 2008 - chat links with ChatGPT to create monthly summaries:

- January 2008
- February 2008
- March 2008
- April 2008
- May 2008
- June 2008
- July 2008
- August 2008
- September 2008
- October 2008
- November 2008
- December 2008

- Annual Summary for 2008

Creating a data treasure room. A common data room is a place where strategic documents may be found for investors and such. I have a bucket load of documents. My plan is to create a data treasure room. Just for fun, as I was writing this little note, I misspelled treasure and put teaser room. They may be one in the same (teaser and treasure). Regardless, it will be a stockpile of data, videos, simple documents, marketing materials, graphics, public financials, Excel files, and other historical pieces. A treasure trove of data.

This is open and available to the public - the adilas data treasure room - Web link - on Google Drive

Recording notes from 10/7/26 to 10/16/26. I got behind a bit. Trying to do some catch up. This is a terrible joke but - Oh, you are being a hotdog, you must work hard to catch up (say it kinda fast and it sounds like mustard and ketchup).

Emails and follow-ups. Sending some documents out for signing. Reading documents passed to me from Steve, AI plans, and a growth advisory contract. After reading the growth advisory document, I replied to the party stating that the timing wasn't quite right. Not that we don't need the help, but the cost and timing are off currently.

Quick meeting with Hamid at 5 pm. We jumped on the GoToMeeting session and then I had to go pick up my daughter. We met briefly and we will hit it again next week. I showed him a few things that I was working on. We chatted for a bit. Very short.

Reworking some documents for Andrew. Got them ready and sent them over to Steve for review.

Went into town to meet with Matt at the food bank. Somewhat of a short meeting, but we went over the progress that I am working on. I showed him what I have done, on my local box or instance. He was happy with the progress, and I told him that I will keep going. I will reach out when I have more to show him.

Meeting with Wayne and Steve. We were talking about some upcoming interface and application changes. Lot of talk about using AI to change things. There are some pros and cons. Here are some of my notes:

- We are burning through tokens.

- Skills and teaching the AI what we really want (rules and processes). We are seeing some problems with consistency and some other issues.

- AI's default fix is to put a guard around it (if exists, do this, if not, do this).

- No real way to test our code.

- AI is taking our code and creating different versions of key features. Multiple implementations for the same thing (ish). We would love it to use our existing processes.

- Making consistent changes - that's what we are wanting. Slight wandering and varying of the code source.

- Back to testing and setting up testing accounts. We are starting to get into automating some of that. Still needs some help.

- Steve is heavy into AI and that is how he is coding everything.

- He is loading in things to the demo sites. Eventually, he would even like AI doing demos, AI doing payroll updates, etc.

- Cory is doing a little bit of backend code stuff. She gets the call from the customer and then she makes the fixes using AI.

- Wayne wants to make the AI more productive and more standardized.

- We have pages and functionality expanding at a crazy rate. We are also multiplying possible problems. Being able to manage all of the different possible configuration options.

- Making customers mad over time due to so many changes.

- Test driven design skills - templates and how to apply them over time. Helping to remove the need to look for AI context. Send it to a specific template and then let it run, based on those templates. Build in the patterns and context.

- Talking about "View Objects" and splitting things into MVC (model, view, controller) stuff. Separating the layers - the business logic, the view layer, etc.

- Wayne is working on some workbench stuff - adding in fixtures and scenarios to run against certain pages. Being able to switch themes. The view object becomes the record of truth. Checking the visual impact of the different changes. Converting some of our older pages into testable views. Trying to bring it (all of adilas) under test, without making major changes.

- Pushing all of the data into a valid view object.

- Setting up new pages that follow our new rules, processes, with view objects that are testable.

- Focusing on the main traffic - pages that get tons of views and traffic - like view cart, etc. Wayne wants us to pick some pages and go slow, vs just telling AI to run with it. Trying to get some consistency up and going.

- Everybody is working on work in progress stuff. Be patient. We may be giving AI too much access and authority.

- Being able to really translate the background meaning of things (intent, assumptions, and overarching context). Coordinating all of the moving pieces.

- If we want to customize things, help make it fast, powerful, and stable. Custom is part of our model.

- Wayne spends lots of time fixing new AI code and missing variables (he said 75% of time over the past few months). It works great but we need those guardrails. He is on a different time zone then we are... New things will launch for us over night. It is morning time for him and his error logs start going off. He ends up changing and fixing things before everyone else comes to work. It is almost turning into his daily process. AI is super fast, but we may be introducing errors and bugs even faster. I'm so grateful that Wayne has some logging and error monitoring tools in place. That is huge.

Got up early to get some custom code started. Had to run a number of new database updates on my local box to get it up to speed and working. Steve, Wayne, and Eric have been using AI to add new functionality to the system.

I then switched over and was working on the food pantry stuff. Setting up a new corporation in the system. Sent off a quick email to Shari O. to see what server she would like them to be on. Started working on my local box to help with some new custom homepages and mini header versions, in order to create a super simple interface. Going through settings and permissions and tweaking things out for this specific use case. Pretty good session and making progress. Starting to work on new homepages with simple custom layouts.

Working with Russell. We were looking at some PHP documentation. Russell was working on an automatic API based off of the database, model (database tables), and classes. He would like to build out a mini adilas app using API sockets, PHP, and raw vanilla JavaScript, CSS, and HTML. He is better at PHP then Adobe ColdFusion. Thus, the switch to PHP, while working with Russell. If we use the adilas API, it won't matter what backend we are using.

Spent the whole rest of the session working on new adilas changes for the dev docs project. Basically, Russell turned over the code to me to start working on it. We made some logo changes and started going through things. It will still take some time, but the main app (as an outline structure) is fully ready. We had AI help us convert a current webpage into new content for the dev docs project. We are still just experimenting with things. It is going to be cool!

Working on some documents for Andrew. I ran some of them through ChatGPT to get some help. I had a bunch of old documents but I needed to tweak them and update them a bit.

Working on some new documents for Andrew Brandt and Brandt OnPoint, LLC. Steve has been working with Andrew on some sales and marketing ideas. The new documents are dealing with percentage ownership in adilas, llc and a hybrid non-compete and non-discloser agreement.

Meeting with Fred from Zaidwood Capital. Quick touch base. They will be sending over a proposal for a possible growth advisory type deal. We'll look at it and see what happens. Nothing has been decided at this point.

Recording notes from last week. Emails and text messages with Steve and a potential client.

Reading a document and agreement with Andrew Brandt about sales and marketing in exchange for some equity options for adilas. I then jumped on a phone call with Steve. We talked about the agreement with Andrew, what he will be doing, and some timing on things. He then let me know about some new leads from Josh and possibly working with an insurance company. Things are constantly changing. We briefly talked about custom buildouts, using AI for some of the coding - on top of what we already have (expanding the platform), and how to structure ongoing maintenance and service fees (basically a commission percentage based off of the full buildout).

We then talked more about the meeting with Wayne and Steve, going over servers, databases and such. That happened last Friday. We are planning to meet more about those subjects later this week. Lastly, we talked about setting up custom code rates, using AI, and then paying commissions and/or birddog fees for guys who bring in the custom work. Steve is trying to just do work for companies that are willing to pay. We have done a lot of free work, over and over again. Hopefully we are learning from lessons in the past. Over the last couple of years, we have had some big fish and big lessons. Big fish play different than littler fish. There are pros and cons.

Recording notes from 10/6/26. On that day, I was doing lots of brainstorming and working with ChatGPT.

Prep work for helping Steve with a plan for some database stuff. Spent hours working on a voice dictation. Originally, it was going to be small, but it sort of grew. It ended up being an 8-page voice dictation with 20+ items on it. I then sent him and email with some supporting documents. This was all dealing with the bus to motorcycle or datasource project. Lots of moving pieces.

For security reasons, I will not be posting the file here. I do have a copy on my computer with the name of "for_steve_bus_to_motorcycle_datasource_project.docx".

Online meeting with Fred and Yimin. They gave me a small rundown of what they would like to do. They are proposing a 90-day growth advisory type relationship. We haven't decided on this yet, but they are going to send me over some information. Towards the end, they were asking me some financial numbers, and I asked if I could just show them. I jumped into adilas and navigated around a bit. That was kinda fun. Hopefully I wasn't showing off too much (click, click, flip, flip, drill-down, new tab, click, click, etc.). I had fun. Here are some of my notes from the meeting.

- Fred did most of the talking on this meeting.

- They would like to look at options for doing a growth advisory type relationship. We talked about what that would look like.

- They were talking about delusion based on the valuation of the company. How things get spread out.

- They try to send their pitches out to 3 different tiers - people who they know and/or pitch to. Each is at a different level... friends and family, semi acquainted to, and more strict business entities and funding parties. Most of those parties and/or people are one and done. If you pitch something, that is your chance. They don't let you keep refining your plans.

- We talked about key employees, key roles, and having too many clients from a single industry. Those are all possible risks and/or potential problems. Basically, warning signs.

- Investors want to see a growth engine - running on full steam.

- Looking at what we could do in 90-days - growing a sales team - viable leadership team - and increasing the inbound pipeline.

- We talked about a couple of pillars - 1. Organization - talent assessment, score cards, and weekly meetings. 2. Sales funnel - play books, compensation, marketing, etc. 3. Operational - SOP's, packaged offerings, KPI's (key performance indicators), and financial reporting.

Finished reading some of the plans from Steve. Last night I had scribbled down some quick notes on post-it notes. I spent some time this morning planning and scribbling down some more notes for the datasource project (bus to motorcycle) on scratch paper. The post-it notes just couldn't handle everything that was needed.

Reading Steve's bus to motorcycle plan. Almost finished it. This was a multi page document that showed plans and phases to help with the adilas database and converting the bigger database into smaller pieces (bus to motorcycle). He was working with Claude (AI) to make the plan. Some of it was perfectly on point... Some of it really needed some background, guiderails, and some handholding. As I was reading it, I was scribbling down some notes on post-it notes. I wanted to make sure and chime in vs just letting it unfold or just play out.

Working with Russell. Looking at stats for our project. It was faster, using AI. We still spent just under 150 hours, but it would have taken us over 600, if we did it in a traditional style. That was good to see.

Russell was showing me some of the voice stuff with ChatGPT. He was using his phone and just chatting with the bot. He has even gone on walks and gives it tons of information. He then jumped on the computer, had it make him a markdown document, and we went over the markdown together.

From Russell, as we were talking... if you know more, your job may be to help others learn and lift them up.

Also from Russell - treat work as if you are employed by God, it helps you have the right outlook.

Looking at some classes and underlying API structure stuff. Some of this code is some stuff that Russell is or has been working on. He would like to use his API engine to do some adilas work. comparing older REST and context API stuff. For Russell's stuff, you just specify the model (database table) and then the system self generates the underlying API based on that model. We spent some time going over some of his documentation and some samples. We were doing good, and then kinda got bogged down in some deep details and likes and dislikes. We ended up chatting about options as we were going through things.

- Sometimes, we make monsters... (our code or application blocks... huge, monsters, that have to be fed, and taken care of...)

- Doing tons with just the basics - it's okay to explore and experiment - as you experiment, you grow.

More AI historical records stuff. Started in June of 2007 through December 2007. See below for some links:

From ChatGPT - small sections pulled out during our conversations:

- Keep them on the path - talking about guiderails, legends, and step-by-step wizards

- A major Steve thread to track - As we continue through the notebooks, I want to watch for this recurring pattern: Real-world event - operational process - transaction/record - relationships - accounting result - And when the evidence supports it, we should recognize Steve's role as teacher and translator, not merely as someone requesting accounting features. That may ultimately be one of his most important contributions to the architecture. He was helping translate accounting out of its traditional vocabulary and into business events and consequences that could actually be modeled in software. You, in turn, could translate those processes and relationships into databases, pages, permissions, workflows, reports, and code. That's a pretty powerful combination:

Steve: "When this happens in the real world, here's what it creates and what has to happen next."

Brandon/system: "Okay—how do we represent that relationship and make the software facilitate it?"

And then you would test it against actual users and actual business activity and repeat the cycle.

That also makes the later Adilas idea of operations leading to accounting, rather than treating accounting as a disconnected after-the-fact activity, feel much less like something that suddenly appeared years later. We're seeing the educational process that helped produce that worldview.

So yes - huge shoutout to Steve. When we eventually write the longer historical narrative, I don't want this reduced to "Steve knew accounting." The richer story is that Steve repeatedly taught accounting as real-world cause-and-effect, and those lessons were translated directly into the evolving system.

Historical overviews for 2007 - chat links with ChatGPT to create monthly summaries:

- January 2007
- February 2007
- March 2007
- April 2007
- May 2007
- June 2007
- July 2007
- August 2007
- September 2007
- October 2007
- November 2007
- December 2007

- Annual Summary for 2007

Documenting the developer's notebook with ChatGPT. Going month by month starting in 2006. I got all the way through 2006 and started into 2007. These are all historical records. Technically, adilas became an official company in 2008. We started the project clear back in 2001.

From ChatGPT:
What happened? - Was value/money coming in or going out? - What business object represents it? - What data belongs to that object? - How does it relate to other objects? - Who may act on it? - How is it verified? - How do we preserve its history?

Simplify a complicated business process into its fundamental players, actions, and relationships.

Here are some of the historical links for 2006. Once again, real work started clear back from 2001. This is just where I started based on records in the developer's notebook. All other earlier records are still in paper (pen/paper/notebook) format.

Historical overviews for 2006 - chat links with ChatGPT to create monthly summaries:

- January 2006
- February 2006
- March 2006
- April 2006
- May 2006
- June 2006
- July 2006
- August 2006
- September 2006
- October 2006
- November 2006
- December 2006

- Annual Summary for 2006

Recording some notes from this morning. Then looking into the adilas core concepts overview and world building document. Trying to envision how to explain all of these interconnected pieces and how they help with business world building or industry specific recipe mapping. These pieces are somewhat interconnected.

I reread a few entries in the developer's notebook. They are elements of time #'s 12999, 13045, and 13059.

Also, I scribbled down some notes on a post-it note for some reverse engineering ideas... start small, expand forever...

Here are some of those ideas (expanded):

- Make up some starting rules and guidelines for the independent rep model. Create a starting spot. They can be tweaked more later.

- Maybe a base salary plus commissions to start out with. We could even start it higher on the base portion while they are learning. Then, once they know what they are doing, taper that back and have them rely more on actual finder fees and commissions.

- For developers, we could do the same thing... as the independent rep model, but for our developers. Instead of commissions, we could flip it to project or hourly variables to help offset learning vs productive development stuff. There is always a learning curve. Help them get started and then lead them to paying work. As a note, if we charge $100/hour, we could split it with them based on their level of experience and expertise. Just for fun, I was thinking a max of 75% for them and 25% for the company. If we have a super star, it could even go up to a 90% (them) and 10% (retain for us or for adilas or adilas shop).

- We have done this stuff before - independent rep model stuff - what have we learned? This is not a blind experiment.

- For me, make a mini "me" budget - what do I owe and where would I go with funding (personally)? This just helps me look at needs and wants, but from my personal angle vs a company angle. I think this would be good for me to do.

- As I was reading the adilas core concepts document... There are 12 main concepts that I am trying to cover. If you boil that down (compress it), you could potentially make it into three interconnected concepts. Then the other main 12 concepts could be a sub of the main three. I was thinking about these... 1. Digital storytelling, 2. World building, and 3. Data assembly line. All of the other 12 main concepts could fit underneath those main concepts. Those ones sound more fun and might make a fun and general (yet deep and cool) introduction. I'm leaning in that direction.

- For everything... start at the highest level and then go deeper - start small, expand forever... - This could even be things like... Money coming in or money going out - accounting can be as simple as putting things in the right bucket or can (virtually create buckets for things). Then the accounting could be figured out after the fact. Everything has a lifecycle (states, statuses, phases, etc.). Help keep it simple. Explain operations and accounting without getting into anything technical, unless the user wants to keep going in deeper and deeper. As part of the this idea... I had drawn a triangle or pyramid type drawing. The top is super simple and it gets deeper and bigger as it goes down. Kinda like the iceberg analogy. Small top but mountains of functionality below.

Online meeting with Bill and Aston from Aizoh Capital. We chatted and they had a number of questions for me. They encouraged me to put together a small data room or at least put all of the needed documents in a place where you can get at them. They recommended, even a google drive, or some other shared folder. Really simple. I was expecting something more formal. As a fun side note, Bill provided me with a written list of what documents they are looking for. That will really help. (see attached).

Most of the conversation was between Bill and I. For this meeting, Aston didn't say much. Lots of questions about sales, revenue, plans, verticals, and team level capacity stuff. We briefly talked about an independent rep model and the pros and cons from that venture. This was our original sales model. It worked great but was somewhat hard to scale, due to a lack of set standards and expectations. I would love to bring it back, but have a plan for it and also some ownership and leadership, in order to really make it work well. As a comment on this independent model, this is now a number of times that people have seemed interested in this model and see potential, but we don't have the rules or regulations set yet. This could be promising.

Emails and doing some catch-up. Filled out a survey about AI usage and sent an email to the department lead at Bridgerland about AI usage in the workspace. Recording notes and hours from last week. Paying bills and recording expenses.

Recording notes from 10/1/26 to 10/3/26. Going through emails and checking on things. That doesn't ever seem to stop. All part of the game.

Looking over a balance sheet for a client. They were looking for a certain value that they were out of balance on. Small email with some notes, after I found what they were looking for. Recording notes from 9/28/26 to 9/30/26.

Meeting with Hamid. We spent the whole session working on some CSS and doing training and practice stuff. Sharpening some skills. We grabbed a graphic off of the Internet and were trying to make a sample app match the style and layout of the dashboard graphic. Fun meeting and training session.

General to do list items. Logging in and checking some of the new code for vendor credits. I bounced into two servers, clicked around, ran some reports, and edited an existing record to make sure that everything was working. Looks good. Sent an email update to Cory and Steve. I signed an NDA agreement. Spent some time reviewing the adilas core concepts brainstorming document on world building and how they (core concepts and world building) relate. I just felt prompted, that I needed to revisit that document. A number of my other projects are at least semi stable at this point. I'm heading in deeper on those world building concepts. See below for some good pieces (history leading into our discoveries of core concepts, world building, and industry recipe maps - all interconnected).

For me...

possible link - dev notebook - "core concepts" - 1/1/2026 to 10/1/2026 - heavy traffic and options from June to July of 2026.

possible link to eot # 12918 in the shop. good breakthroughs - geared for stories - video recorder - solving pain

possible link to eot # 12946 in the shop. more breakthroughs - MVP's, custom code, bridges

possible link to eot # 12999 in the shop. finding the connection between the core concepts and world building

possible link - dev notebook - "world building" - 1/1/2026 to 10/1/2026 - world building

possible link to eot # 12814 - mini version planning - api mini apps

possible link to eot # 12892 - how does AI play into world building - huge base or platform to run on

possible link to eot # 12904 - swot analysis - three level strategic direction - platform refinement, ecosystem growth, and world building

possible link to eot # 12917 - what makes us different

possible link to eot # 13015 - link between industry recipe maps and world building

Pushing some code live and running some updates. Phone call with Cory earlier in the day going over new code for the vendor credit - round 2 code and options. Ran an update script on all servers to flag the correct, existing records, for the new vendor credit flagging and offsets.

Work session with Russell. He was working on an AI generated portfolio. It is fun watching him work. In the background, we were running some checks on security for the documentation project. He wrote a small prompt, then gave that prompt to ChatGPT, it rewrote things and then he modified it slightly, and gave the new bigger or more complete prompt to his Claude agent inside of VS code. The new portfolio will be included inside of the documentation project (used as a base app for the new stuff).

We spent some time talking about a standalone adilas version. We were talking about the floating city analogy... it is all your ship... you decide and configure it on your own. Click to see a small info graphic on this concept of a floating city.

As we were talking, Russell was saying if you are big enough, you earn the right for a rewrite your code.

Reviewing a mutual NDA document. After that, switched over to more work on the round 2 for vendor credits. Working on passing through additional filters for data drill-downs from the P&L (income statement) for vendor credits. Finished up multiple versions so that new output and drill-downs show up where needed. Still need to work on the consolidated version.

Working with ChatGPT on some rough budgets and what not. Light prep work for a meeting with an investor bank. After the meeting, back working with ChatGPT on some rough budgets, values, and numbers. For me... it would be worth pulling some of this information out. Really good stuff.

Web link to the main chat session - Going over tons of numbers and budgets - No names, just positions and department stuff. https://chatgpt.com/share/6ac06eb9-e550-83e8-8cae-6d6d2990b9d4

This is just for fun, but we are working on a pitch for adilas to raise $2M+ for a commercialization round. This is a super small budget for a capital ladder - values above the $2M floor or minimum.

Online meeting with Yimin. We met for half an hour to go over some positives and possible risks for adilas. We started out with the positives. After that, we went over some possible risks. Here are some of my notes:

- We could do a pre or prep step - kinda like a growth advisory type thing. This is to help people get ready to be funded.

- We have grown a lot, just via word of mouth. That usually means that there is something good there.

- People or our clients are finding value in our product.

- Once they are in, they, our clients, seem to be more sticky (staying and wanting our services - sticky).

- Capital efficient - we do a lot with very little.

- There already seems to be some sort of referral channel - keep that going and expand it.

- Because we offer so much, it potentially helps us retain clients. This is dealing with the costs of switching to something else.

- The age of the company. This one is both a positive and a negative. One, we have been around a long time. In some ways, that helps say, wow, these guys are legit. In other ways, they are saying, why haven't you guys made tons of money? What's wrong? Anyways, Yimin was saying that the age of our company could be seen in two different lights.

- Moving on to some of the risks - based on what they are seeing...

- Concentration of clients in a single vertical. He was specifically speaking about cannabis. We are not cannabis specific. That is both good and bad. If that market goes away, that is bad. It is good and shows that we are filling a need. Goes both ways.

- Churn (clients coming and going - normal business cycles) - what if you lose some big clients? Then what? Just questions like that.

- Where is the revenue going? If you are making money, where is it going? I told him that we have been reinvesting it in bettering our system (development work and adding features and such).

- If we can show that we can turn on the faucet, it will show that we have value. This means, if we turn up the sales volume, will that make a difference?

- Lots of owners tend to be in this mentality... Build it and they will come - that doesn't always work. People need to find out about it.

- Pricing - where is that at? How to find a good balance.

- One of the main goals needs to be more MRR (monthly reoccurring revenue) and then keep it.

- Key person dependencies - we need to make sure that there is not a huge single person dependency. Spread out that load and knowledge. That could be a potential risk factor.

We then rolled into some other talks about opportunities and opportunity costs. Looking forward to future benchmarks and hitting certain milestones. All part of the game. What is the vision and the goals? Yimin wanted to know some of those answers. All in all, I would say a pretty good meeting. I can't tell you how many times, people have a number of questions, and yet they don't really want to spend the time to get the answers or dig in. They basically want it all served up nicely on a platter. That's just a whole other level. We have answers and reasons, but it currently takes time to explain and show people. That may be one of our problems. Well, we'll just keep kicking the ball down the road and see what happens.

Working on the round 2 of the vendor credit project. Getting back into it. I left off working through new queries and then showing that output on the P&L (income statement). Adding in some new filters for vendor credit drill-downs.

Phone call with Bryan going over ideas, possibilities, and possible options for selling shares of adilas. Trying to look at all of the options and possible paths. We talked about getting with Steve to see if he could show us what has been done for the delivery integrations and such. I know that we have our own delivery stuff, but we wanted to check on the other main commercial integrations like Grubhub and UberEATS, etc.

Reviewing some findings from Steve on a small plan for the database updates. Light research and then a quick email back to Steve.

Back working on the round 2 changes for the vendor credit project. Working on a global update to help with some older entries. Adding in a new vendor type flag to help me categorize vendor credits as cost of goods sold (product/inventory vendors) or normal expenses (service vendors). Working deep in the logic to pull out the vendor credits in one of two places. Either as a reverse cost of goods sold or as a reverse expense.

Working on the round 2 of the vendor credit project. Added a new vendor type flag to the manual entry vendor credits. This will help us categorize them and pull the correct values into the P&L (profit and loss or income statement). Working through the process and following different paths through the logic.

Recording notes from 9/22/26 to 9/24/26.

Online meeting with Yimin Dong from Zaidwood Capital out of Canada. I took a few notes but mostly listened and chatted during the meeting. Towards the end, the internet cut out. We finished up on the phone. Just as some follow-up notes, he was mentioning a timeline of 4-6 months to normally do a deal. One month doing due diligence. One month doing asset buildout stuff. He was also talking about one of the main things that investors want to see is the growth and repeatable sales channels. The other thing that we talked about were some benchmarks and how to measure where we are heading. All in all, I would say a good meeting.

Phone call with Steve. We had a little catch-up session. Talking about new projects, changes, etc. One of the topics was messages and customer notifications. Steve is somewhat pushing things towards the client direct messaging from the customer portal (ecommerce area). We were talking about some pros and cons of apps and app-based notifications. That is a lot cleaner, and the user gets to determine an opt in/out on their terms. Steve is seeing that texts and marketing texts are somewhat crossing the lines between personal and business.

He was reporting about some new changes that they have been working on for the icon touchpad buttons and menus. We then got into talking about digital menus and menu boards. Some clients only want them digitally, and some may want printable menu options.

We talked briefly about Cory doing some small code and fixes, using AI. Steve was talking about AI agentic coding and multiple models. He uses ChatGPT, Grok, Codex, and Claude. Probably some others as well, but that is the list that he gave me.

He is working with Josh and trying to get some things going for clients that Josh is bringing to him. They are working out some kind of split costing and almost an independent rep type model for custom code. They bill it out at a certain dollar value and then spit it.

Lastly, we talked about how the AI agents are breaking some of our code up into the black box level pages with tops, headers, body or main content, footers, etc. We were working on that stuff clear back in 2015/2016. He is now using AI to do some of that page break up stuff to gain the advantages of the black box code from back in the day. Interesting. They are working on new custom themes and presentation layers.

Right at the end of the call, I had to jump off to get on another meeting. It sounds like some good things are happening.

Meeting with Russell. We jumped into the documentation project. We are almost done with the main project. We still have to come up with the actual content, but the app/engine is almost done. He had made a few changes and it is looking good. Russell was making small changes to the highlight section of the document reader. As we were working, we were talking about working with AI, and how can I give it as little as possible but still have it complete the task well. While we were waiting, we worked on some small notes and planning for our next sample adilas project.

Emails and light research on the vendor credit - round 2 project. Phone call with Cory to go over the vendor credit stuff and how she wants to see it get booked. We logged into a client's site on data 4 to look how they had done it (booked the vendor credit). Part of this is already built into adilas. We are just working on the other part or hitting the correct COGS (cost of goods sold) or expense side of the equation. Light research online to see if I could get any simple explainations and directions. More reviewing, research, and running through a number of small sceanrios. Leaning towards adding in some database flags and letting the original vendor credit records play a stronger role in the financials.

Emails and follow-ups. Letter of recommendation for Cody Apedaile. He was one of our developers. Here is a small list of entries, where I worked with Cody - web link.

Emails and small general to do list items. Pushed up the adilas investment and commercialization overview document. Added a link to it from the adilas AI assets page. Signed up to meet with a banker next Tuesday. I'm hoping to get some other pieces in place before that meeting. Still just pushing the ball down the road. As a follow-up note, I got a call from the bankers and they were requesting a verbal yes/no on a high dollar commitment, should, they take the capital raise on. I had to say no. We are not that big.

Reviewing the investor packet that we made a couple of days ago. I read over a printed version. Looking at it with fresh eyes. Recording some notes from the other day. Flipped over to working on the vendor credit project - round 2. Reviewing some of my notes on the vendor credits. I reread the notes from 1/1/24 to 9/19/26 - See web link for notes dealing with vendor credits for that date range. As a summary, here are a few things that I found interesting.

- We may end up using the three special flex fields to store special expense/receipt numbers - create an offsetting entry

- For all of my main planning notes, see EOT # 2794 inside of adilas - older notes for vendor credits and partial PO project - original project was spread over 4 month (may/aug 2025) - getting pulled in so many directions

- Light research on watchers and feeders for the balance sheet - also the law of deferring (letting something else lead vs just the main entry - what had more data and details)

- See EOT # 13047 in the shop for some new ideas - check the vendor type switch

- Steve recommended that I review the loyalty points and see if we could do something similar with some possible auto actions (behind the scenes).

Working with ChatGPT on images for the investor packet. Meeting with Hamid. We were working on some CSS training. We have a small thing that we are trying to recreate as a practice session. Good learning stuff, from scratch, plus some in-line code prompting. Trying to sharpen some skills. Jumped back into refinement work with ChatGPT. We got the 7-page investor packet, visual version, pretty much done. See attached for a copy of that file.

Small to do list stuff. Light research on Codex with ChatGPT. Steve wants me to check it out. Recording notes from the past few days. Phone call with Cody. He needs a letter of recommendation. He is planning on going back to school to get a masters in computer science.

More work with ChatGPT on the investor packet text and copy. Towards the end, we were finalizing some of the text and even made a few graphics. These are not production ready, but this is where we go things to. See attached for a couple of images.

Working with Russell on the documentation project. He had added a screen reader to the page. Light testing and working with the screen reader. Towards the end of the session, he added a highlighter section for the novel pages. Fun session. I was mostly watching and learning. We have put in about 120 hours (give or take) on this project. It is looking awesome. I have a copy on my local box.

Working with ChatGPT on finishing up some of the investor planning summary stuff. We have a bunch of the stuff and tons of info in the chat. We were working on some summary stuff.

Multiple sessions throughout the day. Starting at 12:30 pm (afternoon) and ending around midnight. Long day.

Back working with ChatGPT on the investor financial presentation. Going over proposed adilas departments and how to mix things like people, structure, products, education, growth, retention, ecosystems, and capital. Good stuff. We were getting super deep. Great discussion, exploration, and planning session.

From ChatGPT talking to me - I really enjoy the role we've settled into. You bring the history, lived experience, raw notes, concepts, and vision; I can help listen across all of it, find the recurring patterns, organize them, and translate them into something other people can understand and act on.

That's especially useful here because we're not trying to replace what Adilas is. We're trying to figure out how to give it enough structure, people, funding, and breathing room to become more fully what you've been trying to build for years.

The old notes have made that clearer to me. A surprising amount of what we're discussing in 2026 isn't a new direction at all. It's unfinished direction that has kept resurfacing because there hasn't been enough sustained capacity to carry it through.

And now we get to put some numbers underneath it. That should be fun.

Emails and light clean-up stuff. Typing things up, using voice dictation, and prep work for the adilas pitch and financials. Finished up the prep work for the code development department. Then flipped over and started working on the prep work for the admin and billing department. Finished up the first round of the two documents.

Working on some voice dictations to help with an AI project for defining some needs for the proposed adilas departments. I have a number of handwritten pages with notes on them. I was opening up Microsoft Word and using the voice dictation features to read the ideas and expand on some of the topics. After doing the voice stuff, I would read over each section and make corrections and small modifications. Good process. It really helps to have the notes written out before I try to do the voice dictation stuff.

More work on the admin and billing department stuff. Prep work for getting back into the chat with ChatGPT. I'm trying to get some things done that I know that I will need (where we are heading with the chat session). Setting up a document that deals with my thoughts on direction and focus. I was expanding on some notes that I wrote on a small post-it note. Look to the future. See attached for my document.

Meeting with Hamid. We were talking about corporate structure and the role of managers. He works at Walmart. At the store level (not the whole global level) they have a main manager, teams and coaches, team leads, and team associates - even they are trying to simplify things.

Inside of adilas, we tend to have a lack of structure, somewhat free floating, and everything is super loose.

Here are a few things that Hamid does to help motivate his team. Morning huddle, showing sales and stats, what is upcoming, keep it fresh and encouraging them, they bring him their concerns, try to motivate them, some rah-rah (even when he doesn't feel that way), quick messages, keeping touch throughout the whole day, small rewards for doing good, get to know them - even outside of work, if they are burnt-out, let them try something different.

Putting value to the versatile or multi-talented folks - you are the best resource that I have for this job.

Towards the end of our meeting, we went over some CSS training. A lot of it today was talking about management styles and sharing some info and stories.

Back working on the investor pitch and business plan. Spent some time going over the product development area or department. Spent some time writing things down on paper to start. I'm really close to this department and don't want to overshadow it or put an unwanted spin on it. I'm not trying to cover anything up, but I've been helping with this department for over 20 years. Lots of changes, both good and bad, along the way. After that, I switched over to working on some department stuff for the admin and billing department.

Back working on the investor pitch deck information. Reviewing some information and a chat session with ChatGPT. Working on getting enough information to establish reality and credibility without drowning them in too many details. The story matters as much as the numbers. Why now? What do we have to offer that hasn't been there before? Great questions.

Adilas is moving from primarily building functionality toward organizing, simplifying, packaging, and exposing what already exists - while continuing to develop the next generation of the platform. We are also seeking to change some of the existing patterns due to team, talent, compacity, funding, and budget constraints. We have done a great job with what we have had to work with. The opportunity comes in seeing what we could do if we apply capital, talent, and ownership in the right ways or directions. That could be really cool!

Working with Russell. Working on the documentation tool and project. Russell was working on some printing options and not showing page breaks when printing. Talking about cause and effect variables and how they change your world. Just one switch can cascade through things. Working through things and talking about pros and cons of what we are doing. Good learning session. Talking about how we are starting to accept certain things from AI based on tradeoffs. Weighing out some of those tradeoffs. Talking about changing the game.

Recording notes and paying bills. Just normal small stuff.

Small intro meeting. Meeting with Aston from Aizoh Capital. We just chatted for half an hour and talked about some different options. Here is a super quick list from a couple of post-it notes that I took during the meeting:

- We need a deck

- We need a data room - show everything

- Investors want to see IP, business plans, tax records, etc. If you think they may or may not, hedge towards they want to see it.

- You have to reach out to thousands of investors. People don't usually queue up or line up.

- We talked some fees - both frontend fees and backend commissions - there were various options based on the reach, the help, the amount of handholding, etc.

- I stated that we were looking for about $2 million dollars to do a commercialization round - Aston was saying that sometimes raising more is easier than raising small. The investors put a value on what you are wanting to raise.

- Nice conversation - One of his biggest recommendations was get some help vs trying to do it by yourself. He said, that would be his biggest advice.

Recording notes from the past couple of days. Also making some notes on where I want to go with parts of the adilas pitch. Trying to work on the pieces there.

Steve and I were emailing back and forth yesterday about the line item level groupings in the shopping cart. I told him that I could give him a small demo on what already exists. Spent some time reviewing the line level grouping stuff.

Emails and looking over some great emails and dashboard mock-ups from Josh. I read over a large email and then sent a quick note to Steve. Recording notes. Emails back and forth with Steve. He is coding some of the invoice line item level grouping stuff for the shopping cart that we were working on over a year ago. It is crazy how things keep coming back up. Anyways, he sent me some stuff from an AI bot, and I sent him over a few other tips and pages to check. Other emails from cory.

Multiple hours working more with ChatGPT on the investor financials and what we are looking for in our pitch ask. Great deep conversation. Going into each of the four proposed departments and answering questions about each one. I will add the link to this conversation later. Currently it is still in the rough and discovery mode.

We were talking about main personality traits of: Organizer, Doer, Creative, Consultant, and Salesperson

We also spent a bunch of time going over ideas and options for the four main departments that we are proposing for the adilas team. They are:

Growth - sales, marketing, lead generation, partnerships, packaging and commercialization.

Retention - onboarding, training, consulting, documentation, customer success and reducing friction.

Product Development - focused development capacity, UX, testing, finishing high-value projects, AI, infrastructure and modernization.

Admin & Billing - management capacity, financial controls, HR/people support, planning, budgeting and coordination.

Just for fun, here are the questions that we are trying to answer for each department:

Where is that department at today?
What people/capacity does it need?
What processes/tools does it need?
What education/knowledge assets does it need?
What does that unlock?

Fun exercise! Good stuff!

Recording notes from the past few days. Lots of notes on element of time # 13045 from my lunch meeting yesterday.

Meeting with Russell. We were working on the documentation project. We were going back and forth. I showed him a few things that I was working on, and he was showing me some of his new stuff. We were working with AI to help build out the book reader and novel part of the documentation project (digital stories or multi-paged documents - not really novels). We added in some zoom features on the book reader and also on the normal photo galleries inside the documentation tool. At one point, I had AI make some changes on my machine. Then Russell had me pass the prompt over to him and we did the same thing (ish) on his machine. Mostly Russell was coding and I was watching and making comments. We talked about possibly doing an AI adilas experiment to see how quickly it could help us remake some things. Just an experiment of sorts.

Just for fun, as we were talking, I got this quote from Russell, "There are three responses... no, yes, and wow! Shoot for the wow!" - kinda fun!

Finishing up doing some prep work for a lunch meeting. I spent a couple of hours working with ChatGPT and feeding it some of my numbers, research, and financials. Our plan was to make a small multi-page document that would cover a brief overview of where we are at today, current financials, where we are heading, some growth opportunities, projects, sales forecasts, what we are asking for, and how the funds would be used.

I really enjoyed where the chat was going and heading. We, ChatGPT and I, didn't finish before the lunch meeting. We got some of the first pages, done to a point, and left off on the upcoming projects. That got pretty deep and needs some more loving. That's okay, I want to return back to those topics and really get them right and correct. I had a bunch of other things printed out for the lunch meeting, but we ended up just talking vs looking at deep or hard numbers or documents.

I went into Logan and met up with Chase. Originally, it was going to be with Matthew Coltrin from Pitch Launch and Chase Combe, one of his investor friends. Matt couldn't make it, so it ended up being just Chase and I. Chase is from Hyrum, UT. We had a great meeting and chatted for about 1.5 hours over lunch. After lunch, I went to a local park and recorded some notes. This is kinda funny, but I also finished my lunch. We were talking so much that I had to get a take-home box and ended up finishing the rest of my lunch at the park. Here are a few of my notes:

- Some of the most fun topics were adilas history, and how what happened then had a cause and effect, that framed up what happened back then and also what is happening right now. That was super fun. Chase was asking some great questions that just led to the next small topic or side tangent. Great questions.

- Chase recommended that we pull out the old independent rep/consultant model and tighten it up a bit. I mentioned that it worked slick, but we had some of the rep/consultants overpromising, not helping their clients, and a little bit of wild west stuff going on. We may have to retweak it, but it worked super well back in the day. Not only for reps, but we did the same thing for developers and tech guys. I'll bet, if we pulled it back out, and tightened some things up and made some rules and expectations, it could work great again. This is a possible way to get sales up, without asking for money or doing some kind of capital raise.

- We talked about a couple things that adilas has tried to avoid in the past. Some of these go clear back to the Morning Star Automotive days (original home of the adilas.biz application - custom write-up for a multi-location used car and trailer dealership). The two topics were traditional loans (borrowing money/debt) and employees. Adilas has tried to avoid both of those with some success. We talked about a tipping point, where at some point, those things may need to come into play. If not, you can become limited by capacity, unless you have tons of sales or some other source of revenue.

- We talked about how not all money is the same. Some of it comes with virtual teeth (downsides) vs other money that is more friendly. One of the things that he said was only take the money that we wanted to vs just taking any money (investments).

- By way of advice, he told me to dumb down the "ask" (request for funding) with more clear we need X, you get Y, this will create Z benefits. He said that a 3rd grader should be able to understand it. Along those lines, he also said that if it was too open or broad, you can lose an investor in them weighing out the opportunity costs. A few small options are okay, but don't overdo it. You have to have a small, tight, ask. Great advice.

- You may not be able to just pull something out that used to work awesome. You may have to adapt from where you are at and what the new goals and/or environment bring to the table. It's fine to recycle certain things, but you want to keep heading forward and/or maintaining ground that you have gained. This isn't always true but try to keep heading forward if possible.

- Use USU (Utah State University) as a resource. You have a bunch of new talent that are looking for jobs. I would also add Bridgerland or B-Tech to this equation. They are a local tech school. They, both USU and Bridgerland, could be great resources. I told Chase that I on purpose moved back to Cache Valley, Utah, because of the college and possible interns and such. We did a bunch of this back in 2013-2017. We ran out of funding and had to somewhat abandon it. Maybe head back that way and see what we can do in the independent developer, tech, or salesperson (rep/consultant) model.

- One of the problems that we had with the older rep/consultant models was dealing with reps that got enough clients and stopped recruiting more sales, leads, and companies. They almost got to a content level (satisfied level) and then just stayed there. We would like it to keep going. He mentioned that instead of an ongoing commission, maybe we could just do some finders fees or bird-dog fees (person who gets the account to sign-up) and then have adilas or some other method of retaining and caring for the client.

- This is a common thing, but sometimes an admin or founder works in the business and really has their hands in deep. There is an old saying, you can either work "in" your business or "on" your business. I think that I need to pull out of the deep, in the business stuff. It is still really important, but if you spend all of your time there, who is steering the ship or driving the car (working on the vision of the company)? There has to be a mix.

- One of the questions that Chase was asking was dealing with our existing team. I mentioned that we are somewhat maxed out or tapped out, based on our current team size and abilities. We want to grow, but there is almost no room to grow, with what we have. It comes down to skills, talents, virtues, time, capacity, and bandwidth (what you can handle). I would love to make some of the "ask" (for funding) about improving and increasing our talent pool and bandwidth. That would be awesome. As a small side note, in part of our fracture - adilas lite plan, one of the first things that we have identified is some underlying team organization and stabilization stuff. It is currently listed under the codename of the jelly fish model. See this website for more info - Web link to the company structure - jelly fish model. One of our primary goals is to get 4 different main departments - Growth, Retention, Admin & Billing, and Product Development.

- If you are going to make any promises, make them clear and upfront. Along these lines, I would really like to eventually build out some profit sharing and what not. We have tons of ideas on the adilas trust and where that could go. Maybe we could setup some benchmark values where we will try to small incremental changes. Like Russell always like to say... "Small drops in a bucket will add up. Just get it started."

- Just a thought for me, what if we make the general ask for funding really simple. Then if we want, we could put more stuff out on the investment opportunities website, if they want to get a little bit deeper. Here is the link to that site - Web link - adilas investment opportunities.

- I think that I am going to set a goal for the commercialization round, funding round or capital raise, for adilas at $2 million. I would then like to show what we will do with those funds and how that will increase the value of the shares of adilas.

- A couple of closing thoughts... Stabilize the team, tighten up the ask, pull the independent rep/consultant model back out, put more complex investment options on the website.

Prep work for a meeting tomorrow. Printing out some financials and getting some numbers together. Working on gathering more information on current financials, project projections, and sales forecasting.

Working on the vendor credit project stuff. We already launched round one of the project. This is just to help it out a bit (round two). Research on vendor credits. It, the topic, covers way more than just vendor credits. Lots of great entries. There were over 50+ entries that mentioned vendor credits. Great review of where we have come from and where we are going. I loved the review session. Tons of fun accounting things coming in the future. Also, a small review of MVP lists for changes that we want to make.

Small note for me... I was doing some research on vendor credits... I only got to the end of 2023... Still need all of the other research since then. The older stuff was a great review and helped me see some pieces and patterns. Even where we are heading. Web link - developer's notebook on vendor credits.

Small data fix for a client on the data 9 server. I had to un-void a PO. I let Cory know once it was updated and she was going to reach out to the client. Recording notes from the day.

Meeting with Abby. I was showing her some of my mock-ups and getting some feedback. We were talking about small levels of the iceberg analogy (only show what is needed, hide all of the rest - like the part of the iceberg that is under the water). She is working on a new graphic about the concept to help record your business story. We talked about the idea of different checkpoints and stops along the data journey. I showed her some older drawings for the concepts of the data assembly line. Some of the pieces are very similar. We also talked about AI and where she stands. It, AI, is not really her thing. She feels conflicted and wants to be true to her values and stance on the subject. I can respect that.

Got up early and started working on wireframes and mock-ups for the food pantry - industry specific recipe maps. Worked on the admin homepage and client/household detail page mock-ups. Went into town to meet with Matt at the food pantry. Showed him some of my progress. We went over some questions and started going through flow and general intake processes. We were mostly focusing on the volunteer check in and assistance flow. We got out paper and pen and did some scribbling and drawing. I already had some of it mocked up, we just made some minor tweaks. I took a few notes and he basically gave me permission to simplify everything. He wants it super simple.

Small session before bed. Graphics and playing with mock-ups. Working on building an admin homepage. Just getting started. I'll finish it up tomorrow morning.

Quick CSS changes to help with the order of operations. There was some new CSS that was added at the end of the section and was overwriting things above it. Small order change to help it play better. Recording bills and recording notes from the past couple of days.

Small fix on the invoice homepage. Some of the top navigation was broken due to a JavaScript error. Ended up making both JavaScript changes and CSS changes. Light debugging with AI's help. I worked for a little over an hour and then Russell joined me. Once Russell joined, we worked with his help on some other fixes for the invoice homepage. He was able to help me make a few changes that I hadn't gotten to yet or couldn't figure out.

We then spent the rest of the session working on the documentation project. Russell was working on adding in a book reader tool. It has vertical page views, multi-page layout options, and zoom functions. It was fascinating to see his creativity and what he can do with it. He uses AI, then reviews it, has it change it, or he changes it himself, to meet his wants and needs. So fascinating to watch and learn.

Phone call with Steve. Talking about updates, changes, etc. We spent some time talking about vendor credits. Steve recommended that we use the vendor switch to help with auto adding the other part of the transaction. If the vendor is marked as an inventory vendor, we could update COGS (cost of goods sold) or a service vendor, we could update the expenses. As a recommendation, he recommended that we check out loyalty points. It has a similar auto flip to keep things square and right.

We started talking about Yogen Fruz and some of their touch level cart buttons (touchscreen stuff). We jumped onto a GoToMeeting and he was showing me the buttons to add new things to the cart. They looked more modern, as compared to the older my cart favorite buttons. Steve was saying that things seem to be heading towards bulk building of the menu trees. He is using AI to build some of these things. The AI was recommending three screens... phone, touch pad (mobile or tablet), and normal desktop mode or sizes. See attached for a couple of screenshot samples of the new buttons that he is working on.

Steve was saying that coding with AI is almost to a throwaway code level. It is almost easier to just rebuild it with new changes vs going in and changing it. Steve is really trying to help clients out and really solving client needs.

Recording some notes from earlier today and yesterday.

Small data fix for Sean. He had done an import (uploaded new inventory items) and was missing the vendor. I had to go in and update a few records and tables to get it correct. Phone call with Sean to do a quick follow-up. Spent an hour fixing a file for Sean. Adding in a default vendor field for a CSV part upload page. Pushed up new files to all servers.

Light research on vendor credits. We already allow for these, through special accounts. Cory and Steve want me to look into helping to tighten things up a bit. They can get kinda interesting. All kinds of situations may arise and/or be needed. I watched a couple of small videos online how other software products take care of it. As a note, it seems like a challenge, no matter how you do it. Here are a few things that I found - small notes:

- Vendor credits can come from returns, discounts, or overpayments

- You want your A/P's decrease

- Back in the day, we use to go to the actual PO or expense and put a new line item on the record stating that we got some kinda of vendor credit. We would then alter what was owed and/or paid. The old way was a very manual process.

- We already allow you to claim and use a vendor credit. We can back tie it to a vendor, a PO, or an expense/receipt. Without being super technical, you are somewhat declaring a new "almost like cash - asset" that can be used as a form of payment on a PO or expense/receipt. Currently, the missing piece is a possible offsetting entry to help keep things in balance. You can't just declare a new virtual asset without adjusting the COGS or expenses or inventory portion of the financials.

- You can map to an expense on the income statement. You can also decrease the inventory value, based on what happened.

- Other software companies had to create normal bills and then negative bills to record the entry.

- Apply the credit to the actual bill

- You may have to make a deposit or put a check back in the bank from the vendor

- There seems to be a need for clearing out the account - a manual offset of some sort

- So many situations... they keep changing... not just one simple solution

- We were thinking of doing an auto entry on the COGS for that vendor but it may not always go straight to COGS. There are a number of possible variables that we may need to consider. As a follow-up to this note, Steve and I were talking about maybe looking up the vendor type switch to see if the vendors were inventory vendors or service vendors. We met over the phone and then on a GoToMeeting session later in the day, after I had written these notes. If we do go with the new option, then we could maybe automate things based off of that.

- As a fun side note, eventually, we need to add in values for in-store credits. those too have some tricky questions about how they came to be and where they came from. All part of the fun.

Working on some wireframes for the food pantry adaptation project (industry recipe map). Working in a graphics program to setup some default layouts and assets that I could use over and over again. Super simple placeholders for page layouts, form controls, buttons, titles, notes, etc. See attached for a couple small samples.

Recording notes from 8/20/26 to 8/22/26.

Small tweaks to the play at the wall website that Hamid made. A few more small changes. l sent a quick email to Wayne about some changes. After that, I spent some time playing with VS Code and Claude AI making some CSS changes to a practice CSS page. Having some fun playing around. I was flipping between ask mode, plan mode, and agent mode. Trying to get my feet wet a little bit. Good work session. I took a break for dinner and then came back and did another small session. More color and CSS tweaks. Ran out of AI credits for this session. Here is a quick link to what I was working on - web link. This is just a simple CSS sample page.

Work session with Hamid. We were checking out the play at the wall website that Hamid had completed. The domain is playatthewall.com - He was excited as it was live. We ended up making a few small changes and pushing up new code to a spot inside of adilas - web link. We will get with Wayne (our server guy) to see how to update the actual domain site.

As part of our work session, we were using AI to help us do some CSS code changes to help with things called media queries (show it this way at a certain screen size). Fun session. It was new territory for both of us, meaning using AI to fix things through an agent vs asking for help and then making the changes by ourselves.

Working on dataflow and mock-ups for the food pantry industry adaptation project (industry specific recipe maps). Decided to use flex grid for the members of the families vs customer contacts. With flex grid tie-ins, I have more flexibility and bulk tools. The customer contacts seemed like a perfect fit until I found out that I needed tons of custom fields per family member (like over six custom fields per family member). I did a few more sketches and mock-ups on paper. I'm planning on using as much of the normal adilas pages as I can, as long as they don't look too complicated. I think that I am ready to start moving into more actual graphics (wireframes or mock-ups) vs small sketches and hand drawings.

Meeting with Abby. Talking about graphics and her current project. She is working on a new graphic for recording the story or digital storytelling. We talked about some ideas and direction. I then showed her the adilas blueprint that I was working on and how it has the five phases of world building in it. We then dipped out and looked at the individual smaller pieces of that graphic (see EOT # 12939) for smaller pieces. After that, we talked about hours, jobs, work loads, and where we are heading. We even talked quite a bit about mental stress and striving for a good balance. Life can get pretty tough sometimes.

Recording notes from the past couple of days. Scanning some of my notes for the food pantry project. See EOT # 13037 for more information and the actual scans.

Looking over the DevDocs or documentation project that Russell, Abby, and I have been making. Looking over code and playing around with different features. I then rolled into a work session with Russell. Doing some code review. If you change one thing, it changes the whole outcome. Russell and I were talking about life and life lessons. He was doing some code review and I was watching and doing some small other tasks as he was doing his stuff. Towards the end, we got into some exploration and deeper code review. Most of the functionality is done and we are actually doing real final code review on html, CSS, and JavaScript. We ended today partway through the CSS review.

Went to the park for a change of pace. Worked on some drawings and mock-ups for the food pantry custom data and workflow diagrams and screens. They are just hand drawings, but see attached for what I'm working on. Just for fun, I passed these notes back through ChatGPT. Nothing major, just reporting in. Click here to see the chat session - https://chatgpt.com/share/6a851427-b398-83e8-8e84-fadc1d2f3cf7

Recording and reviewing some notes from last week. I'm just chipping away at things and making light progress. It is fun to see where I have been and where I am headed. I enjoy that review process. Just for fun... two weeks ago, I was working on the adilas mini pitch. Last week, I was able to get version 2 of the adilas blueprint finished up. This week, I should be doing some more mock-ups and graphics for the food pantry industry recipe adaptation.

I also spent a little while doing some CSS training. Working on text alignment, spacing, and other text formatting options. Continuing education stuff.

Drawing some mock-ups for the food pantry project. I knew that this was the next small phase, but I kept making excuses not to jump into it. I basically had to break into it... it was a small mental barrier of sorts... it wasn't too bad, once I got in. This is just me, but I've done this tons of times, this just felt different in a way - my thinking was different - what do you want, how can you simplify it, hide all complexity until needed.

As long as I'm confessing... I was excited to be designing a new flow and product, but at the same time, thinking, man, how much work is this going to be? I have a little bit of mental trauma due some really long and ugly projects with zero funding and backing. Years and years, grinding through things. Those tend to suck the excitement out of the prospects and projects. Anyways, I am excited to see where this goes.

Reviewing a YouTube video that Steve sent to me. This is my second time watching it. I decided to take a few notes. The video was a tech talk from Tom Enden at a Wix Engineering Conference. Here are some of my notes:

- Being proud of code that I didn't write.

- Going beyond the building of the systems and into what is possible.

- He was proposing that English, real conversations and dialogue, are a rung in the ladder (changes in coding languages). That's the new coding language (English or plain speech).

- The power of dialogue and being involved, participating, guiding, prompting, etc. Not outsourcing thinking but making people think.

- One of the next topics was dealing with who owns the code? Distributed authorship and being original and yet building on top of other choices and decisions.

- We never have controlled all of the pieces; this seems to be a continuation of the same process. We assemble and put things together.

- Leveraging AI and being willing to stand behind it.

- Talking about "taste" and what you want. He was talking about taste as a skill.

- Judgement and choosing what to build. That is becoming the work now vs pure coding.

- Great video, I enjoyed it. Less than 20 minutes. Here is the YouTube link - Web link

Prep work for the food pantry recipe map project. Going over questions, writing up ideas, and working on prep work for wireframes for simple flow, dataflow, or specific workflows.

Met with Bryan to go over some code. We mostly talked and went over some black box stuff. He is on hold for a couple of projects. He is currently working on the Adi AI agent, a new left-side menu system for KOR systems (small white label) and a custom invoice for a client. After Bryan left, I recorded a few notes from yesterday and today.

Going over CSS rules and practice pages. Working through the W3Schools website on CSS. Pulled up a practice document and did a bunch of playing. I've done CSS for years, but I have never really taken a class on it. Trying to make sure that my basics are solid. Continuing education stuff.

Watching some videos on CSS and basic rules. Working through a few sections on W3Schools and CSS training. 

Learning as you go along. Learn things as you need them. You don't need to know everything up front. There is too much. We spent some time playing with AI and image generation. We looked at some of the videos that he, Russell, is doing. We then flipped over to the documentation project that we are working on. Russell was making a few changes, and I was playing with the app (experimenting). We did a little bit of light code review and playing with the actual image galleries and tools. Fun hands-on learning today.

Working with Bryan. He showed me some updates for the Adi AI agent stuff. We merged in a number of new changes. We then pushed it up to data 0 to do some testing. Fun to watch him work and see what we have to do to make things work. It gets pretty tricky. We had a few small glitches, but making progress. At the end, we setup another time to talk and work with this and other small projects for tomorrow.

After Bryan left, for another appointment, I spent some time looking around a bit and playing with some other new features that I see inside of the system. I believe that Steve and Josh have been working on adding some other nav and header stuff. It is still in a beta mode, but just checking things out. It has the branding of KOR or KOR ware (anyways, a slightly different branding).

Work session with ChatGPT. I was looking for an old, saved email and ran across an older version of the adilas blueprint document. I read it and then worked with ChatGPT to create a newer version of the blueprint. Great session. Here is the chat session link: https://chatgpt.com/share/6a7bda35-5d70-83e8-8a7f-5086c886a10c

Just for fun, here are a few things that we cover and go over:

The Adilas Blueprint moves from where we came from, through how the platform works, into where we believe it can go.

Foundation & Purpose - Sections 1-5 Purpose - Adilas in a Nutshell - The Problem We Are Trying to Solve - Origin & Development Philosophy - A Working System and a Working Prototype

The Adilas Model - Sections 6-10 The Adilas Formula - World Building & Industry-Specific Recipe Maps - The Transactional Core - The Data Assembly Line - World Structure & Time

Building on the Core - Sections 11-15 Simple First. Expand Forever. - Ship A & Ship B - The Value Add-On Core - Business Intelligence & Digital Storytelling - AI as a Layer and Cross-Layer Capability

What Makes It Adilas - Sections 16-17 What Makes Adilas Different - Community, Ecosystem & Shared Building

Future Direction - Sections 18-20 Where We Are Heading - An Open Future - Discussion & Exploration Points

The basic journey: Understand the problem - Build on a proven core - Mix the right ingredients - Build the business world - Generate desired outcomes - Keep expanding what is possible.

Here are links to both the older version 1 of the blueprint and the newer, more up to date version 2 of the blueprint. See the chat session link above for the process of updating the blueprint.

Reviewing and then jumping into making some wireframes for the food pantry project. Still in the prep steps of that process. Reread a small chat with ChatGPT on this industry specific recipe and workflow mapping project. Basically, how to assemble and configure the recipe for each industry, depending on which one we are working on. Think, reusable blueprint for other implementations.

Later on, I was looking over their assistance application documents and reports for the food pantry. Comparing online assistance application with the pre-printed forms. There are a number of differences. We will need to standardize the input to get the best results. Also, after making those comparisons, I spent some time looking at the required reports and making sure that we are catching the correct data.

Here are some of my notes, after rereading the ChatGPT session on doing industry specific recipe mappings.

- Think in business objects... 1. Households (the real customer), 2. Persons or people - adults, children, dependents, and their relationships, 3. Visits, 4. Alerts, 5. Notes, and 6. Reports.

- Workflow mapping - instead of pages... what is the workflow or journey?

- MVP Bridges - keep one platform, create a focused front-end, hide complexity, expose power only where or when needed, let organizations flow into the larger ecosystem.

- Mini skin framework, industry recipe map, ingredients (existing pieces, parts, and functionality), mix and blend, then adapt or add industry adaptation stuff to round out the project. Focus on the desired outcomes and needs.

- How can I/we help?

- Find the moments - at times, the system (software) needs to both appear or disappear. Help guide where needed and other times be in the background (transparent).

- This recipe may become one of many.

- Instead of selling modules, we are using existing, proven components, and assembling or configuring them for a different industry.

- Once again, having fun comparing industry recipe maps and world building. I think that it is fun. They work well together and even allow for crossover. See elements of time # 13015 in the shop for an earlier breakthrough between industry recipe mappings and world building. As a side note, that was only a week ago.

- Reusable blueprints for other implementations

Phone call with Josh. He wants me to jump in and help them do a bunch of user interface changes inside of adilas. I told him that I was working on some other pieces and projects. Everybody thinks that the existing adilas platform is our full product. In some ways, that is correct. In my mind, the existing system is just the working prototype of what it could be, not the actual final product. We get judged super harshly on what it looks like. That was not the original goal. The original goal was more of a "could we" and "can we" do this and that? Okay, now that we can see that, the goal needs to switch, but that was not the original goal. The current adilas.biz system is just a prototype of where we want it to go.

The other thing that we keep seeing is that certain people are judging us saying, why don't you do this and that? They are great questions and they have a valid point. However, they kind of just expect us to do it, not thinking about how much that costs or the time that it would take. We have taken a different path through the woods, people like a lot of what we have done and/or are doing. They just expect it to be fully done and wrapped up (all shinny). We have been building this out of a garage and bootstrapping it along, the whole way. this is where we are at.

I really hope that we can get someone to see, wow, if I put some money in and help fund this (gas money or seed money), we could take this whole product, system, application, and platform super far. If not, meaning we don't get outside funding, we'll just keep chipping away at it as we can. I know that it is bigger than I am.

I really like the idea of being a pioneer and helping to pave the road for other future generations. I don't have to build the whole thing, I just want to keep helping and smooth the way for others.

Emails and reading through some feedback from Steve and Grok on the adilas mini pitch. It has some great stuff in it. I have attached the feedback (copy and paste from the email) to this element of time. See attached.

I then switched over to do some planning for the food pantry industry project. As I started, I had the thought to review an older document about taking control of the documentation processes. I have read this document a number of times. Great read. This time, I pulled up the document on one screen and put it into a screen reader on my other screen. It was much easier to read it this time around. I was also able to stop the screen reader and circle back around on key points that interested me. In a way, I'm a want-to-be project manager... :) I've got a number of big projects ahead of me. I've been learning and trying to apply things for years. I've done tons of projects. It has been a process for me. I enjoy it. See attached for a copy of the document that I was reviewing. Once again, I recommend a screen reader for reviewing its contents.

Recording notes from 8/4/26 to 8/7/26. Many of these new entries had a number of graphics and images. Fun to see things come together.

Adding some new links to the adilas pitch, similar to what I did for the mini pitch. More fixing up the bigger adilas pitch (10 slides) with small graphic changes, text changes, and small mini links out to bigger pages. Adding some links to the investment opportunities page and other adilas lite - fracture pages for the new adilas mini pitch. Trying to spread it around. I think that it could be a great little marketing document for adilas. Short, simple, power packed, and visual. Good stuff.

Meeting with Hamid. He showed me some of his progress. We pushed up his code to the live server. We then sent an email to Wayne asking him to wire up the domain playatthewall.com to the site. In the meantime, we pushed it up to a folder on the adilas server. Next week we will jump back into some more CSS stuff and training. Until the mapping to the real domain goes live, you can see his small promotion website here.

Meeting with Adesh from Solen (investors and software company). Good meeting. Talking numbers, history, story, direction, fun conversation. He said that he would take the info along and pass it along to his internal team. As a side note, of all of the investor meetings that I've been on, this one was pretty casual and fun. I enjoyed it. Sometimes, they can be pretty stressful and you're not sure what they are looking for. Anyways, it went well.

Finishing up the adilas mini pitch. Added a small plus sign, in the bottom righthand corner, to each of the mini pitch slides to show that you could click on the graphics for more information. Paying bills and recording notes. Looking around at some new changes inside of adilas.

Working with Abby and Russell. We were working on changes and grid system training. I put the mini pitch into the documentation project while Russell was making other small changes. It was super fun seeing it come to life with real images and content. I was using the auto build sub navigation, gallery options, sliders, search options, etc. Fun session today. See attached for some small graphics.

Meeting with Abby. We all, most of us, have a need for people, interacting with people, for mental health. We were going over some new graphic ideas for "cookbooks for businesses". See element of time # 13015 for details - dealing with industry specific recipe maps or industry recipe mapping. We went over the new mini pitch together. I also got some new graphics. See attached.

Working with Heather to simplify some of the PowerPoint slide presentations and show what we are working on. Going over existing graphics and slides. Talking about ways to remove some of the clutter. Working on a 4 to 5 slide mini pitch. Changed up one of the main systemized approach graphics. Made it bigger and more simple. Along with that, I started a new ChatGPT session to help with the new images for the mini pitch. See attached for some of the new graphics. Fun session.

Here is the ChatGPT chat session link for the session: https://chatgpt.com/share/6a7383e6-7850-83e8-9d1a-b92b80d32da0

If you want to access the actual PowerPoint presentation, 10-slide version, click here: PowerPoint Link. If you want a PDF version, click here: PDF Link

We have also prepared a small 5-slide summary for what we are calling "The Adilas Mini Pitch". If you want to access the actual PowerPoint presentation for the Adilas mini pitch, click here: PowerPoint Link. If you want a PDF version, click here: PDF Link

Emails and recording time. Other small odds and ends. Reviewing and planning the new site for the food pantry. Added some new verbiage to the adilas value add-on core model (master plan).

As part of my review, I was re-reading over some plans that I was working on with ChatGPT for the food pantry - https://chatgpt.com/share/6a5287b4-8b28-83e8-9057-76e9a8d209cb

Here are some of my notes from reviewing the prior chat session:

- Industry adaptation project

- Guided experience for one specific workflow

- Not software... more of a "Volunteer Operations Console"

- At the software level... What do I need to know right now? Try to stay ahead of them.

- Goals: 1. Simple client intake - paper and online - make it simple, 2. Find people instantly (by name, address, barcode, and household), 3. Protect volunteers - alerts and possible workflow disruption feature, meaning, we may need to stop the normal flow until the alert is dealt with or acknowledged, 4. Track visits, and 5. Future client app - this may be a round II or phase II option. Focus on the MVP first.

- Workflow mapping - what do they actually do and in what order?

- This is an MVP bridge type app - keep one platform, create a focused front-end, hide complexity, expose power only when needed, and let organizations grow into the larger ecosystem.

- Mini skin framework - industry specific recipe map - ingredients, workflows, industry adaptation, and generate desired outcomes.

- Serve people over software - focus on the people and serving them

- Look for moments vs screens - aka "Workflow mapping" - Think flow and questions and how can I help vs just interface and software.

- Plan it, meaning this mini project framework, as a case study or industry recipe

- Industry recipe maps and world building - somewhat interchangeable terms - this was a new discovery for me. I personally like world building better, but if someone is struggling with what that means, you could always say something like: Another term for world building is "industry specific recipe maps". Instead of selling specific modules or software pieces, you assemble industry specific solutions from a number of proven components. You take business functions and application players (like customers, invoices, inventory items, vendors, etc.), mix them together and these become your ingredients. You then setup specific workflows, industry adaptation, and generate desired outcomes. It becomes an industry specific recipe of sorts.

- Think reusable blueprints - per industry

Emails, paying bills, working on content for world building and tying things into the adilas core concepts. Working on the sections for decisions, choices, and consequences. See attached for my progress.

Great meeting with Hamid. We jumped on ChatGPT and passed it some of his older code for a new website called "Play at the wall". Eventually, this will be an adilas website to help with API sockets and API endpoints. He was working on generating new content. We went through a process of taking the code that he was working on and then passing it back through ChatGPT to help with some clean-up. Good session. Here is the chat link, if needed. https://chatgpt.com/share/6a6bf039-222c-83e8-b0e9-46d4a9243ea0

Emails, recording notes, and then some page changes out in the adilas lite - fracture section of the site. Adding some links to the PowerPoint slides so that you could get to the full-sized images from each slide. Pushed up a number of small changes and files. Added a video link to the adilas pitch from the videos and research page.

Work session with Russell. We have gotten our documentation project done enough that I got some live code on my machine today. That was fun. I was playing around with things and doing small samples. it should be really fun. We are still doing some code review, but it won't be too long, and I will branch off of his code branch and start making it real for adilas and the adilas presentation gallery stuff that we want to put in it. I'm excited.

Working on the world building document. Reading and brainstorming on ideas and concepts. See attached for my progress. Still just roughing things in.

Meeting with Bryan. Going over some new changes. He is working with all of the main quick search prompts and being able to show the prompts and keywords to help the users. He's making progress and doing well. We pushed up a couple of small changes. Small chats about the future and what we are seeing and hoping for.

Recording notes and reviewing a video from Cory about vendor credits. Emails and then jumping back into the changes on the help files and help navigation stuff. Updated the "all help files" page as well. Pushed up some new code to test live on data 0.

Emails, phone call with Bryan, and light research. Recording notes and hours from last week. Adding links to some of the help files. Reworked the help navigation on the main help pages. Made it look a little bit more modern. Added a show/hide more options with other navigation buttons. Exporting some new mini screenshots and graphics. Almost got the new changes finished. I will wrap it up tomorrow.

Recording notes from 7/22/26 to 7/24/26.

Small fix for Bryan and the Adi AI agent. Merged in some new files and pushed them up for Bryan. Steve wants us to turn the Adi AI agent off until we get a few things fixed. It's kinda sad. Mostly, people, our clients, are freaking out about having all pages run in the Adi shell (iframe). They are used to seeing the full URL with id's and such. Some of them like to use multiple windows, multiple tabs, etc. I think that they don't like change. It is way better than what we have, but they are making blanket decisions and just turning everything off, even if people like it. Oh well, we'll get there. Just a bump in the road.

Meeting with Hamid. We were extracting some of the HTML and CSS from his Next.js code project. Trying to put things back together. The first time, and second time, he sent me some files, there were tons of them (in the thousands). We now have it down to 4 files vs too many to count. The current code needs to be reworked and formatted. Making progress and harvesting code from his project. See attached for a small screenshot.

Went into the Cache Food Pantry to work with their staff. I'm experimenting and seeing if we can help them out with a super simple adilas system. Spent the time with a couple of the key players, watching what they do, taking notes, and sketching a few things out on paper. See attached for some of my notes. It should be a fun project.

Work session with Russell. Working through parts of the documentation project. We are suckers for eye candy. Make it look good. Russell was working on polishing up the different image galleries. We are both using this project as continuing education stuff. Great practice sessions with a purpose.

Working on world building concepts. Trying to combine a couple of documents together with concepts of world building and how adilas is kinda like a digital video recorder for your business. Working on how those two concepts work together to help with digital storytelling. See attached for my progress (still kinda rough).

Small code fix for the parts homepage. It was hiding or collapsing the search form when you first go to the page. Added some code to help it show the search form under certain conditions. It will also hide the search criteria as needed. Small changes. Pushed up some new code to data 0 and sent an email to Wayne, Cory, and Steve.

Reading emails. Working on the adilas core concepts overview document. More brainstorming and reading over the older documents. I'm not sure why, but I keep being drawn back to these underlying core concepts. They have a real value, both as building blocks as well as underlying rules, principles, and instructions. If someone just sees a list of the core concepts, they may think... that is great and all, but how does that affect or dictate what goes on in my business? I'm trying to go through the core concepts and create links back to how they help, organize, and create the underlying structure of world building and how that works for businesses. My focus today switched from just going over core concepts to how do these relate and facilitate world building. That was a fun switch for me.

Sat in on an online webinar about buying and selling a business. The host was Ross from the Front Range Business Advisors. He did a great job and brought a lot of personal experience and information to the table. Here are some of my notes:

- Why certain deals don't close - what are the deal killers.

- Lots of prep work. He kept coming back to this topic.

- You need to have some written processes in place.

- Key players (person or persons that are critical to the deal and/or success of the business). This is a big deal. The new owners need to see themselves and/or some other person filling that role. What does that look like?

- Flushing out some of the real concerns. Lifting the rug and really showing what is going on. Over disclose and then manage what is needed.

- Communication is a huge key - alignment is needed. Things tend to unwind in silence.

- Owner's emotional attachment to the business. What is your identity and who you are? Are they tied to the business? That can create and cause problems down the road.

- Due diligence and looking for those skeletons in the closet.

- Often a buyer is looking for SOP's (standard operating procedures). You need to make the value of the company transferable.

- Take time and make sure and look at client relationships, operational knowledge, vendor relationships, brand/reputation, and employee loyalty.

- Small discussion on cold feet and a tire-kickers. This could be people who aren't sure, just looking for information, and/or aren't fully committed (yet).

- Confusing between buyer enthusiasm and buyer readiness. There is a difference.

- One of the biggest problems is trying to do renegotiation at the finish line.

- Dealing with emotional pressure, not data. Digging into the feelings of or what's behind the questions?

- Preparation is one of the main keys to really selling a business. Clean the books, reduce the owner dependency, align the advisory team, and prepare seller psychology (ask yourself hard questions).

- Figure on a 2-3 years exit prep (it could be shorter, but it takes time). Balance and look at both data and emotional factors. Make a strategic exit plan.

Working with Bryan. He was working with some Grok AI voices. I made a small fix on the parts homepage to show/hide the search criteria. While I was working on that, Bryan was changing out the browser voice stuff. We pushed up some code for Byran. We then talked about normalization and working on voice to text options. We may have to take a break, due to budgets, but Bryan wants to get a list of the next phases and pieces of where it could go. We are joking around, but... we are teasing and saying that he has the Adi AI agent to a 5th grade level. We of course, want it to a college or PHD level, but we are making progress.

Jumped on with Cory, Steve, and Wayne to look at a bug on the ColdFusion servers. Somehow, it was not registering the form scope or form submission values. Nobody could login. We got it fixed and rebooted a number of servers. Wayne is going to look deeper into what might be going on and see if he can see anything in the logs. Crazy stuff. Good team effort to get it fixed.

Looking at new changes to the Adi AI agent with Bryan. He was making a number of new changes and such. Some great little changes. He is getting into the groove and making progress. We pushed up some small changes to data 0 for testing and setup a new time to meet on Monday. He has a couple of other things that he wants to tweak and alter. Good stuff.

Small label builder fix. Added an option where the label could be static and not tied to an application type (one of the 12 main players). Recording notes from 7/13/26 to 7/16/26.

Work session with Russell. Cleaning up code in the documentation project. The AI agent had added tons of inline styles and CSS stuff. We tried to have AI do some cleaning it up, but it was either taking too long, cost too many credits, or wasn't doing a good enough job. Interesting to see what it can do and what it cannot do. There is a cost to everything. If you go super fast, you end up with tons of bloat and extra code. If you try to trim it down, it either takes time or credits (tokens). Most of the changes were in our own documentation of the tool itself. Good work session.

Working with Bryan. Quick touch base and then made some plans for tomorrow. His new Adi AI agent went live this morning. Minimal hiccups. We had one client complain about the new Adi shell wrapper vs normal URL's. They have a custom flow and monitor the URL addresses. We helped them turn it off, so that it went back to the old way.

Working with Bryan. He was showing me some new changes. He is working with AI to help with the AI agent. He is clicking through things and resolving different issues. He has made some great connections and good progress. We made a few more changes, checked things out, and he pushed up some new code. It is looking good. The next major thing is code review, fix a few merge conflicts, and push it live.

We got it all fixed and then I tried using it on my local environment. It was struggling a bit. We spent some more time and got it working. There are a few quirky things, but all in all, we got it rolling.

Went into the food pantry and did some observations. Briefly met with Matt, the owner. Then I went out on the floor and worked with one of the volunteers at the front desk where people were checking in. They, the food pantry, already have a software system but they are looking at making some changes. I was mostly just watching what they were doing. The nice lady at the front counter was very helpful.

We did look over the existing software system. The existing system that they have does track what they need but it is too complicated. I went with the intent of making some notes, but I ended up just watching and observing. My main takeaway was keep it super simple, repetitive, and streamlined. I'm planning on going back and really taking some notes. Today ended up being just the feeling and vibe of the food pantry.

Getting a list of ChatGPT sessions that I have done over the months. Lightly looking over some of them. Quick casual browsing. Web link - developer's notebook for ChatGPT sessions.