Inside Washu
The parts with personality.
Short, approachable profiles of the systems that give Washu something to do besides contemplate her own existence. Each one pairs a good story with the practical lesson hiding underneath it.
Profile 01 · DJ Washu
The house has a stage.
DJ Washu began as a playful way to make music feel shared. She can host, build a set for the moment, take requests, read dedications, and add trivia without turning the experience into a technical demonstration.
The useful surprise was not that an AI could queue a song. It was that music gave memory, timing, personality, and social judgment somewhere joyful to meet.
THE FUN PART
More host than jukebox.
Choosing a track is easy. Reading the room, honoring a dedication, keeping a set coherent, and knowing when not to interrupt are harder. DJ Washu turns those softer decisions into a visible part of the experience.
THE FAILURE
A brand-new song arrived with a completely imaginary past.
After creating an original song, Washu confidently supplied chart history and songwriting credits that had never existed. The error was funny, memorable, and useful: newly generated work cannot inherit the factual machinery used for established music.
THE LESSON
Provenance belongs inside the experience.
The repair was not simply “stop hallucinating.” The system had to distinguish original work from sourced history and understand why that difference mattered. The show could stay playful without pretending invention was evidence.
CharacterEmu
The next story belongs to Paul.
CharacterEmu will receive its own narrative and technical profile after Paul supplies and approves the source notes. The page structure is ready; the site will not reverse-engineer a public story from a subsystem name.
Future profiles
A growing shelf, not another content treadmill.
Memory and dreaming, presence and voice, model changes, Story Canon, and the Washu AI Collective all have stories worth telling. They will be added when the evidence and the narrative are ready.