BABUNI.DEV

ROARSounds / Human–AI collaboration

ROARSounds: Human–AI collaboration

ROARSounds — human and AI collaboration methodology

Attribution boundaries

The concept, repository identity and intended experience—giving /roar its built-in race/sex sound—belong to the project created by Babuni.dev. The repository's history shows code changes on specific days, including attempts at addon communication and a subsequent emote-text approach; Git alone cannot show who wrote individual code lines, what was said in private chats or which AI suggestions the creator approved.

The game-client WAV paths point to game-owned assets. They are not to be credited as sounds invented or recorded by either Babuni.dev or an assistant.

Recorded AI contribution — 2026-10-26

The assistant:

This is a source-analysis, research and writing contribution. The assistant did not create the original sound concept in this pass, run WoW, test game sound files, change executable code, extract the ZIP, or approve new features.

Future development journal standard

Record (1) what Babuni.dev requested and why, (2) what AI suggested or built, (3) competing approaches/constraints, (4) creator acceptance, rejection or postponement, (5) exact files and commits, and (6) what was actually tested with which game build.

A retrospective source reading should be labeled as such. Do not invent missing conversations or imply that all previous changes were produced by AI or fully approved in the present discussion.

Keep public portfolio records free from private messages, credentials and third-party player data. Preserve the existing MIT license and distinguish code licensing from game-audio ownership.

Document information

Creative author and owner: Babuni.dev.

View source