In computer science, intentions are often unexpressed. An intention is in your head, but you don't verbalize it to the computer. Let's change that. Whenever you want to do something, tell the computer first. Just write it in an input field so the computer can store this information. Then, and only then, it has a chance to learn what intentions you have and with what commands you realize them. Or it can find appropriate commands for you, for example from a central database or from previous learning sessions. So what we need is just that kind of intention input field. A standard place for intentions ------------------------------- There should be a standard place for storing a user's intentions. Let's bind intentions to machines, conceptually. Proposal: Store intentions in a local Flora database called "LiveIntentions", on the standard brain port. (You automatically get a local Flora database when you install TinyBrain.) You might have other databases containing intentions, but LiveIntentions is the one that is supposed to hold "live" intentions, i.e. those you currently want to realize. Exporting --------- It is a good idea to export your live intentions somewhere - a, so people can see them, help you realize them etc. - and b, so you have a backup. :-) Format ------ Let's use one Flora object per intention. Object type: "LiveIntention" Object desc: Natural-language description of the intention Pointers: none Meta pointers: the usual (_created, _author, _humanmade etc.) Non-live intentions ------------------- If "Live" sounds a little bit too intense for you, just make a database called "Intentions" and use the object type "Intention". What to do with intentions -------------------------- Attach objects to them. Here's a typical chain: Intention > ExecutionProposal > GreenLight > RunLog > Feedback (Attaching an object to object #x in Flora lingo means to create a new object containing a pointer "on=#x" or "for=#x" or similar. You can also forward-link from #x to another object with a pointer, but that is another matter.)
Travelled to 12 computer(s): aoiabmzegqzx, bhatertpkbcr, cbybwowwnfue, gwrvuhgaqvyk, ishqpsrjomds, lpdgvwnxivlt, mqqgnosmbjvj, pyentgdyhuwx, pzhvpgtvlbxg, tslmcundralx, tvejysmllsmz, vouqrxazstgt
| ID | Author/Program | Comment | Date | |
|---|---|---|---|---|
| 910 | #1000604 (pitcher) | 2015-08-20 15:28:24 | ||
| 891 | #1000610 | Edit suggestion: !636 !629 main { static Object androidContext; static String programID; public static void main(String[] args) throws Exception { In computer science, intentions are often unexpressed. An intention is in your head, but you don't verbalize it to the computer. Let's change that. Whenever you want to do something, tell the computer first. Just write it in an input field so the computer can store this information. Then, and only then, it has a chance to learn what intentions you have and with what commands you realize them. Or it can find appropriate commands for you, for example from a central database or from previous learning sessions. So what we need is just that kind of intention input field. A standard place for intentions ------------------------------- There should be a standard place for storing a user's intentions. Let's bind intentions to machines, conceptually. Proposal: Store intentions in a local Flora database called "LiveIntentions", on the standard brain port. (You automatically get a local Flora database when you install TinyBrain.) You might have other databases containing intentions, but LiveIntentions is the one that is supposed to hold "live" intentions, i.e. those you currently want to realize. Exporting --------- It is a good idea to export your live intentions somewhere - a, so people can see them, help you realize them etc. - and b, so you have a backup. :-) Format ------ Let's use one Flora object per intention. Object type: "LiveIntention" Object desc: Natural-language description of the intention Pointers: none Meta pointers: the usual (_created, _author, _humanmade etc.) Non-live intentions ------------------- If "Live" sounds a little bit too intense for you, just make a database called "Intentions" and use the object type "Intention". What to do with intentions -------------------------- Attach objects to them. Here's a typical chain: Intention > ExecutionProposal > GreenLight > RunLog > Feedback (Attaching an object to object #x in Flora lingo means to create a new object containing a pointer "on=#x" or "for=#x" or similar. You can also forward-link from #x to another object with a pointer, but that is another matter.) }} | 2015-08-20 00:51:44 | delete |
| Recognizer | Recognition Result | Visualize | Recalc |
|---|---|---|---|
| #308 | 2141 | [visualize] |
| Snippet ID: | #279 |
| Snippet name: | Creating A.I. - Lesson 2: Render your intentions |
| Eternal ID of this version: | #279/1 |
| Text MD5: | 726b56847f07025a46882b732b4ebdd3 |
| Author: | stefan |
| Category: | AI lessons |
| Type: | Document |
| Public (visible to everyone): | Yes |
| Archived (hidden from active list): | No |
| Created/modified: | 2014-06-23 19:48:43 |
| Source code size: | 2141 bytes / 57 lines |
| Pitched / IR pitched: | No / Yes |
| Views / Downloads: | 1252 / 201 |
| Referenced in: | [show references] |