惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

B
Blog
V
Vulnerabilities – Threatpost
Apple Machine Learning Research
Apple Machine Learning Research
V
V2EX
博客园 - 叶小钗
阮一峰的网络日志
阮一峰的网络日志
人人都是产品经理
人人都是产品经理
Latest news
Latest news
博客园 - 三生石上(FineUI控件)
美团技术团队
aimingoo的专栏
aimingoo的专栏
Google Online Security Blog
Google Online Security Blog
Security Archives - TechRepublic
Security Archives - TechRepublic
T
Threatpost
Y
Y Combinator Blog
T
Tailwind CSS Blog
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
A
Arctic Wolf
C
Cyber Attacks, Cyber Crime and Cyber Security
小众软件
小众软件
Recent Commits to openclaw:main
Recent Commits to openclaw:main
T
Tenable Blog
W
WeLiveSecurity
L
LINUX DO - 热门话题
D
Docker
Cyberwarzone
Cyberwarzone
量子位
A
About on SuperTechFans
The Last Watchdog
The Last Watchdog
雷峰网
雷峰网
C
CERT Recently Published Vulnerability Notes
P
Palo Alto Networks Blog
The Hacker News
The Hacker News
Blog — PlanetScale
Blog — PlanetScale
P
Proofpoint News Feed
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
F
Full Disclosure
The Cloudflare Blog
T
The Blog of Author Tim Ferriss
T
The Exploit Database - CXSecurity.com
Engineering at Meta
Engineering at Meta
O
OpenAI News
Hacker News - Newest:
Hacker News - Newest: "LLM"
Scott Helme
Scott Helme
IT之家
IT之家
S
Secure Thoughts
MongoDB | Blog
MongoDB | Blog
L
Lohrmann on Cybersecurity
博客园 - 司徒正美
Google DeepMind News
Google DeepMind News

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
AI Isn’t “Inspired” by Human Writing. It Is Built on Unpaid Intellectual Labor
Agustin V. S · 2026-05-07 · via DEV Community

Large language models do not only copy sentences. They absorb human knowledge, recombine it, and erase the trail of attribution.
Artificial intelligence companies often describe large language models as if they were “learning” from human writing in the same way a person learns from books, articles, code, essays, journalism, legal documents, and public conversations. That comparison is convenient, but it hides the central problem. Human learning takes place inside a culture of authorship, quotation, citation, responsibility, and criticism. If a person quotes a passage, they are expected to cite it. If they build on another author’s idea, they are expected to acknowledge it. If they copy without attribution, they can be accused of plagiarism.

Large language models operate under a different structure. They are trained on massive collections of human writing and transform that material into predictive capacity. Academic papers, books, code repositories, technical manuals, legal documents, blogs, forums, comments, and journalistic work become part of the statistical infrastructure that allows the model to generate new text. The final output may look original because it does not copy a single source word for word. But the absence of visible copying does not mean the absence of intellectual debt.

This is the argument behind my paper Plagiarism Ex Machina: Structural Appropriation in Large Language Models. The article does not treat AI plagiarism as a simple question of copied sentences. It argues that the real problem is deeper: large language models can absorb human-made intellectual structures, recombine them, and produce fluent outputs without showing where the underlying knowledge came from. This is what I call structural appropriation.

Structural appropriation means that the appropriated object is not only a sentence or paragraph. It may be a concept, an argument, a definition, a legal reasoning pattern, a coding solution, an academic tone, a journalistic frame, a taxonomy, or a way of explaining a problem. The model does not need to copy a paragraph in order to benefit from the labor that created these structures. It only needs to transform them enough that the source disappears.

That is why the language of “inspiration” fails. A poet may be inspired by another poet, but that inspiration exists within a recognizable human culture of influence, authorship, critique, and acknowledgment. A model does not participate in that culture. It does not read, remember, interpret, or acknowledge in the human sense. It absorbs statistical relations from enormous corpora and turns them into a product. That product is then sold through subscriptions, APIs, enterprise tools, writing assistants, coding assistants, search systems, and productivity platforms. Human language becomes machine capacity. Machine capacity becomes platform revenue.

The original writers usually disappear from that process. Their work may have helped train the system, but the output does not name them. Their style may have shaped the model’s fluency, but the interface presents the answer as if it came from the machine. Their concepts may have contributed to the generated explanation, but there is no visible source map. There is no intellectual debt record. There is no proportional compensation. The result is an asymmetry: the system can use the labor, the platform can monetize the output, and the originator becomes invisible.

*Why This Matters
*

The public debate about AI and plagiarism is still too narrow. Most people ask whether the model copied a sentence. That question matters, but it does not reach the deeper problem. A model can avoid direct duplication and still depend on the work of countless human authors. It can generate a paragraph that passes a plagiarism detector, contains no obvious overlap with any known source, and still be built from patterns extracted from human writing.

This is not ordinary plagiarism. Classical plagiarism is easy to imagine: someone copies a paragraph from an article, removes the author’s name, and presents it as their own. That model depends on visible textual overlap. AI introduces a different structure. A model may absorb thousands of texts on a topic, learn the common patterns of explanation, reproduce the tone, generate a new version, and present it as original output. No single paragraph is copied. No single author can be identified. No plagiarism detector flags it. But the output still depends on intellectual labor that was not credited.

This is recombinative plagiarism. It works through transformation rather than duplication. The model takes patterns from many sources, reorganizes them, and produces a text that appears new at the surface. The more advanced the system becomes, the better it may become at hiding the debt. A weaker model might copy visibly. A stronger model can appropriate structurally. That is the paradox: better generation can mean less detectable plagiarism, not less appropriation.

The key mistake is confusing originality with independence. AI-generated text often looks original because it does not match existing text. But originality cannot mean only “no identical source was found.” A paragraph can be unique in wording and still derivative in structure. An argument can be freshly phrased and still be assembled from prior human work. A definition can sound new while depending on conceptual labor already performed elsewhere. True originality requires accountable transformation. A serious author can explain what they read, what they borrowed, what they changed, what they rejected, and where their own contribution begins. Most AI systems cannot do that.

*Clear Examples
*

A coding assistant may generate a solution that does not copy any repository line by line, but still depends on patterns learned from open-source communities, documentation, issue threads, and developer forums. The generated code appears new. The labor that made it possible remains invisible.

A legal AI tool may produce a polished memo that sounds like professional legal reasoning. It may follow recognizable doctrinal structures, use formal legal phrasing, and imitate the organization of prior legal analysis. But if the system does not show which legal texts, briefs, treatises, or commentaries shaped the output, the user receives legal fluency without clear provenance.

A journalist may use AI to generate background context for a story. The text may not copy a specific article, but it may compress years of reporting into a generic explanation. The original reporting labor disappears, while the machine output looks like neutral background knowledge.

An academic writer may ask for a literature review. The model may produce a smooth overview, complete with plausible structure and citations. But the citations may be added after the fact. They may support the claims, but they do not prove that the generated argument actually came from those sources. This creates the illusion of accountability. The text looks scholarly, but its intellectual lineage remains unclear.

These examples show why the problem is not limited to copyright. Copyright asks whether protected expression was copied. Structural appropriation asks a different question: did the system convert prior human intellectual labor into a new output while making that labor impossible to trace?

*The Missing Concept: Provenance
*

The core problem is provenance. Provenance means knowing where something came from. In academic writing, provenance appears through citations. In journalism, it appears through sourcing. In law, it appears through traceable authorities, statutes, cases, and reasoning. In software, it appears through repositories, licenses, commits, authorship, and documentation.

Large language models weaken provenance because they generate from absorbed patterns without exposing the source chain. A model may provide citations if asked, but that does not fully solve the problem. A source added after generation is not necessarily the real source of the generated idea. It may be relevant. It may support the claim. It may look academic. But it does not prove that the model’s output actually came from that source.

This is why AI disclosure rules are too shallow. Saying “AI was used” identifies the tool. It does not identify the sources. It does not tell the reader which parts were generated, whether the claims were verified, whether the citations were real sources or added later, or whether the structure of the argument came from human research or model recombination. AI disclosure answers one question: was a machine involved? The deeper question is different: what human labor made this output possible?

That is why AI systems need generative provenance. Generative provenance would not require perfect attribution, because even human citation is never perfect. But it would require enough traceability to make generated outputs auditable. Systems should distinguish between sources actually retrieved during generation, sources added afterward to support a claim, user-provided documents, unsupported model synthesis, probable domain influence, high-risk similarity to known works, AI-generated sections, and human-authored revisions.

This would not solve every problem. But it would prevent the total disappearance of intellectual debt.

*The Real Question
*

The public conversation keeps asking whether AI can create. That is not the strongest question. The stronger question is what AI already took in order to appear creative.

Large language models are not “inspired” by human writing in the ordinary human sense. They are built on it. They absorb it, recombine it, and sell access to the capacity produced from it. Most of the time, they do not show the names of the people whose labor made the system possible.

That is why the AI plagiarism debate must move beyond copied sentences. The real issue is unpaid intellectual labor converted into synthetic originality. The machine writes because humans wrote first. The ethical question is whether the machine, and the companies behind it, will ever be forced to remember that.

*Read More
*

This article is based on the working paper:

Plagiarism Ex Machina: Structural Appropriation in Large Language Models
Agustin V. Startari

Related research:

Citation by Completion: LLM Writing Aids and the Redistribution of Academic Credits
**Zenodo: **https://doi.org/10.5281/zenodo.17287506

Borrowed Voices, Shared Debt: Plagiarism, Idea Recombination, and the Knowledge Commons in Large Language Models
SSRN: https://doi.org/10.2139/ssrn.5494528

Author page:
SSRN: https://papers.ssrn.com/sol3/cf_dev/AbsByAuth.cfm?per_id=7639915

Zenodo:
*Personal website: *https://www.agustinvstartari.com/

ORCID: https://orcid.org/0009-0001-4714-6539

ResearcherID: K-5792-2016

About the Author

Agustin V. Startari is a linguistic theorist and researcher in historical studies. His work examines how artificial intelligence systems, institutional language, and predictive syntax reshape authority, authorship, legitimacy, and accountability in contemporary knowledge systems. He is the author of Grammars of Power, Executable Power, and The Grammar of Objectivity.

Ethos

I do not use artificial intelligence to write what I don’t know. I use it to challenge what I do. I write to reclaim the voice in an age of automated neutrality. My work is not outsourced. It is authored.

— Agustin V. Startari.