Recording notes from 6/10/26 to 6/11/26.

Meeting with Hamid. He is working on the adilas API site called "play at the wall" website. He is using ChatGPT and VS code to do the site. We spent the whole session working through prompts, code, making changes, and light testing.

Bryan is working with Gemini and ChatGPT to help build in AI for adilas. He is trying to help make it interact with adilas through the quick search and direct prompts. His progress is looking good. I was impressed. I gave him a number of new pages to check, including the adilas mini API. He didn't know about that yet. We were building it out back in December of 2025 when we were working with the Nxtlinq folks and their AI agent. Anyways, gave him some new resources and talked about things. He is making great progress. Towards the end, we talked about things and plans for the next six months.

Showing Shannon the visual journey that I shared with ChatGPT (web link). We were talking about how long does it take to explain it (adilas) and how long to really get it? Talking about the green overlay graphics and how they show that we use the whole system to provide the functions that we have. Here are some of my other notes from the work session:

- Show different interfaces, chooser options (custom homepages), quick search, etc.

- Help them (our users and clients) see the progression - they won't catch everything the first time. Using the graphics... help them get it... help them catch the vision... oh, I get it... - that is awesome.

- Switched over to the big core concepts overview document. We spent most of the rest of the session reading and doing light editing there on that document. See attached for the progress. We only got about halfway through.

- Talking about solving the Rubik's cube - there are many different ways - either by math, complex algorithms, set patterns, or by story. I think that the story method is easier, at least it makes it easier for me. We are geared for stories.

- Just being silly... Shannon was saying that the word history could be broken into... "his story" (small stretch but fun).

- Bring in that human element.

- I want to pull out the video recorder story. I liked it. It might be fun as a standalone story. See attached.

- We read through the first couple core concepts sections.

- Desired outcomes solve the major pain points... I would like to do an infographic on pain. If you can solve the pain, they will invest time and effort into the solution. That's the hope.

- Nobody really wants all of this stuff (text, documentation, graphics, and info), until they think that I (we) can solve their pain or I (we) have the solution. That's the motivation.

- Here are some notes from the chat session from yesterday:

Level 1 — Features
What do you need?
CRM
Inventory
Scheduling
Accounting
Reporting

Level 2 — Results
Why do you need it?
Operational Control
Customer Awareness
Financial Visibility
Accountability
Process Efficiency

Level 3 — Architecture
How does it happen?
Connected Data
Flex Grid
Operations Lead Accounting
Data Assembly Line
Time-Based Architecture

Level 4 — Philosophy
Why was it built this way?
Systems Thinking
World Building
Results-Based Design
Challenging Tradition
Built By Dreamers

---

Alternate adilas formula wording... normal adilas formula: Mix(functions + players + concepts) = Results

Use Players
Mix Functions
Apply Concepts
Create Results

---

My role as a teacher and translator - teaching complex topics

Multiple sessions. Working on the what makes adilas different graphic series. Ended up pulling in tons of older graphics and working on creating a visual language for adilas. Fun session. We already have one, meaning a visual language, it just needs to be brought into the light a little bit more. Working with Heather on the 3-part pitch. Light edits and changes. Reading over some other documents. More work with AI on what makes us different and the adilas visual language. Finished up the chat session on what makes adilas different.

Two really good breakthroughs from this ChatGPT session.

1. Other companies sell modules and fixed features like CRM, POS, eCommerce, etc. We mix ingredients (players, functions, concepts) to get CRM, POS, and eCommerce. That is a completely different way of looking at software. You get the whole thing... then you mix and blend the ingredients, functions, and concepts to get what you want.

2. One of my personal roles is - I'm a teacher and translator between tech talk and deep concepts and how that really plays out for humans.

Here is the chat session link. It started out wanting to do a series of slides and/or graphics for what makes adilas different. By the time we got finished, it had some great stuff on the visual language and map of how adilas communicates and uses graphics. I loved the session. Here's the link: https://chatgpt.com/share/6a2a467c-9244-83e8-ba63-046be9536efe

Work session with Russell and Abby. We started into creating our own documentation for our own project. Ended up having to add some other pieces such as image captions, mobile menu views, and other small to do list items. It is so fun to watch how this unfolds and what it takes. We are around 45-50 hours into this project, with AI and with master Russell leading this project. This has been a great learning experience.

Working with Abby. She helped me on my layouts and graphics that I was working on. We wrote down some ideas. I will add/edit them later. I gave her some ideas on a new graphic that she is working on - the story of your business and video stuff. I sent her a copy of the core concepts overview document that Shannon and I were working on. It has a section that talks about how adilas records the story of your business, like a video camera. The goal for the new graphics is to show the concept of what we are doing. It isn't actual video that we record, it is data, histories, relationships, and transactions. However, the concept is the same... a record is being kept, and you can get back to it as needed.

Recording notes from the past couple of days (6/8/26 to 6/9/26). Working on a document of what makes us different. See attached.