Bryan and Brandon looking around on the AI keywords, options, and prompts.

Date: 9/26/25

- make sure that Bryan has permission to do help files

- we have an element of time with a small list of ideas - EOT # 12286 in the shop
	- some have been done and some have not. this list was mostly a brainstorming exercise over a few days.

- The Nxtlinq guys are wanting options for doing the payroll

- Talking about part/item searches - there are quite a few variables or phrases that someone could use... training the agent

- a need for documentation - in the prompts, in the help files, etc.
	- bryan had the idea to help put some ai training into the help files, access to the sop's, steps, and simple flow that ai could consume

- we have built out a mini API - no one knows about it - we need documentation and a help file there as well
	- https://data0.adilas.biz/web/adilas_mini_api_calls.cfm
	- URL.useCorpKeyId or FORM.corp_key_id - pass in the corp key id value - Example: USE-0053 or Adi-22
	- URL.aiQuickSearch or FORM.ai_quick_search_field - search string or option/prompt value
	- URL.mode or FORM.mode - default is json, if passed in, it will show JSON. the other JSON option is to pass in mode="" (blank). if you want to show or dump the return object, use the following two possible options: mode=dump or mode=show - both of those will show the Adobe ColdFusion dump of the object (more visual vs the raw JSON).
	- there is already some documentation on the bottom of that page
	- the new help file is: https://data0.adilas.biz/top_secret/help.cfm?id=536&pwd=api
		- as a note... thinking of a super simple help file... then using code (with nightly auto deploys) to run the documentation that keeps changing	

- bryan had the idea... ask them to see if they like where we are going?

- some history... josh knows a guy who knows a guy... it was steve and josh and their connections... then they brought me in... i changed the direction a bit... now we are brining in bryan.

- questions on funding... bryan wants to know what is going on and who is funding what part. all we know at this point is the Nxtlinq guys are building stuff, we are providing things, and we have put over 150+ hours in on this project to date (as of 9/26/25).

- we have suzi building some step-by-step documents (SOP - standard operating procedures) for the cart. she is willing to do other things.

- we have added a bunch of new pages inside of adilas to help with this process.
	- https://data0.adilas.biz/top_secret/secure/ai_quick_search.cfm - super simple ai quick search page
	- https://data0.adilas.biz/top_secret/secure/ai_quick_search_prompts.cfm?action=goMode - ai quick search with all of the prompts by category

- there are three main help files... right now that need to be read through and updated... they may need quite a bit of work.
	- https://data0.adilas.biz/top_secret/help.cfm?id=535&pwd=ai - new ai quick search page with prompts
	- https://data0.adilas.biz/top_secret/help.cfm?id=376&pwd=quick - older classic quick search help file
	- https://data0.adilas.biz/top_secret/help.cfm?id=536&pwd=api - mini api

- need documentation about how to use the prompts... techy... this is how the ai agent can use the prompts, options, and keywords
	- URL help - https://data0.adilas.biz/top_secret/secure/search_action.cfm?aiSearch=new%20cart - this would be for new cart - you basically change out the aiSearch value to whatever is needed. For example: search_action.cfm?aiSearch=invoice%20home - this would be for invoice home. the %20 is for a space and the value needs to be URL or URI encoded.
	- FORM help - action="https://data0.adilas.biz/top_secret/secure/search_action.cfm" method="post" - the main input field needs to be named ai_main_search_field. here is an example:
	<input type="text" name="ai_main_search_field" size="50" value="" maxlength="255" class="form-control" autocomplete="off">
	- we may want to make a new help file to help prompt and setup the ai agents - prompt engineering - for us... use the A.P.E. style - action, purpose, expectation - instruction, context, input data, output indicator

- i have a number of new permissions for the quick search. they are currently only on data 0 and have not yet been made public. we need to open those up so that people can use them.
	- brandon has a plan - check old permissions and add new if related - run per server

- along those lines, on permissions, we need a new quick search permission for employee/users. this does not exist yet. we also need to come up with some prompts to help with navigation for this new section. along with that, we also need new documentation.
	- new permission id=183

- have a meeting with the minds (top level) vs the developers - steve, josh, bryan, brandon, thomas, ted
	- their devs - vincent, matt, and roger

- meet with steve - get direction and make sure that we are all going in the right direction
	- bryan has some billing questions
	- questions about billing for ai usage... available manually for free - charge for use of ai agent using the prompts and mini api