← Latest papers
💻 computer science

Structuring Transparency: Developing Domain-Specific Generative AI Declaration Frameworks in Higher Education

This paper proposes a domain-specific framework for Generative AI declarations in higher education that replaces generic binary statements with nuanced, task-specific structures for writing and coding to enhance academic integrity, foster AI literacy, and better prepare students for professional workflows.

Original authors: Nicholas Micallef, Olga Petrovska

Published 2026-06-12
📖 5 min read🧠 Deep dive

Original authors: Nicholas Micallef, Olga Petrovska

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a chef in a busy kitchen. In the past, if you asked for help, you had to shout, "I used help!" or "I didn't use help!" That's a binary declaration. It's like a light switch: either on or off.

But in reality, cooking is complicated. Did you use a sous-chef to chop the onions? Did you ask a friend for a recipe idea? Did you use a smart appliance to check the oven temperature? Did you let a robot stir the soup while you took a break?

The paper argues that asking students in university just "Did you use AI?" is like asking that chef, "Did you use help?" without caring how they used it. It's too simple, and it misses the whole story.

Here is what the authors, Nicholas and Olga from Swansea University, are proposing, broken down into simple terms:

1. The Problem: The "One-Size-Fits-All" Trap

Universities are currently trying to stop cheating by making students check a single box on a form: "Did you use Generative AI (like ChatGPT)?"

  • The Flaw: This is like a traffic cop only asking, "Did you drive?" without asking if you were driving a race car, a school bus, or a bicycle.
  • The Result: Students get confused. They think checking the box is like admitting they cheated, so they lie. Or, they check the box but don't explain that they only used AI to fix a typo, which is actually fine. This creates a "policing" atmosphere rather than a learning one.

2. The Solution: A "Menu" Instead of a Switch

The authors created a new kind of form, specifically for Computer Science students. Instead of one big box, they made two different "menus" depending on what the student is doing:

  • Menu A: For Writing (like reports or essays).
  • Menu B: For Coding (like programming tasks).

Think of this like a detailed receipt at a restaurant. Instead of just saying "Dinner: $50," it breaks it down:

  • Appetizer: Brainstorming ideas (AI helped a little).
  • Main Course: Writing the actual text (AI did not help).
  • Dessert: Checking grammar (AI helped a lot).

3. How the New Forms Work

For every part of the assignment, the student has to answer three simple questions:

  1. Did you use AI here? (Yes/No)
  2. How much? (Minor, Moderate, or Extensive).
    • Minor: "I asked it for one idea."
    • Moderate: "I used it a few times to help me think."
    • Extensive: "I basically let it write this whole section."
  3. Show your work: "What exactly did you ask it?" (e.g., "I asked it to explain this error message," or "I asked it to write a paragraph about history.")

4. Why This Matters (The "Aha!" Moment)

The paper claims this approach changes the game in three ways:

  • For Students: It stops them from feeling guilty about using a tool. It shows them the difference between "using AI to learn" (like asking it to explain a confusing concept) and "using AI to cheat" (like asking it to write the whole essay). It's like the difference between using a GPS to learn a new route versus letting a self-driving car take you to a test you aren't supposed to take.
  • For Teachers: Instead of guessing, they get a clear map. If a student says they used AI "Extensively" to generate code but "Minimally" to understand it, the teacher knows the student might be struggling with the basics. If they used it "Minimally" for everything, the teacher knows the student is doing the work themselves.
  • For the Future: The paper suggests that in the real world (jobs), people will need to document how they use AI. This form is practice for that. It teaches students to be transparent about their workflow, just like a professional engineer would document their design process.

5. The Catch (Limitations)

The authors are honest about the flaws. This system relies on honesty.

  • It's like a "honor system" receipt. If a student lies and says they did the work themselves when they didn't, the form won't catch it.
  • Sometimes students don't even know what counts as AI (e.g., is a smart spell-checker AI? Is a code suggestion tool AI?).
  • The paper does not claim this form will catch cheaters automatically. It claims it will make honest students feel safer to be honest and help teachers understand the learning process better.

Summary

In short, this paper says: Stop asking "Did you use AI?" and start asking "How did you use AI?"

By giving students a detailed, specific way to describe their help (like a chef listing every ingredient and who chopped it), universities can move away from being "police" and start being "coaches," helping students learn how to use these powerful new tools responsibly.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →