MaidCom Project Thread 2 Project Goal: Simple, low cost, extensible platform for robowaifu development. Picrel shows the model which is being developed. Every part will be designed to be easily printable and replaceable. Her designs will be open source. Modding and customization will be encouraged. This is a base model. Early revisions will be heavily limited in functionality. I invite you to help design and define standards so that it is easy to create specialized add-ons to allow her to become your own waifu. Collaboration is important, MaidCom is officially partnered with Lin and his Waifu Wheelchair, if you'd also like to be officially partnered, say so. Cat eats and miniskirts are encouraged! <--- Previous thread: ( >>15630 ) >=== -add crosslink

Your project is really disgusting >=== Notice #2: It's been a while since I locked this thread, and hopefully the evil and hateful spirit that was dominating some anons on the board has gone elsewhere. Accordingly I'll go ahead and unlock the thread again provisionally as per the conditions here: >>12557 Let's keep it rational OK? We're men here, not mere animals. Everyone stay focused on the prize we're all going for, and let's not get distracted. This thread has plenty of good advice in it. Mine those gems, and discard the rest. Notice:

>Why organize IRL? This community is great and many individuals are already making progress on their prototypes. However this endeavor is not a one man job and organizing IRL would give better opportunities for collaboration and skill sharing/development. >Where should we organize? I propose we organize within a seven hour radius of Chicago. This would include the major cities of Milwaukee WI, St Louis MO, Detroit MI, Indianapolis IN, Louisville KY, Cleveland OH, Cincinnati OH, Columbus OH, Pittsburgh PA, Nashville TN, and Minneapolis MN. There are plenty of opportunities for jobs and universities in these cities. In particular Chicago has a booming tech industry with Google even moving their HQ to the city and the electronics manufacturing and biotech sectors are pretty good too and Detroit MI has pretty good robotics industry although it might not be the best place to live. Another wonderful thing about this area is that most of these homes have basements that could be turned into workshops. >How would this all be organized I propose a fraternity system. A fraternity would help build community and give us a vehicle to recruit others from STEM and skilled trades (machinists especially) The organization could also host a scholarship to help us build talent. Anons with enough money for a down payment could buy homes in the area and rent to below market rate to anons moving in. Different homes could specialize on different projects and collaborate and share equipment and skills with others nearby. What do you think /robowaifu/?

I think we need to figure out how to fit a womb onto a waifubot. Where's the fun in having sex if you can't procreate?

Repost from a thread on /b/;
>"If you're like me and want to fuck a qt battlebot and get her pregnant, the best place to put an artificial womb is where a normal womb would be on a normal girl. The metal exterior could simply be a bunch of metal plates that unfold to allow space for the womb pod inside. The baby is probably safest inside the battlebot, and if she has good calibration then there shouldn't be problems with her falling and hurting the baby. After giving birth the metal plates could automatically fold back up again, shrinking the womb pod inside so she is combat effective again."

Well /robowaifu/? Feasible?

This thread is for the sharing of robo waifu banners. As per the rules, fallow these requirements: >banner requirements: File size must be lower than 500 KB and dimensions are 300x100 exactly. Allowed file formats are .jpg, .png, and .gif. >=== -fmt cleanup

I generated a whole much of neat images with Stable Diffusion 1.6. Enjoy. You are free to use the for whatever. >OP images are my five favorite of the bunch. Some proportions are off obviously. < "a robowaifu with [color] hair, digital painting, trending on artstation" Was the generation phrase. --- >Sorry to spoil all your files, rather than just the one (w/ Lynxchan it's all or nothing after the fact). The Problem Glasses are a Leftist dog-whistle that is rather distasteful around here (and also a red-flag). Certainly not something we would want to look at year-after-year in the catalog. Hope you understand, OP. ** Probably best to limit it to image generation, but also tolerating clips. Anything more advanced goes into the current propaganda thread : (>> TBD) . >=== -edit subject -add footnote -temp. locked to abate derailment => reverted

The original thread can be found here: https://trashchan.xyz/robowaifu/thread/595.html --- Welcome to the Lemon Cookie thread, The goal of Lemon Cookie is to create a framework where a synthetic "mind and soul" can emerge through a "LLM as cognitive architecture" approach. This thread exists to collect feedback, ask for help & to document my progress. First I am going to try to give a high level overview of how this cognitive architecture is envisioned and the ideas behind it. I have spent time looking at cognitive architecture work, in the field there is now a consensus on how the mind works at a high level. An important mechanism is a "whiteboard", basically a global temporary memory that all the other systems read in and out of. Then there is different long-term memory systems that react to and add content to the whiteboard. Along with memory pattern matcher(s)/rules work on the content of the whiteboard. A key thing to consider is the difference in philosophy that cognitive architecture projects have, the intelligence is considered to emerge from the entire system. Compare this to LLM agent work where it's considered the intelligence is the LLM. My feelings on the general LLM space are conflicted, I am both amazed and really disappointed. LLMs possess an incredible level of flexibility, world knowledge and coherence. But everything outside of the model is stagnant. It's endless API wrappers & redundant frameworks all slight permutations on RAG & basic tool calling. I will believe that LLMs are misused as chatbots, simply put their pattern matching and associative power is constrained by chat format and shallow tooling. In the Lemon Cookie Cognitive Architecture so far here are the important aspects: 1. Memory is difficult. I do not think there is a singular data structure or method that is able to handle it all, several distinct types of memory will be needed. So far I plan for a PathRAG like system and a "Triadic Memory" inspired system for external associations (this is missing in most LLM solutions). 2. LLM as Kernel, The LLM's context window is the Whiteboard and has a REPL like mechanism. It holds structured data and logic in scripting-like format so it's both LLM & Human readable while staying easy to parse & allows for expressive structured data. The LLM's role will be to decompose data and make patterns and associations explicit as executable statements. 3. The language has to be LLM/CogArch-centric. There is a thousand ""agents"" that give LLMs a python interpreter as a tool. The two need to be more tightly coupled. Scripted behavior via pattern matching, The whiteboard is a bag of objects, this allows for programmable pattern matching (think functional programming like Haskell). It's also important to allow the LLM to observe code execution and to be able to modify state and execution flow. Data in languages have scoping rules, so should LLM context. Etc... I will go into more depth about the language in another post. 4. Another important system is the "GSR" Generative Sparse Representation and it will be a first class language & runtime type, This also needs its own post. But in general I am inspired by two things, "Generative FrameNet" paper where an LLM & an embedding model is used to automatically construct new FrameNet frames. The second source is "Numenta's SDRs"/"Sparse distributed memory" this representation has a lot of useful properties for memory (Please watch the videos under the "What the hell is an SDR?" segment in my links list for an easy introduction.) I think SDR unions & SDR noise tolerance will be especially useful. 5. A custom model, For all of the above to work well, a model will need to be fine tuned with special behaviors. I do want input on this. Baking facts & behaviors into LLM weights is costly, creating bloated models that are hard to run or train (why memorize all the capitals?), while letting authors gatekeep truth and impose "safety" detached from context. Blocking role-play "violence" or intimacy isn't protection: it's authors hijacking your AI companion to preach at you. Externalizing behaviors via whiteboard pattern matching shifts control: stabbing you in-game can be funny, but a robot wielding a knife isn't. Maybe you want intimacy privately, but don't want your AI flirting back at your friends. When put together I think this will be able to host a kind of synthetic "soul", In a living being what we call a personality is the accumulated associations, learned behaviors, beliefs and quirks molded by a unique set of experiences. I hope this will be true for this system too.

Power & Energy Robots require some form of energy to power them. We need to understand how to store energy in a way that will provide her with all the power she’ll need. To clarify, “energy” is a system's capacity to do work over time. This is measured by Wh, or Watt hour. Closely related is “power” the rate at which work is done. This is measured as W, or watts. As an example, we could have a robot with a 80Wh Lithium Ion battery and two DC gear motors that consume 10W when working. You do not need to rely solely on batteries and motors. We can use other methods of storing energy. This can include compressed fluids, thermal energy, and light, among other things. For instance, glow in the dark paint is useful for storing energy to use at night for safety. Solar panels or a generator can provide power through the energy of long distance nuclear fusion or extracting energy from some reaction. Being part of a robot means we need to consider safety, mass, and volume. How will her energy and power system fit inside her? How will she deal with the mass? What happens when she runs out of energy? How can you minimize her energy use? What alternatives can be used to lower her cost of production and ownership? These rhetorical questions are all important when contemplating how to build a robot.

Tensegrity Thread Tenssegrity is the purposeful application of tension in a system of non-contact components to provide integrity. These components effectively float on compression provided by tension elements. Tensegrity structures are often formed via rigid rods with a cable defining the spatial relations of the system. Picrel 1 is NASA’s Super Ball Bot, which uses the common 6 bar structure. By altering the lengths of the rods, the “ball” can roll. Please see (https://www.nasa.gov/image-article/super-ball-bot/) Our bodies use tensegrity to provide us with incredible strength, durability, and adaptability. Consider how when you bump into something or fall, you can feel the pressure dissipate throughout large parts of your body. This is due to your muscles, fascia, ligaments, etc… transferring the force throughout your body, protecting the impacted part. You can walk with little effort thanks in part to tensegrity. Your legs joints are all floating, providing low friction movement while distributing the force of impact throughout your entire leg when you step. Please see (http://intensiondesigns.ca/geometry-of-anatomy/) Tensegrity can also be made with elastic elements. These structures are what I believe are best suited for our endeavors. They provide looser tolerance requirements and give her body some squeezability. By incorporating naturally stretchable elements, she can better withstand having an Anon using her. (I speak from experience, though I still broke that torso before taking pictures.) Though there are drawbacks. These designs are deceptively difficult to design correctly. Our requirements for external aesthetics provide unique design requirements that complicate the design phase. I still believe using this concept is objectively correct for us to pursue. A good example to build off of (Debatable whether or not it’s true tensegrity): https://www.thingiverse.com/thing:4182634

This thread is for discussion, warnings, tips & tricks all related to robowaifu privacy, safety & security. Or even just general computing safety, particularly if it's related to home networks/servers/other systems that our robowaifus will be interacting with in the home. <---> /robowaifu/ 's standard regarding a robowaifu's physical safety : ( >>38561 ). --- > thread-related (>>1671) >=== -update OP -broaden thread subject -add crosslink -add safety-standard crosslink