.
FRDCSA | minor codebases | Execution Engine
Homepage

[Project image]
Execution Engine

Architecture Diagram: GIF
Code: GitHub

Jump to: Project Description | Parent Description | Capabilities

Project Description

The Execution Engine has for instance a tool that watches over one's shoulder to see the commands they are executing, and prompts them regarding whether they really intend to execute it, or whether a particular situation that triggers other actions has come up. For instance, if you are rushing, it prompts you to slow down. Ideally it will eventually use Prolog-agent to determine the consequences of shell-commands, and trigger on anything potentially harmful and bring it to the user's attention. Also will try to implement plan recognition so that Execution Engine can help detect and achieve good goals and detect and block bad goals. What is good and bad is a question worth looking into, but a simplistic notion for now might be something like, don't delete files for which the particular file(s) is the only known copy. Just general sanity. It's capabilities are not limited merely to interceding as needed, however. Will list more capabilities soon. Supersedes the system/index.html">action-system project.

Capabilities

  • rsr should work with execution-engine
  • Make the SPSE2 system have a component associated with normal-form which associates tasks to be completed with rewards for completing them - then integrate the normal-form and execution-engine permission systems.
  • For verber and the life planner and the execution monitor and execution-engine, there should definitely be a bunch of agents monitoring the situation and trying to work things out from it, such as unforeseen stuff. For instance, could have a video card dedicated to it. Short term contingency planning.
  • Fix execution-engine.bashrc so that it does it again.
  • Brainleach should make use of the execution-engine stuff for hooking the shell.


This page is part of the FWeb package.
Last updated Sat Oct 26 16:36:55 EDT 2019 .