Boundary cases: at least one non-technical client felt overwhelmed by multi-tool complexity, and a subset of surveyed students deliberately rejected AI use, framing the framework as serving the tentatively open¶

Claim · All claims
Evidence · 1 study · design r2 · q1
Currency · no dated study recorded · not yet checked against its sources · not reviewed by a person

Subclaims¶

q1 i? At least one client without a technical background reported feeling overwhelmed by the number of tools and steps involved in building a website and expressed a need for more foundational scaffolding, and survey data documented a subset of students (3) who reject AI in their education or feel the overhead of prompting outweighs potential benefits. → boundary-1

Evidence¶

boundary-1¶

Weihao Qu, Ling Zheng, Chris Buzaid, and Daniel Crawford. 2026. LearnAI: Just-in-Time AI Co-Creation Across Disciplines at a University. https://arxiv.org/abs/2608.19164 doi:10.48550/arxiv.2608.19164

q1 · i? · design · r2

Boundary-case analysis in the Findings section of the experience report, combining interview accounts and survey open-ended responses. The article also reports that survey data document "a subset of students (3) who reject AI in their education," framing rejection as an intentional educational philosophy rather than a knowledge gap.

"At least one client without a technical background reported feeling overwhelmed by the number of tools and steps involved in building a website (e.g., GitHub, hosting, multiple platforms) and expressed a need for more foundational scaffolding, highlighting a boundary condition for the current design."

Discussion¶

Related Claims¶

• Academic integrity, professional development, and equity concerns about AI span all surveyed units, though interpreted differently — related
• Over two semesters the LearnAI deployment reached 18 courses (293 enrolled students) and 35 co-creation clients who produced 36 portfolio websites and over 20 deployed applications — related
• Client interviews suggest a recurring shift from treating AI as a passive answer machine (\"Oracle\") to engaging it as a collaborative tool under human direction (\"Process Partner\") — related