返回首页

对比阅读

对比阅读:Strata Wipes Claude Co-Author Tags — Industry Split on AI Ghostwriting 与 开源项目悄悄删光'Claude 写的'标记 — 行业开始为 AI 代笔署名扯皮

AEN
StrataClaudeAnthropic·

Strata Wipes Claude Co-Author Tags — Industry Split on AI Ghostwriting

This week, an open source project called Strata was caught by the community: they quietly rewrote their entire Git commit history, scrubbing every "Co-Authored by Claude" tag from their commits. We noticed the incident is small, but what it rips open is the most awkward gray boundary in the open source community in the AI era — when AI helps you write code, do you actually have to disclose it in the attribution?

What this is

Strata is a project on GitHub; its specific use case is still being dug up by the community. A developer tried to run its built-in update script, and git threw an error saying it couldn't find a common ancestor node. On inspection, they found that all historical commits had been rewritten and every "Co-Authored by Claude" attribution trace had been cleaned out. Reddit user dasbin posted it to r/LocalLLaMA, generating significant discussion. Technically, rewriting history isn't difficult; the question is motivation — why would a project go to such lengths to erase this?

Industry view

Those supporting disclosure argue: the core contract of open source is honesty; if you used AI to write it, you should say so — that's the baseline. Opponents push back too: tool assistance isn't plagiarism; we don't tag every IDE auto-completion in commits either, so why should an AI assistant get a separate credit line?

What we care about more is the overlooked third voice: this kind of systematic erasure makes code audits, compliance traceability, and open source license compliance all harder. What's worth flagging is that when projects get procured by enterprises and integrated into critical systems, the answer to "who wrote this code, and who's responsible if something goes wrong" is being technically erased. Strata isn't an isolated case; it just happened to get caught.

Impact on regular people

For enterprise IT: code procurement and audit processes may soon need an extra line — AI generation ratio disclosure — this is a new compliance pit.

For individual careers: the value of "I did this independently" on a programmer's resume is being reassessed; the boundary between human and AI collaboration will increasingly need to be spelled out.

For the consumer market: when buying software or courses in the future, will "human-made" become a new premium label? Worth watching.

BZH
StrataClaudeAnthropic·

开源项目悄悄删光'Claude 写的'标记 — 行业开始为 AI 代笔署名扯皮

这周一个叫 Strata 的开源项目被社区抓到:他们悄悄重写了全部 Git(代码版本管理工具)提交历史,把每条 commit(提交记录)里'由 Claude 共同编写'的标记一条条抹掉。我们注意到,这事儿不大,但撕开的是 AI 时代开源社区最尴尬的一道灰色边界——AI 帮你写的代码,到底要不要在署名里明说?

这是什么

Strata 是 GitHub 上的一个项目,具体用途社区还在扒。有开发者本想跑它自带的更新脚本,结果 git 报错说找不到共同祖先节点,一查才发现:所有历史 commit 都被重写,所有'Co-Authored by Claude'(由 Claude 共同编写)的署名痕迹被清干净。Reddit 用户 dasbin 把它挂到 r/LocalLLaMA,讨论量不小。技术上重写历史不难,问题在于动机——一家项目为什么要费这么大劲去抹这个?

行业怎么看

支持披露的一方认为:开源的核心契约是诚实,用了 AI 写就该说,这是底线。反对者也不示弱:工具辅助不等于抄袭,IDE 自动补全我们也没在 commit 里逐条标注,凭什么 AI 助手就要单独挂名?

我们更在意的是被忽视的第三种声音:这种系统性抹除,会让代码审计、合规追溯、开源许可证合规都变得困难。事情值得警惕的地方在于——当项目被企业采购、被集成进关键系统时,'这段代码谁写的、出了事谁负责'这个问题的答案,正在被技术性地抹掉。Strata 不是孤例,只是恰好被抓到。

对普通人的影响

对企业 IT:代码采购和审计流程可能很快要多一条——AI 生成比例披露,这是合规新坑。

对个人职场:程序员简历上'我独立完成'的含金量正在被重估,人和 AI 协作的边界会越来越需要说清楚。

对消费市场:未来买软件、买课程,'人类手作'会不会变成一种新的溢价标签,值得观察。