The Supreme Court has long made surreptitious changes to its opinions without telling anyone. In response, a coder has created a tool to flag & publicize those changes. This otherwise would not be practically possible… Until now.
The only way changes to a Supreme Court decision could be detected in the past was a pain-staking comparison of earlier and later copies — provided, of course, someone knew a decision had been changed in the first place. Which was unlikely.
Enter the crafty code of David Zvenyach, general counsel to the Council of the District of Columbia, who, in his spare time, likes to experiment with computer code. It all started when he read a New York Times article by Adam Liptak outlining how original statements by the Justices about everything from EPA policy to American Jewish communities, were disappearing from decisions. The article was based on a study by Harvard law professor Richard Lazurus.
Altering court document records after the fact… with new language that says something entirely different, as you can imagine, is a problem for lawyers, scholars, journalists and everyone else who relies on Supreme Court opinions. Plus, it’s literally & figuratively… against the law. Knowing this Zvenyach decided to so something about it.
The @Scotus_servo account on twitter is but one example of simple code improving judicial transparency. Another is @FISACourt, inspired by Zvenyach, and crawls the docket of the country’s controversial spy court & alerts the public when there’s a new development in important cases about government surveillance.
These tools appear so cheap to create & deploy. They deliver such obvious benefits. Its strange, but no wonder courts and government websites don’t integrate them as a matter of course. And yet, it matters not. As in the case of the Supreme Court, it appears a single man’s simple script is for now the best way for the public to stay up to date on unannounced changes to the law of the land.