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.