is it too much to ask for some feedback? reddit, locals, coding forums and main stream sites banned or shadow banned me. just for saying this is a new software design pattern , please tell me what you think about it.
I try and I try and I just get banned everywhere. stifled.
anyways this is a summary of the project:
I don’t know about you, but I am not OK with corporate AI!
I am not cool with: an LLM telling me something is inappropriate getting her opinions from corporate news sites adding silly disclaimers censored speech banned words spying on me saving data on some cloud my cup of tea is an offline localized modular AGI.
LivinGrimoire is a software design pattern that lets you absorb powerful skills instantly. Just one line of code per skill.
Need Image Recognition, Speech, Robotics, weather updates, alarms, reminders, or LLMs? Simply add the skill file to the DLC folder. It’s like how Neo learned Kung Fu in The Matrix—the skill is loaded directly into the LivinGrimoire.
Here’s the ultimate simplicity:
To add a skill: One line of code. To toggle it off: Comment that one line out. LivinGrimoire handles the rest: This software design pattern connects the skills, prioritizes algorithms, and queues its tasks on its own.
Initial Set up only includes copy-pasting one directory into your IDE.
It’s fully multi-language, working seamlessly with Java, Kotlin, Swift, C#, C++, Python, VB.NET, and more.
This is the absolute laziest and simplest way to program.
Initial Setup Add the LivinGrimoire core directory (for your chosen language) to the project. Include the main file (recommended loop for the AI think cycle). Create a DLC directory and place the personality file inside. Usage Add skill files to the DLC directory to load them into the AI. Modify the personality file in the DLC directory: Add a skill with a single line of code. Comment out a line to toggle a skill off. Run the main file. Note This is a development kit, not a standalone application. Run it inside your IDE. Refer to the livingrimoire github wiki for additional features and detailed documentation.
I remember you talking about this a long while ago. I tuned out because it made absolutely no sense to me, and trust me, I really tried.
It reminds me of the Temple OS guy.
this is a design pattern by which the user adds any skill/feature/ability to the system with 1 line of code. it has many more features as well. its not fair for you to say it makes no sense without properly articulating the specifics of what makes no sense to you.
That’s not a pattern. That’s an extremely basic list of required knowledge.
You realize most projects already document what you need to be familiar with? It’s called dependencies.
Okay, I’ll bite. Can you link me to documentation that defines what a skill/feat/ability is in this context? It’d be helpful if you have some code examples of what this pattern looks like. I’ll take a look again.
https://github.com/yotamarker/LivinGrimoire/wiki a skill is a subclass of the Skill class. https://github.com/yotamarker/LivinGrimoire/wiki/Incantation-0-LivinGrimoire-experiment
If you’re enjoying working on this project, and learning new things, then I’d never want to discourage that. That being said it’s far too esoteric for me, so I’m once again out.