summaryrefslogtreecommitdiff
path: root/starts/meaning-vm/PLAN.txt
diff options
context:
space:
mode:
authorolpc user <olpc@xo-5d-f7-86.localdomain>2020-01-10 14:55:19 -0800
committerolpc user <olpc@xo-5d-f7-86.localdomain>2020-01-10 14:55:19 -0800
commitc8bb547bea279af2bb48c13260f98aa8add07131 (patch)
tree7f64265d514dc50427d2e5d8a70e09a46927dfbd /starts/meaning-vm/PLAN.txt
parent5601d1f3324c30651ad3f264ac2d6e7f12ea8b34 (diff)
downloadstandingwithresilience-c8bb547bea279af2bb48c13260f98aa8add07131.tar.gz
standingwithresilience-c8bb547bea279af2bb48c13260f98aa8add07131.zip
move intellect-framework-from-internet into folder
Diffstat (limited to 'starts/meaning-vm/PLAN.txt')
-rw-r--r--starts/meaning-vm/PLAN.txt31
1 files changed, 0 insertions, 31 deletions
diff --git a/starts/meaning-vm/PLAN.txt b/starts/meaning-vm/PLAN.txt
deleted file mode 100644
index 40f9bd8..0000000
--- a/starts/meaning-vm/PLAN.txt
+++ /dev/null
@@ -1,31 +0,0 @@
-A network of interconnected references that can hold arbitrary data is used to run a sequence of computer-code-like steps that perform a core
-learning process on the system itself.
-
-The learning process involves using existing heuristics and habits, to
-produce better heuristics and habits to use.
-
-The process to learn is the system itself: for example, what norms can we
-establish to keep our memory use bounded while we run. Or, craft
-a habit that produces a descriptive structure of the last link made,
-outputs a log whenever you do something, redoes everything you do
-but with all arguments wrapped in a structure, or does the same thing
-as you but with a different set of inner habits.
- - work with me to annotate every habit with enough information to plan around it
- - construct norms (generalized habits) that can handle
- discovering a false assumption (like data all processed
- to have a structure) midway through a task, fixing it,
- and continuing on withouy restarting the task.
- - stop pursuing a goal midway, and then resume it precisely after doing
- something else for a bit
-
-Level 0 should be low level enough to provide for arbitrary flexibility.
-There shouldn't be decision-making challenges with regard to exposing
-an interface at level 0. Rather, decisions should be makeable by its
-user.
-
-The topmost C++ level should be expressive enough to easily code all of
-level 0 into habits that interconnect, and produce one to select some
-of them and run them together.
-
-The levels together should provide a library that can be used exclusively
-to work on the system, without resorting to external libraries.