I dislike to discuss AI, but for me the core issue is elsewhere, namely code generation & optimisation.
Sure, the current and predictable future IF compilers are much simpler than GCC, but the latter already use heuristics and pattern matching in these crucial phases. and the open source community isn’t much far behind the closed-one (or, if one prefer, corporate) development of AI (and the current global worries on AI & corporate abuses of AI will motivate the OS community in quickly closing the gap)
(yes, I’m writing from the political scientist side of my peculiar polymath…)
Perhaps came from my EU mindset, but I think that innovative but potentially distruptive technology is best handled by reining than resisting, that is, regulating (the core concept of EU mixed economy) but personally I dislike “preemptive regulating” and I feel that the spate of AI vs. IF debate (which I prefer to generally watch from the sidelines, if not even ignore) is turning in this direction, as the debate involves the “regulatory organs” of the IF community (not only IFTF, but also the competition rules)
IF are based on text and text is relatively easily machine-handled, provided that nonsense like EBCDIC is kept out of the picture, so, outside actual creative text, AI can actually have its usefulness, more so if used at the simplest level (Personally, I will more than welcome an expert system capable of pointing to bad english, and I note pointing, not correcting.)
(Little digression: I think that the community’s competence is capable of coding an IF-specialised linter, capable, e.g. of warning about non-fixed door (the classical major mistake…)
so, my stance is that AI in an IF environment, that is, an environment in which the creativity is based on the same building block of the coding (and intermingled together; I remain convinced that the “zarf license” is the best license for IF work, that is, characters (and digits) put together in a meaningful combination (Inform 7 & 10 is a major case in point) should be regulated in a way consistent with this peculiarity; the consistency lying in balancing between the “narrative and crossword”.
an expert system which in noticing, say, the word “door” in the narrative, raise the depth of analysis on portability attribuites in the code around IS a major linting tool in the IF context, and I hope that everyone agrees on this.
Conversely, if code (and I stress code) generation & optimisation has AI elements (heuristics, pattern matching) is welcome, esp. in the often constrained environment of IF VMs (the lease of life to .z3 VM from the unused code omission IS a major case in point, at least IMO)
so, I think we need more intelligent toolset for the coding side of IF creativity, than debating on regulating AI abuse; the time saved in coding and debugging is time gained for the creativity (side point, fooling around IN ITALIAN with Twine has pointed at much more time spent chiseling the text, and again, this in Italian.)
but for English-speaking people, I say only that Rule 16 applies, esp. in the light that AI tools are mainly from the western side of Rule 16…
Hope of having explained well my viewpoint, and
Best regards from Italy,
dott. Piergiorgio.