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

K

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

L

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

M

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

N

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

O

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

P

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

Q

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

R

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

S

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

T

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

U

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

V

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

W

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

X

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

Y

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

Z

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

Adilas Key Contributors:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Fix & fill in the gaps

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

(sliding window diagram text skipped but referenced)

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

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

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

- Recruit help!

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

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

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

New notes from 12/12/25

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

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

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

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

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

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

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

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

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

- Times & seasons - everything in its time

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

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

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

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

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

- We are gathering

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

(drawing of two models with text)

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

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

- We are organizing

- We are learning

- We are being led

- I am so grateful!!!

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

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

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

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

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

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

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

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

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

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

Meeting with the Nxtlinq guys. Talking about advancements on persistent memory and where things are going. We talked about the backend Nxtlinq dashboard and how to read and help the agent really learn (make things stick). We may need to focus on a specific part of the application and get it really tight. Due to Thanksgiving, we will meet up again in a week. In the meantime, I will be working on some other projects. Once ready, we will get back to AI agent training.

Working with Shannon. Talking about the time it takes to use the AI agents. Talking with Shannon about the type of AI tool we are trying to use and setup. We spent some time talking about concerns and possible constraints, moving forward.

My constraints:

- I'm willing but should we do this? I really want it to work - I can see the potential - We need a master trainer that can help others

- We need to communicate - Steve and I

- My time

- Already put in a ton of time

- Questions on funding and budgets

- Train the mother AI engines and models or the mini model? Which one(s)?

- I need some direction - too many things on the plate and I don't know what to prioritize

- The training pieces are all over (on the web and in certain docs) also in my head - No one spot for all training currently

- Things keep changing

- I am saving my conversations with the AI agent, but it takes time to format them, and if it (the training) doesn't stick, then what?

- Putting in energy but not getting the output that is desired - we can only go fast for so long - we can keep chipping away at things, but that is it

- There are lots of parties involved, adilas, Nxtlinq, our users, and the actual AI agent

- We have a vision and we can build a number of things out... we have plans - those plans will take months and months - kinda feeling pressured

- Do we really want to have meetings every two days

- Tons of potential... how far are we willing to push it?

AI agent constraints:

- I've done x hours on the mini model, currently not retaining anything

- Storage at the database level - For them and for us - How can we help this process?

- How can we help with storage - Known needs - System level, corp level, and user level

- They are retaining the chat messages - At the Nxtlinq level - We are not

- Question - How do we really train this agent or entity?

- It, the agent, is giving bogus answers - For example - How do I get rid of an element of time - How can I tell how many elements of time I have (see stored chats from 11/25/25 - Some other user, not from me)

- Can it do what we need it to do

- Cut off from the mother, meaning the agent or mini model - Already over a year behind the data on the mother AI engine

- We don't know the model that it is based on... It really likes the security and blockchain stuff - Meaning what was the original purpose of the AI agent.

- We just need a simple bot that can translate natural language into adilas tools and prompts

- Not retaining information long term... Currently only per person, per session, and that's it

- How are they doing with the crawler to pick up content

- Demands - too much on us, build, train, market, deploy, and it doesn't even work all the way yet

- People aren't wanting it... what it currently is and can do... It take too long, it requires too many two-part authentication stuff, and it can't do advanced or multi step things...

- It is being used less and less - People want it, but if it gives them the wrong answer and isn't fast enough, they will move on

- Too slow, not helpful enough (wrong answers), too many auth steps, can't do complex actions, etc.

- Say you aren't using it... then you decide to use it... and it takes multiple steps to do the auth stuff... you have a quick question and you want an answer in a couple of seconds... you then have to do a multi-step 2-5 minute process to get your answer. Pretty soon, you say, no, not doing that... that is from our users.

At the end of the session with Shannon, we were talking about our simplified AI plan - 1. Teach it how to do some basic or system navigation, 2. Get it all trained up so that it can help with training and support, 3. The ideal is that it knows everything and can help with the higher consulting level and business level questions.

Shannon and I were also talking about the jellyfish model and helping to stabilize the team and their roles. There is a need there.

Emails and logging in and checking out the Nxtlinq backend dashboard. I'm hoping that I can use that or the main chat interface to help train the AI agent. Either way, we are making progress. We'll see where it goes.

Quick testing of the AI agent. It is still not retaining all of the information that we are training it on. We have to figure out a way for it to retain the correct background information (persistent memory). see attached.

Meeting with the Nxtlinq guys. Small updates. Thomas was showing me his nxtGPT product. They are tied to multiple LLM's at a single time and comparing them to each other. Figuring out the next steps. Talking about updates and ability to train and sync data with new and upcoming data. Talking about tax codes and new rules and how to keep the updates coming in. We need to make sure that the model (our AI agent) can get fed with new and updated business rules, data, and logic.

Phone call with Josh to go over progress and direction. He wanted to know how the training was going, for the internal AI agent inside of adilas. I reported on what I knew and told him that the new persistent training was not sticking quite yet for the AI agent. I sent an email to the Nxtlinq guys, and they are looking into it.

Meeting with the Nxtlinq guys. They wanted a way to get and show the error messages in the chat bot. If the page is able to navigate to the correct page, all is well. If not, meaning it throws an error, they want a way to get at those error messages. We also talked about helping to make better error messages to show what to do to fix things (make things more intuitive). They gave us an update and have optimized the memory functionality of the AI agent. There are now a number of users that can affect the global context (actual AI training) within the system.

After the meeting, Ted, Thomas, Josh, and I were talking about 3 buckets for our customers - low hanging fruit (those who are using it), those who could use it but aren't, and those who don't want to use AI. Ted was really pushing for us to try to get the people actively using it, even while we are training it. His focus is the commercialization process. We were talking about the need for data and feeding the AI agent. After that, we were looking at AI data and logs, encouraging people to keep going and ask for more (what else would you want from the AI agent - figure out what the customers are wanting). Somewhat of an outreach plan to help commercialize things to our customers.

Emails and quick fix for the Nxtlinq AI agent SDK file. Recording notes from the past couple of days (11/17/25 to 11/18/25).

The Nxtlinq guys are adding in more logs so that we can track some other things. They are working on a number of things including improved memory and global context stuff. Memory in AI is making training and knowledge stick. We also talked about a number of other topics. Here are a few of them:

- The costs for the infostructure and keeping the AI agent up and running.

- Talking about global information storage - we really need this, from our team to the bot.

- Talking about influencing things upstream and downstream. We need the AI bot to remember and learn, but we also have to be careful about where it gets its information.

- Light talks about an audio issue between multiple tabs. The AI agent is still listening in a different tab and responding. The simple work around is the mute button on the microphone. We may look deeper into this, if it becomes an issue.

- After the main meeting, Steve, Thomas, and I stayed on the meeting to talk about pricing and future plans.

- Being able to train the agent so that it can help with support, setup, and deployment. Figuring out the pain points and helping us as a company as well as our clients and users.

- Thomas was telling us some stories about introducing agents for other companies.

- Steve was talking about being able to help get the agent up and going and helping with oversight.

- Lots of talk about ingestion rates and values (how much we feed it).

- Human in the loop to help with the training.

- Thomas talking about manual crank windows (roll up/down the windows by hand) vs electric windows (power windows). Ideally, we show our clients and users how awesome it is with AI help. Then, hopefully, they won't want to go back to older tech.

- Getting into the BI level (business intelligence level) later on, as we go.

- If we train this agent up, it will really help our users and clients with training, consulting, etc.

- Here are our steps and phases for working with the AI agent - 1. Navigation and prompts, 2. Setup and training, and then 3. Clear out to consulting.

- Small phone call with Steve afterwards to go over our internal plan a little bit. Good meeting.

Meeting with the Nxtlinq guys. They were giving us some updates. They changed the word verify wallet to verify account. That will help out a bunch. They were giving us a number of other updates on things that they were changing and updating. We are all making good progress. They were making a few requests on and we were as well. Both sides and working well together. They are trying to get us some global admin permissions so that we can help and teach the agent. Lots of talks about ways to monetize things (we've got to pay for this thing). Steve, Josh, and Ted were heading that up. This is new territory for everybody. Anyways, the adilas AI agent (by Nxtlinq) was opened up (turned on and allowed) on every corporation and every server this evening. Here we go!

Quick phone call with Shari O. She had some questions about some sold inventory reports. Spent some time refactoring some code on the adilas third party action page. Removed tons of lines of code. Consolidated some of the sub API socket assignments into a function call.

Jumped on a meeting with Steve to go over some prep stuff for the AI agent launch. We were asking the ai agent to help show us some info. It didn't retain our last training session. It did, during the session, but then it didn't keep it long term or globally. Light AI training... see attached word doc - eventually, we want to make all of our documentation public and use it to train all of the LLM's (large language models). That would be super cool.

Working on cascading the code to get the Nxtlinq AI agent up and running for all corps. Added some code to the classic homepage to check for the AI agent. If the AI agent is not found, it auto adds it. That should help with new corps coming onto the system. Finished up the code to cascade the auto deploy of the AI agent to all servers and all corps. Pushed new code up and ran the update.

Multiple sessions throughout the day, all working on the AI agent launch. We are just a day or so out from the live launch. Here are a few of the things that I was working on today.

- Doing some planning for the day. We have a bunch of things planned to help with the AI agent roll out. Sat down at the table, away from the computer, and wrote out about three pages of notes. If I go right to the computer, I get an idea and just want to do it. Sometimes, it really helps to step away from the computer to do some planning.

- Started coding by adding in a new user level on/off switch for using the AI agent at the personal settings level. Tied that mini switch clear down to the login level of the application. Cascading code throughout the system to match the new setting.

- Working on bulk flipping the AI agent on for all corps. Tightened up the mini API to specifically look for the Nxtlinq web id to see if access is allowed or not. Read through a draft copy of a new entry from Cory for a news and update on the AI agent inside of adilas.

- More planning for a bulk update to help turn the AI agent on for each corporation and get the correct API sockets turned on as well.

- Checking code and then cascading database changes to all servers. Running updates to add the new user level setting for show/hide for the AI agent. Pushed up a couple of files and did some light testing on data 0.

Adding in some new corp-wide settings, to the local variable scope for the SDK for the AI agent. Sent a small note to the Nxtlinq guys with a few questions. Responding to some emails. Sending information back and forth with the Nxtlinq guys. Showing them some newly proposed corp-wide setting variables. Nineteen new variables for things like what to call the company entity, what to call your customers, your parts, inventory items, locations, etc. Basically, helping the AI agent speak the language of the corporation or company using the agent.

Meeting with the Nxtlinq guys. They have been removing the AIT validation stuff, at our request. It just makes it smoother. We are tracking and logging things inside the system already. They are also logging things based on the passed in user info. Here are some other notes from the meeting tonight:

- Maybe an internal survey to see what is important to them, security wise

- Shooting for a friction free environment for the users on the AI setup and usage

- Automation of orchestration and governing the management of the AI tools

- The launch is just the start. Then we finetune and optimize things as we go

- Possible customer services bots or agents monitoring support bots and prompts

- Talking about support and helping to see some automated options - less manual work - maybe use the AI agents to submit any support needs or bugs

- We talked a lot about prepping for a launch next Tuesday. We are planning on pushing the AI agent to all of our existing users. They don't have to use it, if they don't want to, but it will be turned on and available for all users.

- They, Nxtlinq, are going to do a quick video or series of gifs to help with the wallet link-up and verifying the user.

- Steve was saying that we will be trying to stay in front of our clients - prep what we can

- From Ted... our super users will become superhero users

- Small discussion about people - they need to use the new tools, or they will be left behind

- Ted was talking about the wheel. He was saying that AI will be as impactful as the wheel, in his mind.

- Helping our customers become believers

Quick meeting with the Nxtlinq guys. They were reporting on a number of enhancements. They now have complete audio options, no need to click the send button. They are wanting to get an Adi (our dog avatar mascot) image for the AI agent. Ted is really wanting to get the AI agent out to all of our clients. Even for free for the first little bit. Light talks about learning cycles and dedicated learning time for both us and the AI agent.

Some of the feedback that we are getting is that our clients want more deeper functionality... things like customer histories, PO's for specific vendors, and other more advanced look-ups and datasets. We have to start somewhere... we'll get there.

Meeting with the Nxtlinq guys. They had a small agenda and we went over it. Nothing too crazy. They are using a crawler to go over the help files. They did have some questions about some of AI quick search prompts that did not have a help file and/or would go to some other site or external reference. We talked about it and they are going to use their web crawler and get what they can.

Thomas from Nxtlinq was talking about their AI agent, they are calling NxtGPT (GPT stands for Generative Pre-trained Transformer - AI deep learning stuff). That seems like a cool name.

I may put in writing some of our requests with regards to the AI agent. We just want to turn it on and not have to verify or set permissions. Our application has built-in error handling and user permission checks on every page. If we have to do settings inside the system and inside the AI agent, our customers or clients might say no. Too much setup... Anyways, I will put some stuff in writing and we'll go from there. Basically, I'm going to say that adilas, as client of NxtGPT and Nxtlinq, we don't want the AI agent to require permissions. The adilas.biz application will take care of the permissions at the user per corp per page level.

They reported that they are ingesting the help files and pushing them over to the agent. That is awesome. There are over 500+ help files. That is awesome and will really help get the AI agent smarter on adilas stuff.

Lastly, I really want to read over some feedback that they, Nxtlinq, gave us from the last meeting. I briefly saw it, but want to really give it a better look over. That is mostly for me. Anyways, good meeting. I sent Steve a quick text after the meeting.

Meeting with the Nxtlinq guys. They went through our feedback (from Sean) and tried to duplicate and checkout any and all of our feedback that we gave them. That's pretty awesome. Some of the feedback was requesting complex or linked prompts. We know that the users want us to get there, but we have to take it one step at a time. We aren't there yet. We tried to provide them some answers and such. I think that it went pretty good. Talking about ingesting help files for the AI agent. Talking about re-verification of identities within the AI agent. We are making progress.

After the meeting, I was working on a newly requested combo prompt for starting a new cart and assigning a customer to the cart. Finished up the new advanced prompt. It looks like this: new customer cart assign [customer id] - Here are all of the cart prompts as of right now.

Meeting with the Nxtlinq guys. It was just Thomas and me. We briefly spoke for a few minutes and then jumped off. I then went in and disabled the user access that I had given them to the data 20 box. We will give them a different user login. Light clean-up and then a small email with an update.

Meeting with the Nxtlinq guys. Fairly quick meeting. Making some great progress. I reported that the multi-tenant options were available on all servers. I also reported on a number of new keywords and prompts. After the meeting, I spent some time and got one of the older accounts on data 20 up and running as a new test spot for the AI agent.

Emails and checking up on the proposal/questions sent over to the Nxtlinq guys. Working on some code changes inside the system. Added a dynamic server name to be passed through the AI agent code. Went in and added seven new API sockets to be turned on through the 3rd party solutions page for adilas API sockets. Sent an email to the Nxtlinq guys with a small update.

Somewhat of a long and technical email to the Nxtlinq guys. We need to make some decisions on how to proceed from testing to a multi-tenant type environment. I ran through a number of questions and tried to provide some possible solutions. We honestly can go in multiple directions. Hopefully I said that in a way that it wasn't too confusing.

Small clean-up for the day.

Doing a few random things. Data clean-up for Sean and a client out of California. Reading through emails. Recording notes from yesterday 10/16/25. Lots of good direction and ideas. Including info on creating your own aliases and AI quick search prompts. Lastly, working on an email... started a draft for the Nxtlinq guys. I ran out of time.

Phone call with Steve after our AI meeting. Going over tons of ideas and options... Exciting times.

- On the 3rd party solutions page, add in the other API's that Nxtlinq may need to access their data. Do this all behind the scenes so that a user doesn't have to go in and turn any of those settings on. That way, all of these API sockets will be monitored and controlled via the 3rd party solutions channel.

- We can handle the user level permissions - meaning allowing a user to turn the AI agent on/off at will. The corporation may turn it on, but not all users may want it. Basically, the corp level will be the top level and the user level will be on an individual basis level.

- Earlier today, we were talking about subsets of aliases - Steve had the idea... What about multiple levels deep? Aliases of aliases of aliases... We can totally keep it all strait but what if a user does something all the time... What if the AI agent was able to make its own aliases for common tasks. Talking about predictiveness and interpreting input and intent - We even talked about slang or certain terms that may be used in different regions.

- "Adi go" - command prompt - We already have "Adi" as our little blue dog avatar (helper or mascot). Maybe using "Adi" as a command prompt. This would be similar to how smart phone users can talk with Siri or Alexa. Ours would be "Adi". Idea from Steve.

- Sell what we have

- The value of hyperlinks - mixing command line, Gui interfaces, web, and API - we are built for this

After Steve and I got finished, I was wrapping up for the day. I was really grateful that everything was going good, meeting wise, direction, etc. I was saying a little prayer and had a number of thoughts pop into my head. Call it inspiration, direction, or whatever. I'll take it and I love it! Here are my notes:

- On the user set aliases (making their own prompts), for the AI quick search prompts, what if we used a "#" (pound or hashtag sign) for all user specific prompts. That would not compete with any of our existing prompts. For example: #xyz or #something or #somethingelse... - we could even reclaim certain existing prompts by just add the hashtag in front of it. Another example may be... The prompt or keyword for clocking in/out has an alias of "my time" - what if a user wanted to use that for his/her own prompt for project time tracking. They could create "#my time" or "#time" and it would totally work. Even though both of those values are normal keywords by themselves. It could be really cool. Imagin a hashtag and at least one letter, more if needed. Super simple for quick speed.

- Be able to build and show the prompts and what they are tied to. Simple user interface to setup and maintain their own AI quick search prompts. Very similar to the icon payee top links in the snow owl theme, but even more, and easier to get to... they would be clickable and usable in the AI quick search text fields. Anywhere in the system... That would be super cool! Even better than the icon payee top links (existing link building or special button feature inside of adilas right now).

- What if we used the "go mode" page (new AI quick search prompt page) to show their own prompts or even a fracture type interface - simple tiles and buttons - (small sample image)

- When creating your own buttons, be able to name them, color them, set an icon, a link (advanced - they have to know the URL or web link) or a simple quick search prompt. Maybe even tie the user created prompts and buttons together or make it a dual-purpose database action. Some of the buttons may need to open up a new window and some (most) will just jump to that new page. Just some ideas.

- What about being able to tie multiple prompts together in a mini list, process, or mini prompt recipe? That would be super cool. Imagine something like this: start cart, choose customer, show x or add y to the cart, simple cash checkout - simple English or natural language instructions and the system would help them walk through that process... kinda hold their hand. It won't just do all of them at once, but it will know what the process should be. We could easily create those one-to-many relationships and virtual steps or phases of the process. Just for fun, it makes me think of a data assembly line or assembly line for data. Cool stuff!

- Along this multi-prompt line... We already allow for duplicating invoices to the cart. What if we used a template type scenario and setup a master invoice and then were able to duplicate the exact thing in one click. If changes are needed, they could modify it, but cut out all of the searching and such. What about a partial duplication process... once again a mini recipe for certain steps or data assembly line controls.

- We have a page inside the current system called "my favorites". It currently has a number of buttons on that page. This was one of my todo list notes from a couple of days ago... It totally fits here (see below).

todo: Get back to the ideas of the my favorites page inside of adilas... it got taken over and a bunch of hardcoded buttons put on it. But it does have some potential. See this help file - help.cfm?id=418&pwd=favorites - or visit this page - top_secret/secure/my_favorites.cfm. Added this note on 10/14/25 - it would be so cool to let the users choose anything that they want in the system and then organize it and name it. Cody Apedaile started a draw your own interface (but got pulled off of it for budget reasons). Anyways, the goal is still there to help create your own interface and organize your own buttons as you see fit.

-  Super simple, using old school tech with a modern or new school flare... it will work

- What about helping with memory... We could help hold small comments, save/hold this or that, or even helping to string things together... Maybe help them with their memory... It won't tax the server very hard (store simple things in session - per login). Imagine small AI quick search prompts like clear memory, save to memory, view memory, etc. Super simple stuff. Use JSON storage if saving memory in a more long-term fashion. Simple interface to get things in/out of memory and even use the AI quick search field to help. That would be cool.

- This may not be ready yet - but what if we record and then help them go from one thing to the next to the next... simple session memory with a display... If we know a series of AI quick search prompts... It wouldn't be that hard to display something with a next button, help them step through the process.

Meeting with the Nxtlinq guys. Going over progress. Then talking about multi-tenant options (settings, domains, corps, keys, secrets). We setup some small dates and goals to get an MVP up and live. Other small talks on different subjects. Fairly quick meeting.

Meeting with the Nxtlinq guys. They have automated and worked with 350+ tools to date (adilas AI quick search prompts). We were talking about testing. Going over the auditability (following the audit trail) and tokenization tracking. We want it to be more loose and they want it to fully follow full block chain tokenization stuff. Functional testing vs real user experience testing. Talking about really beating things up. We are trying to get things done within about a week as far as all of the tools. We are shooting for sub 500 total tools. That means I have another 100 or so still to go before next week... I hope I make it... :) I've got a list, a plan, and a bunch of notes... What I don't have is time.

Making a plan. Went through a bunch of menus and found 30 or so homepages or sections that I want to add to the prompts list. Started working through my small list. Ended up doing some special coding to allow a vendor/payee id to be assigned directly to a new PO right from the AI quick search prompts. That should help out the Nxtlinq guys. Steve told me earlier today that they were looking for something like that.

Six different sessions throughout the day. Starting at 7:30 am and ending around 1:15 am (on the 14th). Long day. Here are a few of the things that we did.

- Working on help files and emails.

- More work on help files and navigation options. Recording notes from Saturday, big work session day. Back rolling through the additions, changes, and updates for the AI quick search prompts. More navigation and help options. Trying to expose some of the different resources like switching corporations and the developer's notebook.

- Working on new prompts for the API sockets and other key pages. Spending some time in the invoice and deposit sections. Things like apply payments, show invoice payments not yet deposited, sales tax reports, etc.

- Adding in a new payee lookup for the mini API, at Matt's request (from Nxtlinq). Started working on the new code.

- Working on some new code for a vendor lookup and an employee lookup for the mini API. Working on the code, testing, and pushing things up. More work on documentation. Then went to all servers and pushed up new database records for help files (10 new ones) and new permissions (7 new ones). Did that for all of the servers. Email to the guys at Nxtlinq with some instructions.

Meeting with the Nxtlinq guys. We showed them tons of new progress. We have really spent a ton of time in there (in the AI prompts and keywords) prepping the model. They had a couple of questions, and we had some good conversations. Bryan pitched a cost sharing model and then we got into some questions about the future of AI and where we see it going. The last 15 minutes or so were Steve and Thomas going over lessons learned and what each sees as part of the future.

Quick meeting with Bryan. He was doing some research for me on new AI quick search prompts to help round out the navigation section. He passed me over a bunch of things via the GoToMeeting chat. I'll try to work on them before tomorrow evening, meeting with the Nxtlinq guys.

Documentation and then working with Bryan again to get his new code implemented into the system. Lots of back and forth, testing, documenting, and pushing up code.

Meeting with the Nxtlinq folks. We presented on what we have been doing. I showed them some new stuff and all of the new prompts and documentation. Hopefully it is helping them out. I am happy with it. The new prompts are already making my life easier (I have been using them).

Meeting with the Nxtlinq guys. Steve, Josh, Bryan, Matt, Roger, and Vincent were on the meeting. We showed them some progress and sent them over some help file links. Mostly what we were able to show them was the new documentation stuff.

One thing that Vincent said that I liked was "Remove the friction". That should be our main goal in this venture. I liked that saying. If we could remove the friction on other parts, things would be even smoother. Without getting too technical, you have to have some friction, but making things smoother would be a plus. There is a balance point.

On the meeting with the Nxtlinq guys. They had a couple of questions. They want to know when we will get certain deliverables done and live. We also introduced Bryan Dayton as a new adilas team member on this project who will be helping Steve, Josh, and I. That should really help. Often, Steve and I are on all kinds of meetings and don't get the time to get everything done that we need to. Adding in Bryan to the mix should really help. We will work with him to help pass the vision and help direct him in the right ways. Good stuff.

After the meeting, jumped on a phone call with Bryan. Talking about next steps and setting up some time to meet tomorrow. After that, I sent a text message to Steve with an update about what we went over and when we are meeting next. I'm excited to see where things go.

Spent all afternoon working on AI options and prompts. I'm making tons of progress. Most of it is hidden right now but I will try to document it here soon. I want to get it working and tight enough before I get people to really beat it up. Uploaded some of the changes.

Meeting with the Nxtlinq guys. They were showing me some progress. We gave them 7 new prompts last meeting. They were showing how they can already use all 7 of those in what the AI agent can do.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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