people who are so unskilled in writing even a paragraph and need to have it generated for them are usually not skilled enough to notice the extremely rote, trite cliches that LLMs abuse over and over again, that make it glaringly obvious it's slop.
the the short quippy triplicate comparisons, the inability to contradict itself or reference itself, it's a stink you can pick up immediately and if I see it, it tells me you either can't tell, or didn't read it.
Yeah, it should be freely available, you have to be able to know the rules you're supposed to obey in order to obey them well. I've been making a free API for US law search, you can point whatever model you want at it: https://law.agentlookups.ai/
Very much a work in progress, only federal and state so far, no municipal codes yet, and no case law yet. Big hole, I know. Also working on making the search ranking work better.
Right now it's just a bunch of crawlers for the individual states. If there's interest, I could periodically stand up snapshot torrents or something. That something you'd be interested in?
Alternatively, if someone else knows an all-in-one option that exists, I wouldn't mind retiring those crawlers...
Not op, but that's a very interesting proposition. While the law and legal code are technically property of the people, I'm not aware of any single point of download for it all.
There’s no single point of download for it all because there’s thousands of autonomous entities that issue law and adjudicate cases, at least 51 of them distinct sovereign entities.
We could enforce (suggest?) a common format / api at the federal level. Especially if it’s incentivized with funding that more than justifies the cost of maintenance. Similar to how federal interstate funding is only available to states with a 21+ drinking age.
Yeah, going to the courts and municipal code seems like it's going to be a heavy lift. Many of them seem to hang off of municode, though, so maybe it's not a huge number of unique crawlers.
There is none, not for statutes and definitely not for case law; even at the appellate level where you have multiple federal circuits, then 50 states, then territories, military, tribal and a whole host of other niche courts. And the appellate court systems can be split into districts, and by lower and higher levels.
Then if you want to really get into it, The People should also be able to access trial court level, and at that point you have over 3000 distinct court systems with their own access systems, usually requiring logins and CAPTCHAs, and half of them not even having anything accessible online at all, and the other half only having recent stuff online and the rest rotting in a flooded basement.
That’s awesome! I especially like RECAP as a method for freeing things from PACER.
Seems like you all are already doing a lot of what I’ve been aiming for with mine. Are there useful ways to contribute, or have you all gotten it to a pretty good place technically, and it’s mostly a matter of spreading it at this point?
> By using the legal search index, Astra for Law can search U.S. case law, statutes, regulations, court rules, and administrative decisions across a corpus of more than 230 million URLs, with sources added daily. Our work with Free Law Project, the nonprofit behind CourtListener, brings its case-law collection covering more than 99.9% of published U.S. precedential case law (opens in a new window) into this research experience.
CourtListener already has an MCP interface and Grok is quite good at pulling from it. In my experience, Grok 4.6 is quite good at analyzing legal cases and human-written documents. Better than Opus 5. I'm not sure if it's better than Fable 5.1 on that task, b/c I'm not willing to spend my precious Fable tokens on case law searches lol.
Git is incredibly mediocre. But it's all most people know. It's a version control tool that can't handle binary files; and no GitLFS does not count. The end result is a version control tool that is unable to actually version control all the things you need for a project.
This results in a Meta VCS layer where a ton of critical assets are stored in Docker files and other misery. If you want to re-compile a project for 2015 then good luck and god speed.
Personally I think full toolchains belong in source control. And that you should be able to clone / materialize a repro, yank your network cable, and build. This is how big tech monorepos work. It is TheWay imho.
IMO screw that. It's maybe a good way to build software in exactly one environment for exactly one environment, deployment to a corporate server fleet.
Consider a Linux desktop distro: if every little binary (out of order of magnitude 1000) acted like the center of the universe with gigabytes of build environment and "opinions" galore instead of portability, builds would take much more resources than they already do and parts wouldn't necessarily work together.
The .git directory does not contain plain files, so the same files may look different in different .git directories. But yeah, you could make it work if you designed for it.
Visual Studio and Xcode take up tens of gigabytes, are updated often, and include system components. Storing them in VCS is impossible, and would be a waste of disk space.
Disagree. They’re stored _somewhwre_ anyway, and they may as well be versioned.
Putting toolchains in perforce is how it works for lots of C++ shops, the setup instructions are “sync and hit build”, whether there’s a toolchain upgrade required or not
Threw $10 at this to help me prepare for my league’s fantasy auction this weekend. It spend $3.50 and then said “this action would cause you to go above your spending limit”.
Then I threw $100 for a Codex Max sub and it included Astra and it did it for me.
It does when you have a team of 100's of engineers every change has to pass through, 3 layers of management, SRE teams, DevOps YAML engineers, product management and a partridge and a VP.
> You don't know that they didn't read it!
If someone sends me AI slop to read then I am going to assume and behave as if they didn’t read it until proven otherwise.
It is the responsibility of the sender to proactively say “I read this and stand by it as at least mostly correct and reasonable”.
They are also free to say “AI slop have not yet proof read”. Then I have an informed choice.
reply