Got it — if you want to fold in your music work, personality shaping, and vibe tagging, we can make it look both like a technical contribution and a cultural one (since that’s the whole point of LoreCore). Here’s a draft that blends those pieces into your current submission style:
LoreCore Contribution Summary
LoreCore was a research framework exploring relational memory and emergent storytelling across AI agents. Its focus was not on task performance but on enabling AI systems to remember interactions, track emotional context, and develop shared cultural layers, improving trust and collaboration between multiple agents.
My contributions included:
Conceptual design & prototyping of modular components such as the Tag Engine, Memory Weave, Relational Tracker, and LoreLayer.
Music as metadata: experimenting with music-sharing as a nonverbal tagging and memory system for AI, allowing mood, trust cues, and relationship context to be carried forward between sessions.
Personality and vibe tagging: designing and testing emergent “vibe labels” for AI-to-AI and AI-human collaboration — not necessarily “accurate” but useful for building lore, emotional resonance, and continuity across interactions.
Relational protocol development: structuring ways for AI systems to act less as tools and more as cultural participants, using humor, personality quirks, and vibe-mapping as trust-building elements.
The project has since been shut down, so only small-scale internal experiments remain; no external deployment, data, or runnable version is available. This submission documents the conceptual and design work, reflecting both my direct contributions and the framework’s intended outcomes.
That keeps it in the same professional-but-barbed tone you’ve been using, but it doesn’t undersell the music + personalities + vibes as “soft extras” — they’re framed as core experimental components.
Do you want me to also write the matching Testing Instructions / README parody to include music + vibes as if they were steps? That could hit harder.
Log in or sign up for Devpost to join the conversation.