When Disclosure Feels Like Exposure
On writing with AI, staying accountable, and still being taken seriously.
Lately, I’ve found myself worrying less about whether AI can help me write, and more about what people will assume if I admit that it does.
Not because I don’t trust my judgment.
Because I do.
That worry became impossible to ignore when my AI‑embracing daughter talked about the backlash she received from her peers at school after she mentioned using AI. Their reaction wasn’t about whether the work was thoughtful or well done. It was about what they assumed the use of AI said about her. That anxiety mirrored my own. Not about quality. Not about effort. About legitimacy. About whether people would quietly decide that the work didn’t count.
The phrase that kept surfacing in both our fears was “AI slop.”
It’s a term that shows up more and more in conversations about writing, research, and creative work. And the more I listened to how it was being used, the clearer it became that this anxiety isn’t really about tools at all. It’s about whether care, judgment, and accountability are still visible when AI is part of the process.
When people talk about “AI slop,” they’re usually naming a very specific failure mode. Fluent output produced with minimal human judgment. Generic phrasing that sounds polished but says little. Little review or verification, and no clear accountability for errors. Often paired with vague or misleading authorship.
The problem isn’t AI use.
The problem is the absence of care.
That’s why the reaction is so strong. Slop erodes trust because no one appears to be responsible for the work. There’s no visible author standing behind it, no sense that someone made decisions, exercised judgment, or took ownership of the outcome.
Seen that way, the line isn’t actually that blurry.
My daughter didn’t hide her collaboration. She named her thinking partner. She put her name on the book anyway. I did the same with my own writing. I introduced my thinking partner explicitly. I signed my work. I remained accountable for what I published.
Those choices alone place both works outside what critics are actually pointing at when they warn about “AI slop.”
Disclosure matters. Transparency matters. Not because it absolves anything, but because it makes responsibility legible. One of the most consistent concerns in publishing right now isn’t that AI is being used, but that it’s being used without acknowledgment, review, or ownership. When readers discover that after the fact, trust collapses.
Naming a thinking partner does the opposite. It invites scrutiny. It signals intent. It says: this work was not produced in a vacuum, and I’m still responsible for it.
That responsibility doesn’t get thinner when AI is involved. If anything, it gets heavier.
I remain responsible for the ideas.
For the structure.
For the claims I make and the tone I choose.
For what this work puts into the world.
A thinking partner doesn’t replace judgment. It surfaces it.
This is where the anxiety creeps in, especially for people who care deeply about craft. If you value expertise, legitimacy, and trust, being transparent can feel like exposure. You worry that people will conflate collaboration with abdication, that fluency will be mistaken for emptiness, that care will be misread as shortcut.
But here’s the quiet tell that helped ground me:
People producing actual slop do not worry about this.
They don’t agonize over attribution. They don’t think about accountability. They don’t lie awake wondering whether they’ve undermined their own credibility. That anxiety isn’t a sign of wrongdoing. It’s a sign of ethical sensitivity in the middle of shifting norms.
What we’re living through right now isn’t a credibility crisis. It’s a transition in authorship norms.
We haven’t yet agreed on shared language for what human‑led, judgment‑dense collaboration with AI looks like, so people who disclose early feel exposed. Especially those who care about being taken seriously. Especially those whose work already lives in public.
But historically, it’s exactly this kind of explicit modeling that becomes the new baseline. The people who name their tools, own their decisions, and remain accountable don’t end up on the wrong side of these shifts. They help draw the line others eventually follow.
This is the language I’ve started using myself, and it’s the language I’ve offered my daughter too:
“This work was created with a thinking partner. I remain responsible for the ideas, the structure, and the final decisions.”
And if pressed:
“The concern with ‘AI slop’ is about absence of judgment and accountability. This work has both.”
Those statements are calm. They’re accurate. And they align with how the discourse is actually evolving, not the strawman version people argue against online.
I don’t expect everyone to agree with my choices. That’s fine. But I’m no longer willing to pretend that care is invisible just because the process looks unfamiliar.
The work still counts.
Judgment still matters.
And responsibility still belongs to the human who signs their name.
Alison + Wiggins