WorkThatGodBod: Human–AI collaboration

WorkThatGodBod — human/AI contribution and provenance

Authorship without invention

Babuni.dev's project defines a low-friction reminder experience situated in World of Warcraft and a distinctive fantasy-inflected writing voice. The repository README, source and Git commits establish the project's published goal and technical history, but do not preserve every original human instruction, AI proposal or decision conversation. Do not credit an original idea to AI simply because AI helped explain, document or later modify code.

The current 99-line source corpus may have been revised through collaborative processes; the available Git diffs alone cannot assign authorship of each metaphor or exercise suggestion to a person or model. Do not invent that ledger.

The documented 2026-10-26 AI contribution

The assistant:

• Inspected the live README, Lua, TOC, MIT license, documentation scaffold and representative dated commit diffs.
• Recovered the transition from one slot to multiple slots and from plain prompts to fantasy writing.
• Counted 99 current prompts and precisely calculated the current outbound chat distribution.
• Identified important divergences between old README descriptions and actual v1.1 source.
• Drafted and committed expanded Markdown documentation and flagged creator decisions for future work.

These are technical analysis and editorial contributions, not evidence of new feature approval, implementation changes or gameplay test success.

Responsible presentation

User-facing documentation must plainly say that some prompts are transmitted to other players, and that the tool does not provide individual medical advice or track completed exercises. Preserve the MIT copyright credit and Babuni.dev author identification. Never publish private health information, player chat logs, credentials or unapproved raw conversations to GitHub as part of the development journal.

What every future change record should capture

1. Creator direction, reason and constraints.
2. AI suggestions, assumptions and considered alternatives.
3. Explicit approval, rejection, postponement or correction from Babuni.dev.
4. Changed files and linked commit/PR.
5. Tests performed, environment, expected and observed outcomes.
6. Remaining uncertainties and potential user-facing consequences.

When documentation is reconstructed after the event, label what can be proven by source and what is only an editorial interpretation.

Document information

Human creator and creative director: Babuni.dev.