Rain, who helped build Meta’s Mononoke source-control server, sees a familiar design in Anthropic’s Scion. Their objection is not that Anthropic reused open-source ideas: it is that the announcement’s credit understates how closely the systems resemble one another, while presenting Claude as a designer.

The essay puts the descriptions side by side:

  • Both use “derived data”: extra indexes built from recorded changes to make questions like who last edited a line faster to answer.
  • Rain argues the similarity extends to the terminology and architecture, not merely a shared goal.
  • They welcome reuse, but call for specific credit to the earlier system and its builders. They also report that asking models about earlier designs surfaces Mononoke.

The useful distinction is between permission to reuse a design and responsibility to acknowledge it. Rain’s argument is that LLM assistance makes checking earlier work easier, not attribution less necessary. The essay alleges insufficient credit; it does not establish how Scion’s designers arrived at the design.

The thread on Hacker News adds a real disagreement about what adequate credit means.

What the thread adds

  • BryantD — disputes the missing-credit framing: “Mononoke is a component of Sapling, as I understand it. In fact, the repo link provided in this article links to a subdirectory of the Sapling repo. I’m not totally sure I understand the complaint.”
  • sunshowers — initially alleged: “Here the data model is a direct copy, down to the terminology.” In a later reply, Rain reports receiving private correspondence confirming deliberate reuse: “Claude was pointed directly at Mononoke and asked to re-engineer it.” That changes the author’s stated basis from inference about similarities to a reported private confirmation. The correspondence is not supplied in the comment, so this remains Rain’s account, not independently verified evidence of Scion’s development process.
  • MeetingsBrowser — reports a separate agent-coding experience: “And then I noticed some links to images from random small github projects and realized somewhere along the way agents had searched for existing projects and copied almost everything.” An anecdote, not evidence about Scion.
  • arjie — offers a non-model-specific explanation for familiar architecture: “People carry in their head what they know.” Mawr objects that “Coming up with the idea of an index is not a novel thought.” Rain’s later reply disputes that narrower framing: the claimed resemblance concerns the changeset model and server design, not indexing alone. The disagreement is about the specificity of the shared design; similarity by itself does not settle provenance.
  • sunshowers — specifies the requested correction in a follow-up: “Yes, and I would like it to explicitly say that their data model is very similar to Mononoke’s, and avoid even the appearance of the idea that Claude came up with it de novo.” In another reply, the author makes the boundary explicit: “I am appealing to norms, to basic decency.” They are not asking for attribution to become a legal requirement.
  • simonw — accepts the request to name Mononoke alongside Sapling, but disagrees about the announcement’s implication: “I didn’t think that their article implied Claude had come up with the design.” The distinction matters: inadequate specificity of credit and a claim of model originality are separate objections, not established facts about how Scion was built.

Handles are pseudonymous. HN exposes no per-comment scores; its ordering is HN’s own ranking. This is a slice of the thread, not a consensus.