Collaborative Discussion 2 Reflection

This reflection covers my initial post, peer responses, feedback and summary for the second collaborative discussion in the Machine Learning module, which focused on AI writers, human oversight and responsible use.

Initial Post Reflection

The risk-gradient framing gave my initial post a useful structure. I separated low-stakes administrative writing from high-stakes legal, medical, HR, educational and public-facing uses, then treated creative writing as a separate cultural problem. Hutson helped establish the paradox that fluent prose can look authoritative without grounded understanding, while Noy and Zhang helped me acknowledge the real productivity gains.

However, the post treated these governance controls as more straightforward than they are. I named controls such as approved data use, source verification, bias testing, audit logs, human sign-off and accountability, but did not explain how they should work. "Human sign-off" can be weak if the reviewer is rushed, lacks expertise or assumes the model is correct.

I also could have been more critical of administrative use. Routine summaries, emails and report drafts can still contain sensitive data or introduce false details that later become part of an official record.

Exchange with Abdullah

Abdullah's response challenged an assumption I had not examined closely. He accepted the need for human oversight but pointed out that human-in-the-loop governance can become a procedural formality if reviewers are affected by automation bias or are not trained to intervene. I should have been more specific about what effective oversight involves, including escalation thresholds, reviewer competence, evidence checks, auditability and permission to override model output.

His point about diversity-aware prompting also strengthened the creative-writing argument. I had cited the risk that AI assistance may reduce collective diversity, but said little about prevention beyond keeping human judgement central. I could have explored varied prompts, multiple models, deliberate constraints, or human editorial standards as possible safeguards.

Peer Response Reflection: Ariel's Post

With Ariel's post, I was able to make the question more precise. Ariel focused on simulated cognition, agentic AI and the possibility that users may outsource cognitive work to systems that do not actually reason. I separated the question of whether an LLM "thinks" from the reliability of its outputs.

Questioning the social-media analogy was also important. Evidence about habitual platform checking and adolescent brain development does not automatically transfer to LLM-assisted reasoning, so the comparison should not be treated as established evidence.

However, my response narrowed the issue too quickly. Cognitive outsourcing is difficult to evidence, but that does not make it unimportant. I should have asked what evidence would be needed and engaged more with Ariel's concern about task execution and decision support.

Peer Response Reflection: Paul's Post

Paul gave strong examples of LLM benefits and risks, including nonsensical outputs, dangerous advice, opaque complexity and harmful stereotypes. My response built on these examples by distinguishing simulated empathy from real empathy. An empathetic tone can be useful in customer-service drafting, but dangerous in safeguarding or healthcare contexts.

I also challenged Paul's statement that there is "no effective solution" to bias and harmful output. Accepting that claim would have been too fatalistic. Dataset documentation, curation, bias testing, disclosure, source checking and accountable human approval may not eliminate harm, but they can reduce it.

Where the response fell short was in repeating ideas from my initial post rather than developing them further. I could have examined limited interpretability more closely: if model behaviour cannot be fully explained, what level of testing, monitoring or restriction is acceptable before deployment in sensitive domains? I also should have treated the self-harm example separately from general high-stakes use, because safeguarding interactions require much higher standards for safety and escalation.

Summary Post Reflection

By the summary post, my position had developed. I moved away from asking whether AI writers are useful and focused instead on the conditions under which they can be used responsibly. The distinction between AI as a writing aid and AI as a source of authority was clearer.

My treatment of human-in-the-loop review had also developed. I no longer presented human sign-off as sufficient by itself, instead linking oversight to escalation criteria, source verification, audit trails, bias testing and periodic auditing. The summary handled creative writing more carefully too, acknowledging the tension between democratising expression and narrowing collective diversity.

Even so, the summary still named governance mechanisms more readily than it explored trade-offs such as cost, speed, expertise and organisational incentives. It could also have made a stronger connection to machine learning evaluation through prompt testing, output monitoring, and failure-case logging.

Overall Reflection

Across the discussion, I kept the argument balanced and evidence-led, avoiding the view that AI writers are either harmless productivity tools or inherently unacceptable systems. However, I relied too heavily on governance language without always translating it into practice. I identified safeguards more consistently than I explained how they would be implemented or tested.

What I will carry forward is that responsible AI goes beyond simply "keeping a human in the loop". The real test is whether that person has the expertise, evidence, authority and time to intervene effectively, especially under pressure from speed, cost, convenience and overconfidence in fluent machine output.