A Flawed Arbiter of Authenticity

By
Edward Cating

A Flawed Arbiter of Authenticity

by Edward Cating

This story was developed in open collaboration with an AI model, which I disclose here on the same terms the story argues for: plainly, and in my own name.

The sentence, as written, said: When my father passed, I felt a profound sense of loss that words cannot truly capture.

I read it twice, the way you'd hold a coin up to the light to check if it was the good kind of fake or the bad kind. This was the bad kind. Not because it was untrue --- plenty of true things sounded exactly like this --- but because it had no fingerprints on it. Nobody's father had ever passed this smoothly. I could hear the shape of the tool that had made it: the throat-clearing abstraction, the little bow before saying anything, the reach for profound like a man reaching for the good silverware in front of company.

I didn't delete it. Deleting was for amateurs. I rewrote around it, the way you'd reset a bone instead of amputating.

My father died on a Tuesday, which felt like an insult, since Tuesdays were his day to call.

Better. Not because it was more clever, but because it had a seam in it, a place where a real person's irritation had leaked through the grief. That was the whole trick, the one I'd been paid for, one way or another, since I was twenty-three: you didn't need to write something a person would say. You needed to leave in the one wrong-sized detail a machine would have sanded off out of politeness. A tenth of a degree of asymmetry. Enough that a reader's animal brain, the part that had spent two hundred thousand years learning to tell a living face from a mask, would relax without knowing why.

The manuscript was called, provisionally, What My Father Left Me. The man who'd hired me to finish it, a dermatologist outside Hartford, had written the first draft himself, badly, and then, by his own sheepish admission, "cleaned it up a little with the AI, just for flow." What he'd actually done was feed it dozens of pages of raw material and let something else decide what mattered. My job, contractually, was developmental and line editing. Actually it was resurrection. I found the one true bone in each chapter and built a body around it convincing enough that nobody would ask where the rest came from, and when I was done, nobody --- not the dermatologist, not his future readers, eventually not even me --- could have told you which sentences were his and which were the machine's and which were mine.

At 6:40 I saved the file, renamed it Ch4_v3_NR, and sat a second too long with my hand on the mouse, the cursor blinking in the white space after a stranger's dead father, before I remembered I had my own dead father waiting, two folders down, in a document I had not let anyone read closely enough to fix.


It was a handful of pages, and they were the only writing I owned outright anymore --- owned like authored, in the older, smaller sense. Mostly they were about the register: twenty-two years of a restaurant, my father at closing flattening each receipt under his thumb before filing it, like the day hadn't really happened until it had been pressed flat and put away. And they were about a ring of keys. I hadn't run my usual passes on those pages. I hadn't let myself be good at them, on purpose, the way you don't let a doctor operate on her own family. I left in things I would have cut from anyone else's draft. I told myself this made them more true. I did not examine that belief very hard, the way you don't examine a load-bearing wall while you're still living in the house.

I sent six of the pages to the Kestrel Nonfiction Fellowship: twelve thousand dollars and four uninterrupted months, to one writer a year. I didn't tell my brother, Aaron, or our mother. Under the upload field, in the gray twelve-point font websites reserve for sentences they hope you won't read, it said all submissions were screened for AI-generated content, and that substantial AI-generated material would be disqualified without further notice. I read substantial twice. It was doing an enormous amount of work for a word that short. I knew what it could do. A few years earlier I'd edited a woman's wildfire-evacuation memoir that came back from this same fellowship flagged at seventy-one percent. She hadn't used AI either. She used commas the way an anxious person breathes --- too regularly, too evenly, a technique for staying calm rather than for meaning something --- and that regularity was, to a machine, indistinguishable from its own.

There was a checkbox. I certify that this submission is my own original work. I clicked it the way you click every checkbox in your life, meaning it and not thinking about it in the same motion, which was, I would consider later, an almost perfect description of what everyone meant by human anymore --- not the absence of a machine's help, just the presence of a click nobody made you slow down for.


The email came at 4:12 on a Wednesday, from an address that began, unpromisingly, with no-reply, which told me everything before I'd opened it. A yes arrives from a person; a no arrives from a system that has already decided a person's time isn't worth spending on you.

The rejection itself was a paragraph of procedure. The attachment was not. AI CONTENT ANALYSIS --- SUBMISSION #4471, it said, in a sans-serif font optimized for nothing except being read quickly and believed. Overall assessment: 68% likelihood AI-generated or AI-assisted. Below that, my six pages, most of them in plain black text, and three passages highlighted the pale, clinical red of a health app flagging a resting heart rate.

The second was the one about the keys.

My father's version was a ring of keys. Forty, maybe fifty of them, on a coil of wire, most fitting locks that no longer existed --- a bakery that closed in the eighties, an apartment three moves ago, a car sold for parts. He never threw a key away.

Beneath it, a note. Segment flagged: high-confidence AI-generated (94%). Detected pattern: emotionally resonant object-based narrative construction; low syntactic entropy; consistent with common LLM memoir-generation strategies.

I read emotionally resonant object-based narrative construction three times. I thought about the actual weight of that ring the one time he'd let me hold it, at nine, in the kitchen, while my grandmother snapped beans two feet away. Some machine, having been shown enough memoirs about enough dead fathers, had learned that this --- the objects instead of feelings, my family's whole inherited grammar of not saying things directly --- was not a thing my family did. It was a thing memoirs did. It had a name. It had a percentage.

Then I did the thing I tell clients never to do, which is reread your own sentence right after someone has told you it's wrong. You will not read it as a sentence anymore. You will read it as a crime scene.

It's a good sentence. I know it the way I'd know a chair was well built without needing to have built it. And standing in my own kitchen I felt the bottomless vertigo of realizing that "it's a good sentence" and "a machine could have written it" had, at some point in the last few years, become the same observation wearing two different coats. Forty, maybe fifty. I'd chosen that hedge because I genuinely didn't know the number, and a false precision would have been its own kind of lie. Now I heard, instead of my honesty, a technique. The calculated imprecision. The little bow before the fact, dressed up as candor. I had spent my whole career manufacturing the texture of authenticity for other people, and I could no longer tell, looking at my own sentence, whether I had found the bone or built it.

I tried to go under the sentence, back to the actual afternoon --- the beans, the cold weight of the keys, the give of the coil of wire in my palm --- and for one bad moment, standing in my kitchen at nine years old and thirty-four at once, I couldn't get there directly. I got there through the sentence. The afternoon was gone the way all afternoons are gone, and what stood in its place was years of remembering it in prose, each pass smoothing the last, until I couldn't have told you whether I was recovering a memory or maintaining one.

That was the actual insult, underneath the fellowship's polite one. Not that a machine had accused me of writing my father. It was that I couldn't produce, from the inside, the thing that was supposed to prove the machine wrong. I had the sentence. I had only ever had the sentence. And a sentence, it turned out, did not come with a certificate of where it had been.


There is no button on the Kestrel website that says Appeal. There was a contact form, and a reply that arrived in four minutes, which told me no part of a person had been near it. It assigned me case number KNF-22841 and informed me that decisions informed by content-integrity screening were final and not subject to individual review.

Two clicks into the privacy policy I found who had actually decided: submissions may be processed using third-party AI detection services, including but not limited to Pandora Labs. Not Kestrel's judgment. A vendor's. I knew Pandora. I'd paid for a professional seat for years, quietly screening clients' manuscripts before I handed them back, so none of them ever had to know I'd checked.

I read the company's technical report that night the way I read a client's worst chapter: not for pleasure, not yet for anger, just for the seams. Mixture of experts. Token-level heads. A training process that paired human writing with a machine's best guess at the same writing and taught something to feel the difference. They had built the thing the way I built a resurrection, at industrial scale, with better tools than mine. The only difference was that nobody had ever handed my work a percentage and called it a verdict.

One finding was buried near the end: the same passage could score differently depending on what surrounded it. I had built a career on a version of that fact. A good line survives being moved into a worse paragraph; a great one can die of the company it keeps.

So I tested it. I pasted the keys paragraph, unchanged, into the middle of six pages of the least sentimental prose I owned --- a software license I'd ghost-edited for a payments startup, all indemnification and governing law --- between a clause about liability and one about arbitration venue, the way you'd hide a photograph inside a tax return.

Nine percent.

It felt like vindication for about one breath: proof that the ninety-four had never been a fact about my father's keys, only about the company they'd been keeping. Then I noticed what I had actually done, which was take text a fellowship had flagged, disguise it inside a document built to bore a machine into inattention, and confirm that the disguise worked. That was not a discovery. It was a technique. People in my business had started whispering about tools that did exactly this at scale --- swarms of rewrites testing themselves against detectors until one passed, indifferent to whether any of it was true.

And I had run the test from my own account.

The email arrived before I'd closed the tab. Unusual activity detected on your account. We've identified a pattern consistent with adversarial testing behavior --- repeated submission of matching or near-matching content across differently structured documents within a short window. Professional-tier access may be suspended pending outcome.

That one I couldn't argue with. The first report had guessed at something interior --- a feeling, a father, an afternoon nobody else had been in the room for. This one had simply watched me at a keyboard and described exactly what I'd done. It had been right, completely, both times, about two different women who happened to share my name: the one whose grief it had misread, and the one who'd gone looking for the seams in its misreading and found them.


The week wasn't finished with me. The dermatologist called with no hello: his publisher had run the whole manuscript through its own screening before the contract went final, and chapter four had come back flagged --- the paragraph about his father's hands, the one I'd built around a comma splice he'd typed at a red light. His contract warranted that the work contained no AI-generated material. If any was discovered, the publisher could withhold the rest of his advance and take back what it had already paid. My invoice was a line inside that advance.

"Fix it," he said. "However you fix it."

I knew how. I had proved it on my own father two nights earlier. I called him back the next morning, because some conversations deserve to cost both people the same amount of time, and told him what fixing it would mean. The paragraph had been flagged for its specificity. The only way to make it pass was to sand the specificity off --- softer verbs, fewer exact objects, a certain evenness the model reads as calm instead of grief.

"I'd be laundering it," I said. The word surprised me on the way out, but I let it stand. "You'd never fail a scan again. I don't think you'd recognize your father in it."

He was quiet a long time. Then he said he needed to think about it, and I told him to take the time, and did not tell him I might be talking myself out of the last client stable enough to make my rent look survivable on paper.


My account's case went to a person. His name was Marcus Oyelaran, and the first thing he said, after the recording notice, was that he couldn't reverse a flag on this call --- a review board decided that --- and that he wanted me to know it going in, so I wouldn't be waiting for something he couldn't give me. Nobody in the entire process had told me, at the start of a conversation, exactly what the conversation could and couldn't do.

The flag was accurate as a description of my behavior, he said, and he didn't soften it. Whether it was a violation or a good-faith attempt to understand a tool was still, for now, a human question.

"And my father's memoir," I said. "Is that a human question too?"

A pause, long enough that I heard a keyboard somewhere behind him. "I've read that paragraph probably a dozen times today," he said. "It's in your case file." Then, off the record --- and he meant it literally, it was not going in the file --- he told me he didn't think it was AI-generated, and that what I'd done with the license agreement looked like someone trying to understand a tool rather than someone trying to profit from breaking it. "That's my opinion. It isn't evidence. I'm not allowed to call it evidence. I just didn't want to get off this call without saying it once, to a person, instead of writing it into a system that's going to average it out with everything else it already thinks it knows."

A few days later he wrote to me from a personal address, which told me before I'd read a word that it had been written by a man and not cleared by a department.

Two years ago I would have told you, without hesitating, that the model does something more like sorting than understanding. I don't believe that anymore. Some of its calls are too specific to be coincidence and too strange to be simple statistics. The people who build these systems have said publicly that they don't fully understand how their own creations work, and that this is basically unheard of for any technology anyone has ever built. These things are grown, not built. Nobody wrote the part of it that decided your father's hedge looked ninety-four percent synthetic. It grew that judgment the way a plant grows toward a window nobody told it was there. So when you ask me what it really meant by the number, I can't go check. There's no file to open. There's only the number, and a company that would prefer I call it confidence instead of what it actually is, which is closer to a very expensive guess that happens to be right often enough to bill for.

Please don't reply to this address.

I read it more than once, slower each time, and thought that it was the most rigorously honest document anyone in the whole ordeal had produced about how little anyone actually knew, and that it had arrived, appropriately, from an address with no authority behind it at all.


I told my mother at her table, after the plates were cleared. All of it: the fellowship, the percentage, the keys, my own account, the thing I had done that actually was exactly what it looked like. She held up one hand without looking at me, the gesture she'd used my whole childhood to mean I am still using this silence, do not take it from me yet.

"They said his memory of the register wasn't real," she said finally.

"They said the writing about it read like something a machine would generate. It's not the same accusation, but I don't think it lands any easier."

She got up and came back with a shoebox I'd watched come down from that shelf my entire childhood, for reasons nobody ever explained. Under a stack of photographs was the ring of keys. She set it on the table between us like evidence she'd been holding for the other side.

"You wrote fifty," she said.

"Forty, maybe fifty. I said I wasn't sure."

"There's nineteen." She said it the way you'd correct an oven temperature, without judgment about why you'd had it wrong. "He used to shake them when he walked so they sounded like more. It was a bit. Your father had a bit for everything."

The machine and my mother had arrived, from opposite directions, at the same place: doubting the number I'd built the paragraph's whole authority on. The machine had called the paragraph too smooth to be a memory. My mother was telling me the memory itself had been smoothed, decades earlier, by a man performing for children too young to know they were watching a performance. Neither of them was wrong. I had built a true sentence out of a false number, remembered honestly, about a man who had invented the false number himself, on purpose, out of love.

"That machine read a paragraph about a man doing a bit with his keys," she said, "and decided nobody real could have written it, because it sounded too much like the kind of detail somebody would invent to seem honest. That's the most accurate thing anybody's said about your father since he died. You didn't get caught making him up. You got caught getting him right enough that a machine that's read a million fathers didn't believe a real one could be this particular."

She put the keys in my hand across the cleared dishes. "Fix the number," she said. "Not because they're right. Because you know better now, and you didn't before, and that's the only kind of correction that's ever actually worth making."


Aaron and I finally cleared out the storage unit that held what was left of the restaurant, a job we should have done the year he died and hadn't, because doing it would have required agreeing on what to keep. A prep table. A stack of laminated menus. The register, its drawer taped shut with packing tape gone amber, which neither of us moved to open. And, under a broken heat lamp, a box marked RECEIPTS that wasn't receipts. It was notebooks, a dozen or so, the cheap drugstore kind, filled cover to cover in his handwriting.

Most of it was order logs and supplier complaints. Then, a few notebooks in, the register.

Register jamming again on the humid nights. Paper curls in the drawer, won't sit flat, then the tray won't close and I'm forcing it at 1 a.m. like an idiot. Started flattening the night's receipts under my thumb before filing so they'd lie down properly. Works. Ten seconds a night. Should've thought of it years ago. Note: ask R. about a dehumidifier.

There was no feeling in it. Not hidden, not compressed, not performed. There was a drawer that stuck, and a hand that flattened paper because a flat thing files easier than a curled one, and a joke about a dehumidifier. I had built a paragraph, and possibly an entire understanding of my father, out of ten seconds a night that he'd considered a fix for humidity.

I noticed myself wanting, at once, for this to have destroyed something and for it to have touched nothing real at all. Neither was true. He hadn't been performing grief with his thumb. He also hadn't been wrong to let his daughter believe he had, because I hadn't invented the gesture --- only what it meant, the same way my mother had invented what the keys meant, the same way he may have invented the dehumidifier joke for himself, so that he could be a practical man solving a practical problem instead of a man standing in a kitchen every night not knowing how else to end a day. The notebook only had the drawer. And I had just done to my father's private, un-witnessed handwriting exactly what a detector does to a paragraph: read it once, assigned it a meaning it could neither defend nor deny, and called the reading a fact about him instead of a fact about what I'd needed the drawer to be.

Near the back of the same notebook there was a fishing entry. I brought it to Aaron rather than reading it to him over the phone, because some sentences deserve to be handed over rather than performed. Our father had taught him to read rivers the way he taught everything that mattered, standing beside him, with his hands and never with a word.

Took A. out one more time before my hands got too bad. Didn't tell him it was probably the last one, didn't need to. He tied two leaders without me asking, one for him, one already looped on my rod. Fish took his fly downstream of where he called it, which pleased him more than it should have, and I didn't tell him I was proud of exactly that. Good morning. Don't know how many more of those I get.

Aaron read it twice, standing in his own kitchen. "He knew it was the last one," he said. "I always thought I was the only one who knew."

"Isn't that a good thing? He was proud of you. In his own hand, nobody grading him for it."

"It should be." He set the notebook down carefully, the way you'd set down something you'd just learned was more breakable than you'd been treating it. "That morning was the one thing I got to just have. I never needed anybody to confirm it. Now there's a second version, and even though it says I was right, it's not the same as being right without a second version to be right against."

Mine had taken the feeling out of something I was sure had one. His had put a feeling into something he never needed proof of. Neither of us could say who'd gotten the worse deal, and for once neither of us pretended.


I put the keys on the counter when I got home, where they have stayed ever since, and did not open my father's file. I kept thinking about Marcus's email --- grown, not built --- and somewhere around midnight, down a link from a link, I found a sandpile.

Drop sand one grain at a time and the pile eventually reaches a state where the next grain might do nothing, or might bring down an avalanche the size of the whole pile, and there is no way, looking at that grain, to know which. The size of the avalanche is a fact about the pile's entire history, every slope that ever formed and collapsed underneath. You cannot recover it by weighing the grain that set it off, however carefully you weigh it, however good your scale.

The keys weren't the avalanche. My father wasn't. Even the paragraph wasn't --- the paragraph was one grain, weighed by a machine that could only ever weigh grains and call the weighing a verdict. Whatever had actually been true about my father, not the count, not the sentence, had never been locatable in a paragraph at all. It was a property of the whole slope: every receipt pressed flat at the register, every key shaken to perform a joke for children who wouldn't get it until they were grown, every version of him my mother and my brother and I had each built out of the same man and never once compared until that month.

Which meant I had been asking the wrong machine the wrong question, and so had I.

I opened a new document and typed its first line.

The machine that flagged my father's memory was not wrong about the paragraph. It was wrong about what the paragraph was for.

I didn't write a defense of him. I no longer had a version of him clean enough to defend. I had four --- mine, my mother's, his own, and whatever the report thought it saw --- and none of them agreed, and none of them was lying. So I set them side by side: my paragraph against the ninety-four percent, against nineteen keys, against a sticking drawer and a dehumidifier, with nothing underneath any of it telling the reader which to believe.

Which meant it couldn't only be about my father. If the subject was what a flawed arbiter does to an unverifiable life, I knew exactly who else had one. I found the wildfire memoirist's name in an old client folder --- Renata --- and wrote to her before I could make the email more careful than the moment deserved. I told her I'd been flagged too, that I was writing about what that does to a person, and asked whether she'd talk to me, on the record, in her own words.


She didn't answer for most of a week.

I remember you, she wrote. You cut the chapter about the second evacuation and the one about my ex-husband's truck, both of which I fought you on, because the book was too long and my agent had already sold it on a page count. I want to say that before I say yes to anything, because I don't especially want to be in a book about being misread by the person who once decided which parts of my own story got to survive.

This one I recognized, all the way down, as earned. I hadn't forgotten the chapters. I had filed them as a production decision, a page count, a deadline --- the kind of cut that gets absorbed into the job without it ever occurring to the person making it that it cost the person who lived it something that couldn't be put back. I had spent weeks furious that a machine had reduced my father to a percentage without knowing what it was doing. I had done a version of the same thing to Renata's ex-husband's truck, with less excuse.

You're right, I wrote back, and I'm sorry, and the apology doesn't bring the chapters back. If you do this, I want you to have what I didn't give you the first time: final say over what stays in.

She answered within the hour. Okay. Ask your questions.


"Ask me the real one first," Renata said when I called. "Not the percentage. Everybody wants the percentage, and it's the least interesting part."

"What's the real one?"

"What it did to my sister." Her sister had read the report before she did --- had forwarded it, thinking she'd want to see it fast --- and had called that night, not about the fellowship at all. "She said, and I wrote this down afterward because I didn't trust myself to remember it right: Was the part about the dog even true, or did you just need the book to have a dog in it?"

"There was a dog."

"There was a dog. It turns out there's a version of the truth that survives a machine and one that doesn't survive your own sister, and I only found out they were two different tests by failing one of them in front of her." They hadn't really talked for months afterward. Not a fight. "She read me differently. Carefully. Like she was proofreading me instead of listening." It was fine now, mostly. "But put that in as the point, not as an anecdote, because you're about to make the report's mistake. You're treating the percentage like the injury. It wasn't the injury. It was the delivery mechanism. The injury was somebody I loved filing me under maybe fabricating."

Then she asked the question I hadn't prepared for. "Why is this your book? You got flagged once. I got flagged once. Why does the version with your name on the cover get to hold mine inside it?"

I didn't have a practiced answer ready, which surprised us both. "I don't know yet," I said. "I know the noble version, about giving voice to people the system failed, and I don't trust it. It sounds like a sentence I'd have cleaned up for someone else's book without checking whether it was true."

"That's a better answer than the noble one," she said. "It's not an answer, though. Ask me the rest. We'll come back to it."


I transcribed the call before I wrote a word, because that was the rule I'd made walking in: get the words down exact first, shape them later. I kept the rule until I got to the sister. An hour later my draft read: Her sister found the report first, and the question she asked that night was smaller and worse than anything about the fellowship: whether the dog had ever existed, or whether Renata's grief had simply needed one.

For a moment I was proud of it. It moved. It had a rise and a cadence the transcript didn't have. Then I read her actual words beside mine and saw what I'd done. She had never said her grief needed a dog. And I had quietly deleted the one thing she'd volunteered about herself --- I wrote this down afterward because I didn't trust myself to remember it right --- because it complicated the clean line I wanted. I had found the true bone and built a body around it, the way I had since I was twenty-three, on a woman who'd spent a whole phone call telling me she did not want to be handled. I had spent weeks angry at a machine for producing a confident verdict it couldn't verify from the inside. I had just done the same thing to a living person, in prose, and it had felt, while I was writing it, exactly as true as everything else I'd ever written --- which was apparently no evidence of anything at all.

I didn't delete the polished version, and I didn't restore the transcript. I set both side by side, chose neither, and did something I had never once done in my career: I sent a client an unfinished section. Both versions are here, I wrote. I'm not asking you to pick. Tell me whether either one, or the two of them together, gets you right.

Then I sat at my counter, my father's notebooks at one end and my manuscript at the other, two boxes of unverified people, and understood that I was waiting exactly the way I had waited for Kestrel --- standing on the other side of the same window, for someone else to decide whether I had gotten a person right.


She answered the next morning. I'm not picking either. But "here are two versions, you decide" is its own kind of trick. It looks like humility, and it hands the reader the job you didn't want. Leave both in. Then let me write the sentence that comes after them, and don't touch it, not even a comma.

Beneath it was a single paragraph.

My sister and I are fine now, in case anyone reading this is worried. We didn't fix it by working out which version of the dog was true. We fixed it by her asking me, straight out, instead of deciding quietly on her own, and me answering the same way. That's the whole trick, if there is one. Ask the person instead of the report.

I put it in untouched, down to the comma. She had done, in a few sentences she controlled completely, more of the book's actual work than I had managed in weeks of trying to be fair to her from the outside.


When I read the whole thing through for the first time as something other than its author, I hunted for every place I'd been tempted to add a sentence that settled an argument the sources hadn't settled, and I cut every one of them. Then I went looking for a title and found one in an old file: a line I'd typed to myself at 2 a.m., weeks earlier, as an accusation aimed at Kestrel and the report. A flawed arbiter of authenticity. It had never only been about them. It was about my mother, choosing for decades which parts of him we were allowed to see. It was about Renata's sister. It was about me, deciding for a living, on other people's behalf, what their sentences were allowed to mean. I put it on the title page and let it aim at everyone in the room, including whoever was holding the pages.


The dermatologist brought me his proof copy before I'd sent mine anywhere. He hadn't let me launder it. He'd told his publisher the whole truth, and they had kept the deal on one condition, printed under the copyright block of every copy: Portions of this manuscript were flagged by automated content-integrity review. The author affirms sole authorship of the complete work.

"My father's book," he said, his hand flat on the cover, "with a line in it saying a machine doubted him. Forever."

"I think it's the first book I've ever worked on," I said, "that tells the truth about how it was made."

The same week, Pandora reinstated my account, with a permanent annotation: Prior adversarial-pattern flag, resolved, non-punitive. We compared our asterisks like people comparing scars from the same accident.

I sent the manuscript to Isthmus Review, a literary quarterly whose submissions page said, in the same plain language I'd been trying to write the whole thing in: We screen. We disclose the screening. We publish flagged work when a human editor believes the flag was wrong, and we say so in print when we do. It was the first policy I'd read that admitted a machine's opinion and an editor's word were two different things, and always would be.

Writing the cover letter, I noticed the old thought arrive one more time --- a dozen versions of the manuscript quietly competing against each other to see which scored lowest. I noticed it arrive, and then it left, the way a smell does once you've finally found where it's coming from and fixed the actual problem. The book was built to be disagreed with. Running it through something designed to erase the disagreement would have been sanding the receipts flat before reading what was written on them.

There was a checkbox. I certify that this submission is my own original work. It wasn't a simple sentence anymore. My own original work now included a paragraph I'd left untouched because someone else had earned the right to write it, a report I hadn't written, reproduced in full and disagreeing with me on the record, and my father's handwriting, which was not my work at all and was the entire reason the book existed. I checked the box anyway, because I finally understood what it had always been asking, underneath the simple words --- not did you write every sentence alone, but do you stand behind the whole thing, seams included, exactly as it is --- and for the first time in that whole year, I could answer without anyone's percentage telling me whether I meant it.


The reply came weeks later, on an ordinary Tuesday, from a person.

Our screening flagged your manuscript on intake. I want to be direct about why. The software has no way to distinguish a quoted, deliberately reproduced instance of flagged text from an original one. Your piece contains, verbatim, the paragraph a different system flagged, and ours did what it is built to do, which is flag paragraphs, not read essays. It came back at ninety-one percent. That number sat in front of me for exactly as long as it took to reach the sentence in your own piece explaining why. Then it stopped being useful to me, the way I suspect it eventually stopped being useful to you.

We're accepting the piece. We're also going to say, in a short note above it, that it was flagged on submission and that I chose to publish it anyway, and why. Most places would quietly override a flag like this and never mention it. I think the whole point of your piece is that quietly overriding it and saying nothing is exactly the kind of decision that got made about your father, and about a woman named Renata's memoir, by people who never once had to put their name next to the choice. I'm putting mine next to it.

I didn't cry. I noted that, this time, not as a small useless victory but simply as a fact about the shape the news had taken: arriving uncomplicated, arriving as something that was, for once, only good. I wrote back three words before I let myself write anything longer. Thank you. Say it.

Renata called after she read the advance copy. She had searched her paragraph, she said, for the place I'd smoothed it, and couldn't find a seam, which meant either I hadn't touched it or I'd gotten too good at hiding the touching, and she'd considered the second possibility seriously before she believed the first. Then she told me she was writing something of her own --- about her mother, who was still alive to be hurt by getting it wrong. "I stole your rule," she said. "Words down exact first, shape them later. I'm telling you so you don't find out by accident."

"You can have it," I said. "It wasn't mine either, really. I learned it from a machine that was worse at knowing the difference than either of us."


That night I went looking, almost by accident, for Ch4_v3_NR, and at the top of it found the sentence I'd found first, before any of this: When my father passed, I felt a profound sense of loss that words cannot truly capture.

I read it the way I'd read it the first time, for the tells. It was still the bad kind of fake, still a sentence with no fingerprints on it, still as easy to catch as it had ever been. What had changed was that I no longer believed catching it told you anything final about the man inside it, or about the son who had reached for the nearest words a machine could offer because he hadn't yet found his own. There had been an actual father, actually dead, and an actual son, and a machine that offered him some words, and none of that made the sentence true, and none of it made the sentence nothing. It was a fake, and evidence of something real standing behind the fake, both at once --- the way my paragraph was, the way the register was.

The keys were still on the counter. I picked them up and weighed them once, the way my mother had, the way I imagine he had a thousand times without either of us watching closely enough to count, and put them back down exactly where they'd been.

Nineteen keys. Forty, maybe fifty, in the version I'd believed long enough to build a book out of. Both true. Neither finished. I turned off the kitchen light and went to bed, and did not, for once, lie awake waiting to find out what I actually was.

How I Used AI to Collaborate on This Story

This story was developed with Anthropic's Claude, an AI model, working as a drafting partner under my direction. It is a condensed version of a novel we built the same way.

I supplied the premise and the working title, and I chose the ideas the story rests on: what AI detectors measure and what they miss, how little even the builders of these systems understand them, and how order arises from chaotic systems, which became the sandpile. I made the structural calls. I set first person throughout, decided which characters survive the cut to short-story length, brought Renata back after the first condensed draft dropped her, and chose the ending's refusal to resolve. I edited the prose directly, including a standing rule that repeated numbers must never become rhymes. I also renamed the detector and decided to disclose.

Claude drafted nearly all of the sentences. That includes the original chapters, the condensation to short-story length, and the synopsis, pitch and logline. It also researched the technical material and ran consistency passes. I accepted, rejected or redirected each piece.

The story argues that an unverifiable seam should be disclosed rather than smoothed over, so I'm disclosing this one: the direction and the responsibility are mine, and most of the sentences were drafted by an AI at my direction.



AuthorEdward Cating
SubmittedSep 30, 2026
TitleA Flawed Arbiter of Authenticity
LoglineA ghostwriter who makes AI prose pass as human for a living is told by a detector that her memoir of her late father reads as machine-made. She discovers that no source (not the machine, not her mother, not even her father's own notebooks) can settle what was true about him.
Word Count7091
TypeShort Stories
GenreLiterary Fiction
How AI Was UsedThis story was developed with Anthropic's Claude, an AI model, working as a drafting partner under my direction. It is a condensed version of a novel we built the same way. I supplied the premise and the working title, and I chose the ideas the story rests on: what AI detectors measure and what they miss, how little even the builders of these systems understand them, and how order arises from chaotic systems, which became the sandpile. I made the structural calls. I set first person throughout, decided which characters survive the cut to short-story length, brought Renata back after the first condensed draft dropped her, and chose the ending's refusal to resolve. I edited the prose directly, including a standing rule that repeated numbers must never become rhymes. I also renamed the detector and decided to disclose. Claude drafted nearly all of the sentences. That includes the original chapters, the condensation to short-story length, and the synopsis, pitch and logline. It also researched the technical material and ran consistency passes. I accepted, rejected or redirected each piece. The story argues that an unverifiable seam should be disclosed rather than smoothed over, so I'm disclosing this one: the direction and the responsibility are mine, and most of the sentences were drafted by an AI at my direction.