An embedded forth system sounds better as the user's knowledge base would have to be encoded in such as way it would be extensible and memorable. A computer key

An embedded forth system sounds better as the user's knowledge base would have to be encoded in such as way it would be extensible and memorable. A computer keyboards job in this case wouldn't be the end usage but a slave process to entering data in the host process for freeing up cognitive space for the user to delve in to their problem set. Some sort of mucking together of prolog and forth is what I'd imagine, a simple enough programmable stack builder constrained to the user's expressive capabilities while focusing on making new rules to constrain the host computer's usage. The role of the keyboard is to prevent the main computer from deviating from the user's focus in the problem solving session of input and retrieval (I/O).