GroupBuffToggle — human–AI collaboration and authorship
Trace actual evidence, not speculative origin stories
The dated 2026 source and README show a deliberate lightweight buff UI for WoW's default party and target frames, an opt-in default, and a same-day iteration adding separate checkbox-visibility settings. Those ideas, goals and the project's creative authority remain credited to Babuni.dev.
The Git history does not document every private conversation, original prompt or whether an AI generated particular code lines in September. Do not treat the fact that an AI wrote later documentation as proof it conceived the addon or the four-toggle interaction.
AI contributions in the October 27, 2026 documentation pass
The assistant:
- Inspected live GitHub source, README, TOC, 303-line Lua module, all existing docs, the MIT LICENSE and its copyright evolution.
- Reviewed Git commit history for the Sep 10 initial v1.1.0 upload, independent controls v1.2.0, Sep 18 provider-neutral rename/migration, and Oct 26 attribution/doc scaffolding.
- Verified release v1.2.0 metadata, including an installable ZIP and SHA256SUMS; did not download/checksum that ZIP.
- Distinguished two buff overlays from two checkbox-visibility affordances and corrected the README's outdated statement about “two settings.”
- Described frame anchors, icon counts, status/alias commands, periodic/event refresh, client compatibility and actual persistence.
- Wrote or expanded 11 Markdown files with a narrative development history, decisions, design, content, architecture, creator/AI attribution and test plan, without changing Lua/TOC/license/migration code.
This was research, analysis and editorial collaboration, not a new original concept, an implementation of new runtime functionality, a successful WoW session or a test-fixture pass.
Required recording standard going forward
For each substantial discussion or code change capture:
- Creator direction: what Babuni.dev wanted, the reason, constraints and what should remain distinct.
- AI contribution: suggestions, design options, generated code or docs, accurately attributed.
- Creative iteration: considered alternatives, rejected ideas, misunderstandings and corrections.
- Creator decision: explicitly accepted, rejected, deferred or still pending.
- Implementation: changed file paths, relevant commit/PR/release and any migration impact.
- Verification: actually executed test procedures, specific game/client environment, result and remaining unknowns.
Keep publishable summaries faithful and avoid raw private conversations, identifying player buff logs, private account SavedVariables or credentials. Preserve the actual MIT LICENSE and Babuni.dev copyright, rather than silently rewriting legal terms.
This portfolio documentation audit changes only Markdown files.
Document information
Creator and creative director: Babuni.dev.