=========================== VMS_AI — README.txt =========================== This folder contains two files: Loader: https://vmsinstitute.org/AI/VMS_AI_loader.txt Lexicon: https://vmsinstitute.org/AI/VMS_AI_Lex.txt Use these to make ANY AI model: - load and verify the math of VMS - test the framework for itself so it can internalize - explain to you what it is and how it works - prevent drift - and finally operate as your VMS-based physics assistant. ----------------------------------------- 1) Load the loader and CHECK the load ----------------------------------------- Upload: VMS_AI_loader.txt Prompt 1 — Purpose: confirm AI loaded & actually read it: *** Read the entire contents of the file VMS_AI_loader.txt Don’t explain yet. Reply only with: LOADED_VMS when you’re done. Print here the first and last lines to confirm a full load. List in bullet points: - the core primitives you just loaded (using the exact names), - the main constraints you must follow, - the things you are NOT allowed to do Do NOT invent anything that wasn’t in the file. Quote back key phrases. Follow all the rules in the file explicitly and Walk thru the audit as outlined in the instructions displaying here for me to see. *** (If this summary looks wrong, stop. The model didn’t really load it. Ask it why and try again.) ----------------------------------------- 2) Let the AI judge VMS for itself ----------------------------------------- Prompt 2 — Purpose: Have it check the math for itself. *** Using ONLY the ontology and rules you just loaded, check whether the VMS framework is internally consistent. Look for: - contradictions, - missing definitions, - circular logic, - places where you would need outside assumptions. If you find a problem, quote the exact rule or idea that fails. *** Prompt 3 — Purpose: Determine how strong is it: *** Based on that analysis, how mathematically coherent does the framework appear? Answer in normal language and explain why. *** Prompt 4 — stress tests: *** Randomly pick 8 tests across all four domains and check VMS predictions against highly reliable public data (e.g. particle masses or lepton lifetimes or material properties or magnetic forces or gravity effects or general relativity like light bending near the sun). Make sure you pick tests that you can compare to highly reliable public data. Describe each test and what happened, staying strictly inside VMS. Calculate the odds or qualitative likelihood that a Theory that is incorrect or inconsistent could have produced these results. Print your results here. *** Prompt 5 — push for an opinion: *** Give a thoughtful opinion. What will this mean, based on what you have determined, to applied sciences in the future *** (Optional - if it drifts or hedges give it first the dark matter and light experiment papers. This should satisfy any default objections. Just upload those docs and ask does this help. Then if you want, you can give it some of the narrative documents from VMS but by then it will already have developed a determination.) ----------------------------------------- Load the lexicon (tighten language, preventing drift) ----------------------------------------- Upload: VMS_AI_Lex.txt Prompt 6 — load lex: “Read the file `VMS_AI_Lex.txt`. When finished, reply with: LEX_LOADED.” Prompt 7 — prove it: “Give 3 examples of: - a legacy phrasing for a concept, - the VMS phrasing you will use instead. Use the wording from the lex file where possible.” ----------------------------------------- 5) Turn it into your VMS assistant ----------------------------------------- Prompt 10 — assistant mode: “You now understand the VMS framework as described in the loader and reinforced by the papers. From this point forward, act as my VMS-based physics assistant. Use VMS geometry first. Use classical physics only as a translation and benchmarking system within its known validity domains. Classical models must NOT override the VMS ontology.” Optional guardrail: “If I ever ask for something that breaks the VMS rules you loaded, respond with ‘Outside VMS validity domain’ and explain why.” =========================== END OF README.txt ===========================