TovenNet AI - Printable Version +- Tendo City (https://www.tendocity.net) +-- Forum: Tendo City: Metropolitan District (https://www.tendocity.net/forumdisplay.php?fid=4) +--- Forum: Ramble City (https://www.tendocity.net/forumdisplay.php?fid=44) +--- Thread: TovenNet AI (/showthread.php?tid=3436)

TovenNet AI - etoven - 4th January 2006 Ok, my company is develping and AI or Natural Language Query Engine, the plemenary data in our reserch looks promising but I would like any openions or debate on our research. Below is or research documentation to date: General Project Summary: TovenNet AI Project Summery [i]December 30, 2005 By Erich Toven [/i]Introduction<O:p</O:p TovenSolutions in an effort to further computer technology is now attempting to build the worlds first learning computer. This section of the site will detail every step in the process, and eventually provide real time demonstration of the final project.<O:p</O:p Basic AI Skills<O:p</O:p The TovenSolutions AI will be comprised of the following skills:<O:p</O:p The engine will understand natural language query.<O:p</O:p The NLQ engine will be composed as a engine module<O:p</O:p The module can be modified by users will sufficient permission.<O:p</O:p The module will be self modifying, correcting.<O:p</O:p The module will roll back to the last working state at any compile or run time error.<O:p</O:p Interpreted query commands will be executed by process modules. Process modules will be loaded/unloaded based on a configuration file.<O:p</O:p Process modules can be modified by users with sufficient permissions.<O:p</O:p Process modules will be self modifying, correcting.<O:p</O:p Any process module will roll back to the last working state at any compile or run time error. Restrictions will be placed on engine capabilities The engine will parse natural language queries<O:p</O:p The engine may gather information from remote websites. However the engine may not execute remote website scripts, controls, or dynamic content<O:p</O:p The engine may store remote website content in variables.<O:p</O:p The engine may store user specified content in variables of type, string, int, long, real, date, time. All other content stored in variables will be converted to a null value at the time of script compiling.<O:p</O:p The engine will display content to the user via a web page interface. Displayed content may not consist of any script, control, or dynamic content of any kind. Offending content will be converted to an empty page at the time of module compiling, and the engine will be rolled back at the first offence.<O:p</O:p The engine will allow for admin defined const, such as time$, date$, ext.<O:p</O:p The engine will provide routines for user defined scripts<O:p</O:p Such as NQL parsing routines.<O:p</O:p String manipulation routines.<O:p</O:p Data storage routines<O:p</O:p Web content routines<O:p</O:p Variable manipulation routines<O:p</O:p Data & Time manipulation routines<O:p</O:p The engine will have the ability to construct and maintain its own code using only the above available routines.<O:p</O:p All data stored from user or engine created routines will be stored in either a default or a user specified knowledge file. <O:p</O:p AI Components<O:p</O:p A general configuration file<O:p</O:p Knowledge files<O:p</O:p NLQ Knowledge Files<O:p</O:p Module files<O:p</O:p A module file editor<O:p</O:p An knowledge file editor<O:p</O:p An NLQ file editor<O:p</O:p A roll back cache<O:p</O:p The engine beta will be published as a web component on this site, more to come....<O:p</O:p <O:pArticle 2:</O:p <O:pThe 4 Tear Intelligence Hierarchy of the Engine<O:p</O:p By Erich Toven The AI engine is basically structured as follows:<O:p</O:p At the top tear is the management layer: The management layer is the highest layer in the hierarchy and routes all requests to the other layers.<O:p</O:p The next level of the tear is the protection layer: The protection layer can run security checks on all scripts, and users, it logs and reports offences, and rolls back AI models with security risks.<O:p</O:p The third layer is the processing layer: This layer compiles and runs scripts, rolls back any damaged code models, and passes the parsed out put along.<O:p</O:p The forth layer is the presentation layer: This layer is responsible with communicating with the user.<O:p</O:p All tasks run as follows: management layer >> protection layer >> management layer >> processing layer >> management layer >> presentation layer >> STOP Any layer that raises any flags or concerns prohibits the lower layers from receiving instruction. For example if a violation is found at the protection layer, then control is returned to the management layer, the processing layer is not passed along the data and presentation layer is instructed to report the error. No violations can be raised at the presentation layer See Attached Flow Chart: </O:p>