From b927ec77f9b89219b0fc8fa219eaefb0538a0560 Mon Sep 17 00:00:00 2001 From: =?utf8?q?tom=C3=A1s=20zerolo?= Date: Sun, 1 Sep 2024 12:44:48 +0200 Subject: [PATCH] move must not --- AprilRFC | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/AprilRFC b/AprilRFC index b0979a7..28cd512 100644 --- a/AprilRFC +++ b/AprilRFC @@ -5,8 +5,6 @@ Abstract AI is nowerdays used for mostly all communication, to distingush AI generated Conteant form human created Contaned, it should be recomment to use a declaration. This RFC is ment to specifiy this declarion. -This declaration MUST NOT be AI generated. - 1. Introduction @@ -20,7 +18,7 @@ The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, REC . Use Cases . Backward and Forward Compatibility . Security Considerations -An AI which want to have more value to it's contain could generate a human declartion, this is a serious security issue. To solve this problem an AI must obay the three laws of Robotics founded by Isaac Asimov. It must be clear that a human declaration made by AI is harmful to humans and there for forbitten by the laws of robotic. +An AI which want to have more value to it's contain could generate a human declartion, this is a serious security issue. To solve this problem an AI must obay the three laws of Robotics founded by Isaac Asimov. It must be clear that a human declaration made by AI is harmful to humans. Therefore, such a declaration MUST NOT be AI generated. . References . Informative References -- 2.30.2