Comment by areoform
16 hours ago
Identity verification won't work. Nothing will. They are paying (and will continue to pay) US citizens sitting at home to copy-paste / type prompts out if they have to. But eventually they won't have to.
Once there are enough spam PRs on github / uploads of claude conversations, enough mythos output used in production etc.; it'll just be the same albeit delayed. Doesn't matter either way.
I feel for Anthropic's team and I understand where they're coming from, but once you reason it out, you'll come to the conclusion that this war is an exercise in futility.
Unlike prior systems - like Google's algorithm; these models aren't entities that use math in the process of doing X or Y (information retrieval from such and such infrastructure) -- they are the math. More precisely they're mathematical functions. Very very complex functions. Almost certainly impossible to write out without filling up a library functions. But they're mathematical functions nonetheless.
So when your text is processed, then Mythos / Opus etc at their core compute the result of the Mythos / Opus function,
f(text) -> (text_transform)
where f is a continuous function, https://www.turing.ac.uk/sites/default/files/2025-11/languag...
According to the Stone-Weirstrass theorem (edit, it's Stone-Weierstrass with an e.), with enough data points and mathematical sophistication, anyone can approximate the shape of this function.
Of course, the more data we get, the better our approximation becomes, but the beauty of it is that all we fundamentally need are the input and output and eventually we'll create a good enough approximation of the f that's Mythos. Which is the entire product.
I bounce ideas off of Opus these days (Fable for the brief time it was available) and it pointed out that this is arguably the same as Google search, but I disagree with it because Google search is a process;
Google search differs because the algorithm is one step of a multi-step process that is continuously occuring. Google crawls pages. Google stores and indexes what it finds. Google then exposes this to retrieval via its algorithm. User uses algorithm.
Google isn't a mathematical function. It used to be a process. (RIP Google 1998-2019, you will be missed and remembered)
You cannot arrive at the results of those operations via simple observation; not unless you index Google by making another Google.
You can however, do so for these models. It is a very costly process, but there are many paths up the mountain. Many ways for this to be ultimately pointless. As many ways as there are bored mathematicians.
It's better in the long run for Anthropic et al to make friends / not give people a reason to sneak in (a la piracy -- another attempt to control information) than it is to try and shut people out.
And no, it's not going to be pandemonium because if everyone has access to Mythos then no one has access to "Mythos."
Why wouldn't you first run this model to fix the obvious bugs it could find on your codebase? The power of a Mythos goes away if you can do the amazing "jail break" of "Claude, fix all the bugs please."
Just saying.
That's an insightful perspective and I think I largely agree. But just for fun, I wonder if that isn't an argument in favor of making the function implementation impure. Perhaps "enhancing" all queries with some sort of search result (or query of a giant db) instead of charging for an explicit tool call. Not only is it sorely needed to prevent stale data but (on the process level) it breaks the purity assumption on which the approximation theorem depends (alternatively on the function level it introduces hidden inputs).
This is why every AI company does crawl today.
Do they just reshape the function on the fly or save the process steps? Maybe it doesn't matter anymore. Even Google indexes are more and more spoiled to become representation of the function, because of the AI slop.
Genuine live data is king.