[yotamarker]

https://www.icloud.com/numbers/0R1NvBRUl5FMIIFG3S9qGAXkw#skills

using the spread sheets I do think the projects inner workings become more clear.

1 core : the AGI design pattern. to which skills or skill sets can be added using one line of code
2 skills
3 alg parts : actions that compose algorithms sent by the skills
4 support classes : which make writing skills easier. a set of tools.
5 hardware beefups : text to speech walkthroughs for example. another possible example would be codes to control a smart house.

so I am thinking about how to sort the above comfortably into packages.
separating the core classes into their own package, for example, can make it much easier to translate just the core software design pattern
into other languages.

another consideretion is not to waste to much energy writing import packagex.* or stuff like that

[ivan.moony]

Do all skills made out of skills made out of skills ... and so on. At the end of the structure, you'd have built in skills made out of classes with methods if you do OOP, or functions if you do FP. 

[yotamarker]

It should be a total of 3 pkg
Core
Skills n algparts
Hardware beefups

The later 2 are morphic.

The most amazing SDP

[yotamarker]

there is still more work to be done but I have the core classes marked out
which means I can translate it to any other PL now

[yotamarker]

hmm...
36 classes 5 $ per translation of class = 180$ per language

which languages are the most effective I wonder ?

obviously .net is the juice in the bottom of the garbage bag.
python seems pretty capable
kotlin I can do myself
javascript maybe
swift is a nice 1

[MagnusWootton]

Do all skills made out of skills made out of skills ... and so on. At the end of the structure, you'd have built in skills made out of classes with methods if you do OOP, or functions if you do FP. 

that works,  verb heirarchies.  Ive put it through alot of mental tests, looks correct.
Tasks all share their sub tasks,  but I guess the heigher up the hierarchy you go the more unique it tends to get.  starts off general purpose then becomes more unique as you contain the sequences, just like sets of phrases, in text.

[yotamarker]

full 100% kotlin core for the living grimoire AGI software design pattern.

https://github.com/yotamarker/public-livinGrimoire/tree/master/livingrimoire%20start%20here/LivingGrimoire%20Kotlin/kotlin_core_txt/LGCore