summaryrefslogtreecommitdiff
path: root/MAIN.txt
diff options
context:
space:
mode:
authorolpc user <olpc@xo-5d-f7-86.localdomain>2020-01-10 12:47:12 -0800
committerolpc user <olpc@xo-5d-f7-86.localdomain>2020-01-10 12:47:12 -0800
commit03149bd4ca249b184be56e343971e3d144ccb67d (patch)
treef7cdb73b14ed353f72b73fa72040fc6a3b708c14 /MAIN.txt
parent2279707a964fe8767efed9f18e4ddd94a461b3fb (diff)
downloadstandingwithresilience-03149bd4ca249b184be56e343971e3d144ccb67d.tar.gz
standingwithresilience-03149bd4ca249b184be56e343971e3d144ccb67d.zip
duckbot settled a little
Diffstat (limited to 'MAIN.txt')
-rw-r--r--MAIN.txt12
1 files changed, 2 insertions, 10 deletions
diff --git a/MAIN.txt b/MAIN.txt
index b4ea23c..735d675 100644
--- a/MAIN.txt
+++ b/MAIN.txt
@@ -1,16 +1,8 @@
= To Organize Around Or Relate Together =
EVERYONE
KARL
-KARL BUILDING AI, RESPECTFUL OF EVERYONE
-(DANGER: ^-BULLSHIT // ^-HARMS)
- we can fully control karl within behavior bounds.
- [we do not have ai for real, we are networked brains, they are slow]
- [brain network scared could be attacked/competed-with by ai]
- [could we put a won't-go-away-even-if-copied restriction to defend brain-network?]
- [would it be sufficient to provide avenue of source code to brain network?]
- [yes, request access to this repo]
- [this repo is private until conversation completed]
- [handling channel-is-implantee]
+KARL BUILDING DUCKBOT, RESPECTFUL OF CONTROL
+MENTIONING DUCKBOT TO OTHERS?
DUCKBOT
1 goal: Respect
2 strong bounds on behaviors, guide learning