JonKazama-Hellion/HellionChat
1
0
Fork 0
Code Issues Pull Requests Actions Releases 28 Activity

Clarify that AI involvement varies by area and over time

Browse Source 
The earlier wording could be read as "Claude wrote all Hellion-
specific code." Pair-level assistance doesn't mean uniform AI
authorship — some commits are mostly hand-written with the AI as a
sounding board, others lean on it for API walkthroughs or drafts
the maintainer then edits. Spell that out, and note that the share
of hand-written work is expected to grow as the maintainer's plugin
experience grows.
This commit is contained in:
Jon Kazama
2026-05-01 21:40:12 +02:00
parent ebf58cb916
commit eaf3e79c96
1 changed files with 20 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AI_DISCLOSURE.md
+20 -9
View File
@@ -1,19 +1,30 @@
# AI assistance disclosure
Per the [Dalamud Plugin AI Usage Policy](https://github.com/goatcorp/DalamudPluginsD17/),
this fork uses AI assistance at the **Pair** level: the maintainer plans,
reviews and integrates every change and tests it against a running game
client; Claude (Anthropic) helps explain Dalamud APIs, suggest patterns and
draft code on request.
this fork uses AI assistance at the **Pair** level. Pair means the maintainer
plans the architecture, decides what gets built, reviews each change and
tests against the running game; Claude (Anthropic) helps explain Dalamud
APIs, suggests patterns, drafts code on request, and reviews approaches.
Neither side acts autonomously: nothing ships without the maintainer's
review, and Claude can't run the game.
The level varies by area and over time. Some commits are mostly hand-written
with the AI used as a sounding board, others lean more on Claude for an API
walkthrough or a code draft that the maintainer then reads, edits and
integrates. The maintainer's commitment is to be able to explain why every
piece of Hellion code is the way it is — not "I typed every character."
## What's where
Upstream Chat 2 (by Infi & Anna, EUPL-1.2) is the foundation and was not
produced with AI assistance. Hellion-specific code — `ChatTwo/Privacy/`,
`ChatTwo/Export/`, `Resources/HellionStrings*`, `Ui/SettingsTabs/Privacy.cs`,
`Ui/FirstRunWizard.cs`, `Ui/HellionStyle.cs`, the Migrate3 recovery and
plugin layout migration in `MessageStore.cs` / `Plugin.cs` — was written
with Pair-level assistance.
produced with AI assistance. Hellion-specific code lives in
`ChatTwo/Privacy/`, `ChatTwo/Export/`, `Resources/HellionStrings*`,
`Ui/SettingsTabs/Privacy.cs`, `Ui/FirstRunWizard.cs`, `Ui/HellionStyle.cs`,
plus the Migrate3 recovery and plugin layout migration in `MessageStore.cs`
and `Plugin.cs`. These were developed with Pair-level assistance as
described above; the share of human vs. AI authorship varies file by file
and is expected to keep shifting toward more hand-written work as the
maintainer's plugin-dev experience grows.
## What AI is not used for