Obviously it would be great if this caught on, but it's not even widely understood/agreed on that read-time precision is a desirable quality in a legal system.
This is something almost everyone here takes for granted; we want the interpreter or machine to give the same result for the same input.
We want that property so we can know the run-time behavior during development.
There are judges and politicians in the US that advocate for various "interpretations" of laws including parts of the constitution, which are different from what the law literally says.
In fact they refer to the literal meaning as the "literal interpretation", implying it is one of many valid interpretations, and casting doubt on the idea of language having a precise meaning.
The crowd here knows that it is totally possible and often invaluable to work in languages with precise meaning.
Anyways, in practice this means: all the steps happened for the law to get passed by the legislature including arguing about the exact text, and instead of enforcing it as written, the judiciary enforces some slightly different but similar law.
A technology like this necessarily concentrates power in the legislature, and takes it away from the judicial system.
It concentrates legal power at write time and removes it from run/read time.
Catala is specifically for tax codes and other laws that involve formulas and calculations, not all laws, so I don’t think most of your concerns apply to it specifically. There are often complicated rules governing how, e.g. benefits or tax credits are calculated that natural language is clumsy at expressing, so having a formal language that encodes that logic seems useful.
I agree government/justice by algorithm would be very dangerous, but Catala does not seem to be that.
It’s also the case that the massive set of constantly evolving case law is akin to the most convoluted and buggy “libc” ever implemented, running on a system where random bit flips occur frequently. Any lawyer who says they know how to definitively encode an assumption is inherently making a probabilistic statement colored by their own experience and definitionally limited exposure to case law - it may be near perfect, but it exists in an imperfect runtime environment.
This doesn’t mean that this isn’t a useful tool as an aid for interpretability. And perhaps we can reach a point where ambiguity in case law can “propagate” through a graph of nodes to give a range of answers to any question about a regulation - perhaps with the aid of LLMs. But until we have such a system, it can be dangerous to draw conclusions from systems like this one.
> "interpretations"... which are different from what the law literally says.
We have to remember that the letter and spirit of the law can grow apart over time, and loopholes are often gamed before that naturally happens anyway. So obviously we still need judges to keep the "spiritual" aspect of intent alive, so that evil isn't laundered through technicality.
"Literal" should really be a concrete thing, but it does feel strangely connected to a problem that has existed since Sola Scriptura, up to Gödel's theorem. I think about this everytime software and law collide. That article on "what color are your bits"[1] also comes to mind.
Curiously enough, law in the US, which inherits from Common Law, is heavily focused on the interpretation (the case law) in the courts of the written law, as opposed to the written words themselves. This is in contract with civil law, napoleonic law and Japanese law, which places greater importance on the written words themselves.
Do you really want, for example, the US constitution's write time understandings to be perpetuated forever? Their understanding of "citizen" did not include neither women nor black slaves, just to take one example. Another example is the famous question of "whether or not the right of a woman to abortion is a consitution-guaranteed federal right?" to which a bunch of very important folks gave an answer in 1973 but another bunch of very important folks gave a different answer in 2022.
Write-time understandings no, write-time language yes.
You can always change it, which is what happened in the case of women and slaves.
To be clear, changing the text is the correct way to handle that, we shouldn't have just relied on the understandings of people changing over time to fix those issues.
The famous example you give illustrates why a system without precise meaning cannot work. It can seem like it works when lots of people act in good faith, but it quickly breaks down with even a few actors play the actual game instead of some "spirit of the game".
In 1973, judges ruled one way, playing the actual game to accomplish a goal, and then everyone acted surprised in 2022, when the same tactics (playing the actual game not the spirit) reverted the decision.
I'm going to take a guess, and assume that you were in favor of the 1973 understanding and not the 2022 understanding. It would have been nice for that to have been captured precisely in some kind of specification, instead of enacted with a volatile read-time mechanism.
I don't live in the US and I'm rather indifferent to either understanding, so it would be correct to say that I'm neither in favour nor in opposition of any one of these. Being personally unaffected, I simply find it an interesting subject to observe.
With that, I still want to point out that even if we both agree that "changing the text is the correct way to handle," it's not a possibility that is even remotely practical or achievable; any meaningful progress that the US have had in the last 100 years or so was achieved solely by the means of "reinventing" the meaning of already written (and unchangeable) words. That seems to be the exact thing you seem to be in opposition of.
I have a potentially more optimistic (and simultaneously more pessimistic!) view to offer.
Some differing interpretations of the law distinguish between the lawmakers' intention vs the literal meaning (and keep in mind that language itself changes a lot in just a few centuries. The hard problem is that, in PL terms, the law is written in syntax without agreed upon semantics. So a decent step could be just using some agreed upon semantics, like we do in code! Then at least "interpreting" it would be unambiguous.
Maybe a decent analogy would be gcc vs clang might produce different programs for certain undefined behavior, and different combinations of pieces might lead to different behavior too (like race conditions), and somebody (the plaintiff/user) is asking you (the judge/compiler) to decide what's going to happen in this next loop/program/whatever.
Or maybe a decent analogy would be getting a ticket that the API is erroring in some rare user's case and having to look into the code and stacktrace to realize it's some weird unanticipated interaction between two different pieces of legacy code (150 year old law) that now interact due to a recent merge (a new law from last year), and now it's crashing, so we have to figure out how to interpret/compile/resolve this user's case.
If law was usable like code, we'd never have any of those issues, just like we never have those issues with actual literal programs. And when we do, it's just because we're using the wrong language/aren't encoding enough things in the types and semantics/shouldn't have used this niche compiler so now let's get a new interpretation from another Supreme Compiler/etc. Life would be easier \s
So it's maybe more optimistic than you, in that the run/read time power (judicial) doesn't get diminished, but more pessimistic in that I believe it because I believe that changing the language from english law jargon to some formal language doesn't actually eliminate the issues it might be intended to eliminate.
We really need this in India. There are 53 million cases which are pending in courts, with over 180k cases open for more than 30 years (see https://en.wikipedia.org/wiki/Pendency_of_court_cases_in_Ind...). It is estimated that more than 300 years will be taken to dispose of all cases.
If law code is a repository:
1. Each trial should be encoded into a law.
2. If the trial is already covered sufficiently in the codebase, and both parties agree to it result. Then case is solved.
3. If not, the new judgement leads to a "pull request" into the codebase.
Catala is a fantastic project and a real attempt to bring computer science and law together. Which is not easy!
That said, for practical projects in legaltech a modern pure Prolog system has a lot of useful properties. A project that attempts to use Scryer Prolog for this is VATmiral.
I've thought a lot about law-as-code, but my conclusion is always that bad actors will be given an advantage by being able to brute-force the code until they find a way to get away with whatever obviously-immoral-harmful stuff they want (imagine giga-corps spending a few millions on hardware to brute-force tax law - ROI probably even better than tunneling through mountains to grab stonks first..).
In the end it reminds me of a quote by Edmund Burke:
"Bad men obey the law only out of fear of punishment; good men obey it out of conscience - and thus good men are often restrained by it, while bad men find ways around it."
I'm wondering if it might be impossible to write a law that both prevents the sprit of what we want it to prevent, while also not preventing the spirit of what we don't want to prevent. :)
> The aim is not to formalise or put into code all the law, because that would make no sense, but we are interested in the law that is already executed automatically, such as the calculation of social benefits, tax or unemployment.
Can anyone explain why it's believed this "would make no sense"?
It does stand to reason that all law could be formalized. For example, consider the definition of murder in the first degree from 18 USC § 1111:
"Murder is the unlawful killing of a human being with malice aforethought."
You might say, well, "unlawful" and "malice" are fuzzy concepts; but we can take them to be facts that we input into the model. I guess we could write something like this in Catala:
scope Murder :
definition in_the_1st_degree
under condition is_malice_aforethought and is_unlawful consequence
equals
true
In the calculation of social benefits and taxes, the facts input to the model are generally things like prices, depreciations, costs, areas of offices, percentages and so on, input numerically and sworn to be true. These numbers are then used to calculate an amount due (or in arrears). Performing the calculation in a way that is verified to conform to the law is a big part of the work.
However, in other areas of law, determining the facts is actually where the real work is -- was there malice aforethought? A formalized legal machine could process these facts but it's not a big help. The models would just be a huge list of assumptions that have to be input and a minimal calculation that produces `true` or one of the alternatives of an enum.
Law isn't written to cover 100% of real life scenarios and potential cases, it's written with deliberate parts of ambiguity, that will ultimately be up to courts to set the precedents for, in various situations and context.
I think the idea is that you can't really cover 100% of real-life cases in "code", either legal or software, so the areas you'll leave this out of would be those "not-entirely-strict" parts.
A computer program takes digital bytes, runs some discrete logic on them, outputs some more bytes. Laws take messy real world stuff, run some subjective decision tree on them, and output some messy real world actions to take. If you model the former with the latter you end up 'shelling out' to human judgement every 2 words. Suppose you accidentally shoot somebody while duck hunting, the meaning or value of pretty much everything here can't be determined by a computer, so the code-law version of this random snippet of natural-language-law would be pretty useless:
> If it is found that the defendant did the killing or wounding, but that it was not intentional or negligent, the court shall dismiss the proceeding. Otherwise, if it is found that the defendant did the killing or wounding intentionally, by an act of gross negligence, or while under the influence of alcohol, the court shall issue an order permanently prohibiting the defendant from taking any bird or mammal.
A lot of law is based around subjective gray lines. “How would a reasonable person behave in this unique situation?” Is at the root of a lot of legal situations.
Write a function for that, keeping in mind that “this situation” needs to be modeled with potentially infinite variables. Then try to define a “reasonable person”.
Hell, the reason most trials happen is because there is huge grey area, and the written laws are not obvious as to what the outcome should be.
I think the primary reason is that laws are about human convention, not real objects which one can clearly and deliberately define. Like at the most basic level nothing exists at all except for quantum fields or something like that. Everything else we talk about on a regular basis, people, dogs, streets, businesses, etc, is defined by convention to a greater or lesser degree.
It is therefore quite hard to create a formal system to refer to objects in the world in a way which induces no contradictions with intuition. This is why we have courts, among other functions of government.
> Basically, all human knowledge is an application of either math or philosophy
Philosophy is not knowledge, it's pure speculation.
> law is philosophy, so cant be modeled by math
Law is not philosophy unless it was written based on sloppy speculations. In other words, what law is, depends on how it was written, it can certainly be modeled by logic and math methods can be developed for it too.
It's nothing new, lawyers have to master logic as part of their training.
Modelling intent, with math, is not going to happy. Law is based around the intent of those taking actions, and understanding intent is absolutely philosophy.
Understanding intent is understanding interest and that's not philosophy. If it's not about interest, it's psychiatry - not philosophy either.
Besides, only a lesser part of law is about intent, the major part is about punishing and avoiding harm, finding the true facts and applying the written law to them.
Down-voting can't change the truth, we've been led by the nose for far too long.
Intent has been the core underiding feature of the law since the Magna Carta. To ignore or trivialise it is nothing short of advocating for the return of kings.
> Intent has been the core underiding feature of the law since the Magna Carta.
I've already explained that intent is another word for interest - material or political, it may not be as trivial as potato chips but it's far simpler than rocket science.
> To ignore or trivialise it is nothing short of advocating for the return of kings.
Another purely speculative assertion with zero meaning or practical value.
There's no logical path from trivializing your occultist and unknowable notion if intent to the return of kings. First, you've got to start with a proof that at present there aren't any kings... but philosophy's got no proofs.
Speaking of kinks (sic), wasn't Epstein one of them? Or at least under their protection... until he wasn't, as usual.
If intent were so simply explained, then the High Courts across the world would serve no function - as interpreting intent is their core role.
Material interest and intent only accidentally collide. Intent cannot be defined in that manner.
Almost every person beneath a capitalist system has a material interest in wealth. That does not translate to intent to seize it.
If intent does not matter, only interest, then there is no war crime in bombing boats. There is no arguing with the government's interpretations of law, as they will have a vested interest as to how it plays out.
The "test of intent" is not a part of law to be so offhandly thrown aside.
> Almost every person beneath a capitalist system has a material interest in wealth. That does not translate to intent to seize it.If intent does not matter, only interest, then there is no war crime in bombing boats.
That's a different topic, legislative intent is different from criminal intent, the latter does not change the fact of wrongdoing, only the severity of it. Bombing sailors in a wreckage situation is either a war crime or gross military incompetence which may lead to court-martial. This together with interest-as-motive are decided based on facts and logic, not philosophy - these arguments support my view, not yours.
scope QualifiedEmployeeDiscount :
definition qualified_employee_discount
under condition is_property consequence
equals
if employee_discount >=
customer_price \* gross_profit_percentage
then customer_price \* gross_profit_percentage
else employee_discount
It feels like the best of both worlds, a syntax that is new and strange to use while basically being the same old abc If Else programming language.
Not sure I'm seeing any law-specific features either. Maybe if there were some tokens like 'jurisdiction' or 'jurisprudence', but it seems like yet another programming language.
I wonder what people who speak the actual Catala have to say about this semantic appropriation. It would be very easy for creators just to google it first.
Napoleon's only been gone for about two hundred years, whereas Common Law has some real classics. For example https://en.wikipedia.org/wiki/Statute_of_Merton was a set of laws promulgated in 1235, some of which remained in force (at least nominally) until the 1980s. I don't know much about Canon Law, but that surely goes back even further.
All that to say, you can just do your best to understand the law in the the context in which it was written, and replace the text every now and again.
Not even unrelated, Catala (the law-language) seems to be a French project, supported by institutions in France, and Catalan seems to have a intertwined history with France: https://en.wikipedia.org/wiki/Catalan_language#France
> The language is named after Pierre Catala, a professor of law who pionneered the French legaltech by creating a computer database of law cases, Juris-Data.
That’s not correct, the accent is simply there to know how to pronounce the word, and while in some specific cases (diacritic accent) it is there to avoid confusion in words that are pronounced the same with different meaning, the presence or lack of accent does not as a rule change the meaning of a word.
In this case, catala and català mean the same thing, one is simply misspelled as all words with the strong syllable being last will always have an accent mark if they end in a vowel.
Your first paragraph insists that "the presence or lack of accent does not as a rule change the meaning of a word." While your second insists that "[the same word without an accent] is simply misspelled as all words with the strong syllable being last will always have an accent mark if they end in a vowel."
But your accent rule also isn't followed by the language you claim uses it as a hard and fast rule: in the case of the single syllable Catalan word ma (my, femenine) and mà (hand). Please square that with your declaration that " all words with the strong syllable being last will always have an accent mark if they end in a vowel." Seemingly ma is breaking your rules, as well as your assertion that missing the accent is only a spelling error. In this, and many other cases, the accent completely changes the meaning of the word which also contradicts your assertion I highlighted in paragraph 1. Maybe "as a rule" isn't the correct phrase given the multitude of words that can change meaning with an accent mark.
The broader thing you missed is that Catala is the last name of a person working on the project, and is not missing an accent. That is how the person's name is spelled. Even in Catalan. Català is a Catalan word refering to a different thing. In this case the accent is incredibly important since it helps us differentiate between a man's name and a language.
In both the figurative and spelling sense we must therefore conclude that, in reality:
You clearly don’t even speak the language and are just fishing for an argument. I have already explained why your comment is incorrect, have nothing else to say to you on that subject if you insist that the accent mark will completely change the meaning without understanding that the accent in català follows the normal ortographical rules while the accent in mà is diacritic, a special rule that only applies to often monosyllabic words.
mà / ma does not break the general rule because the word does have an accent mark, it just also falls under the diacritic special rule.
On your point about the author’s last name, it’s fair, but also you’re ignoring that the last name comes from the same word and is thus a spelling variation from French/Occitan, further proving your assertion of Catala != Català as wrong.
> You clearly don’t even speak the language and are just fishing for an argument.
Please refrain from making negative assumptions about my language skills and motives. I am not a native speaker of the language, but I do read and understand it fine. This is not the place for passive or backhanded personal attacks.
> I have already explained why your comment is incorrect, have nothing else to say to you on that subject...
Since you made it personal, and then went on to say quite a bit on that subject I will provide my comments:
Thank you for acknowledging the validity of my points. I hear your argument, but it doesn't invalidate mine. Either an accent mark has no bearing on the meaning of a word or it does. I have demonstrated that it is absolutely and undeniably the case that an accent mark can change the meaning of a word in Catalan.
My original assertion is, verbatim: "...the accent can completely change the meaning of a word". You aren't arguing that ma and mà are the same word, despite your assertion that "the presence or lack of accent does not as a rule change the meaning of a word".
I don't address formal grammatical rules, and I am not arguing against your interpretation, it is correct AFAICT. I understand that there are rules for placing accent marks, which is why I asked you to explain the full rule when I was able to easily contradict the grammar rule. That doesn't contradict my argument.
The argument is simply that the placement of an accent changes the meaning of some words in Catalan. There was a side argument that if the last syllable is stressed it must have an accent on the vowel, which you asserted was true "as a rule". That was not true, as evidenced by you having to explain when it doesn't work "as a rule". It can be the case that accent marks have rules for when they are written, and also be the case that different words can have the same letters and differ only in the accent. Both of our arguments are correct.
In this exact case that is what is happening. Catala is a niche programming language named after a french man. Català is a language. The presence of the accent is distinguishing meanings between Catala and Català. I can write the following: "Parlo català, però no se res sobre el llenguage Catala", and the presence or absence of accents will mean the difference between that sentence being gibberish and that sentence meaning something. Likewise, Ma, si, dona, que, etc. can all have an accent added to them to give them a completely different meaning in Catalan. It is unequivocally true, and I don't know why you would assert otherwise.
Obviously it would be great if this caught on, but it's not even widely understood/agreed on that read-time precision is a desirable quality in a legal system. This is something almost everyone here takes for granted; we want the interpreter or machine to give the same result for the same input. We want that property so we can know the run-time behavior during development.
There are judges and politicians in the US that advocate for various "interpretations" of laws including parts of the constitution, which are different from what the law literally says. In fact they refer to the literal meaning as the "literal interpretation", implying it is one of many valid interpretations, and casting doubt on the idea of language having a precise meaning. The crowd here knows that it is totally possible and often invaluable to work in languages with precise meaning. Anyways, in practice this means: all the steps happened for the law to get passed by the legislature including arguing about the exact text, and instead of enforcing it as written, the judiciary enforces some slightly different but similar law.
A technology like this necessarily concentrates power in the legislature, and takes it away from the judicial system. It concentrates legal power at write time and removes it from run/read time.
Catala is specifically for tax codes and other laws that involve formulas and calculations, not all laws, so I don’t think most of your concerns apply to it specifically. There are often complicated rules governing how, e.g. benefits or tax credits are calculated that natural language is clumsy at expressing, so having a formal language that encodes that logic seems useful.
I agree government/justice by algorithm would be very dangerous, but Catala does not seem to be that.
It’s also the case that the massive set of constantly evolving case law is akin to the most convoluted and buggy “libc” ever implemented, running on a system where random bit flips occur frequently. Any lawyer who says they know how to definitively encode an assumption is inherently making a probabilistic statement colored by their own experience and definitionally limited exposure to case law - it may be near perfect, but it exists in an imperfect runtime environment.
This doesn’t mean that this isn’t a useful tool as an aid for interpretability. And perhaps we can reach a point where ambiguity in case law can “propagate” through a graph of nodes to give a range of answers to any question about a regulation - perhaps with the aid of LLMs. But until we have such a system, it can be dangerous to draw conclusions from systems like this one.
(Not a lawyer, this is not legal advice.)
> "interpretations"... which are different from what the law literally says.
We have to remember that the letter and spirit of the law can grow apart over time, and loopholes are often gamed before that naturally happens anyway. So obviously we still need judges to keep the "spiritual" aspect of intent alive, so that evil isn't laundered through technicality.
"Literal" should really be a concrete thing, but it does feel strangely connected to a problem that has existed since Sola Scriptura, up to Gödel's theorem. I think about this everytime software and law collide. That article on "what color are your bits"[1] also comes to mind.
[1]: https://ansuz.sooke.bc.ca/entry/23
Curiously enough, law in the US, which inherits from Common Law, is heavily focused on the interpretation (the case law) in the courts of the written law, as opposed to the written words themselves. This is in contract with civil law, napoleonic law and Japanese law, which places greater importance on the written words themselves.
Do you really want, for example, the US constitution's write time understandings to be perpetuated forever? Their understanding of "citizen" did not include neither women nor black slaves, just to take one example. Another example is the famous question of "whether or not the right of a woman to abortion is a consitution-guaranteed federal right?" to which a bunch of very important folks gave an answer in 1973 but another bunch of very important folks gave a different answer in 2022.
Write-time understandings no, write-time language yes. You can always change it, which is what happened in the case of women and slaves. To be clear, changing the text is the correct way to handle that, we shouldn't have just relied on the understandings of people changing over time to fix those issues.
The famous example you give illustrates why a system without precise meaning cannot work. It can seem like it works when lots of people act in good faith, but it quickly breaks down with even a few actors play the actual game instead of some "spirit of the game". In 1973, judges ruled one way, playing the actual game to accomplish a goal, and then everyone acted surprised in 2022, when the same tactics (playing the actual game not the spirit) reverted the decision.
I'm going to take a guess, and assume that you were in favor of the 1973 understanding and not the 2022 understanding. It would have been nice for that to have been captured precisely in some kind of specification, instead of enacted with a volatile read-time mechanism.
I don't live in the US and I'm rather indifferent to either understanding, so it would be correct to say that I'm neither in favour nor in opposition of any one of these. Being personally unaffected, I simply find it an interesting subject to observe.
With that, I still want to point out that even if we both agree that "changing the text is the correct way to handle," it's not a possibility that is even remotely practical or achievable; any meaningful progress that the US have had in the last 100 years or so was achieved solely by the means of "reinventing" the meaning of already written (and unchangeable) words. That seems to be the exact thing you seem to be in opposition of.
Wouldn't 1973 be spirit based and 2022 be text based in this instance?
[dead]
I have a potentially more optimistic (and simultaneously more pessimistic!) view to offer.
Some differing interpretations of the law distinguish between the lawmakers' intention vs the literal meaning (and keep in mind that language itself changes a lot in just a few centuries. The hard problem is that, in PL terms, the law is written in syntax without agreed upon semantics. So a decent step could be just using some agreed upon semantics, like we do in code! Then at least "interpreting" it would be unambiguous.
Maybe a decent analogy would be gcc vs clang might produce different programs for certain undefined behavior, and different combinations of pieces might lead to different behavior too (like race conditions), and somebody (the plaintiff/user) is asking you (the judge/compiler) to decide what's going to happen in this next loop/program/whatever.
Or maybe a decent analogy would be getting a ticket that the API is erroring in some rare user's case and having to look into the code and stacktrace to realize it's some weird unanticipated interaction between two different pieces of legacy code (150 year old law) that now interact due to a recent merge (a new law from last year), and now it's crashing, so we have to figure out how to interpret/compile/resolve this user's case.
If law was usable like code, we'd never have any of those issues, just like we never have those issues with actual literal programs. And when we do, it's just because we're using the wrong language/aren't encoding enough things in the types and semantics/shouldn't have used this niche compiler so now let's get a new interpretation from another Supreme Compiler/etc. Life would be easier \s
So it's maybe more optimistic than you, in that the run/read time power (judicial) doesn't get diminished, but more pessimistic in that I believe it because I believe that changing the language from english law jargon to some formal language doesn't actually eliminate the issues it might be intended to eliminate.
We really need this in India. There are 53 million cases which are pending in courts, with over 180k cases open for more than 30 years (see https://en.wikipedia.org/wiki/Pendency_of_court_cases_in_Ind...). It is estimated that more than 300 years will be taken to dispose of all cases.
If law code is a repository: 1. Each trial should be encoded into a law. 2. If the trial is already covered sufficiently in the codebase, and both parties agree to it result. Then case is solved. 3. If not, the new judgement leads to a "pull request" into the codebase.
Can't wait for lawmakers to get a red CI before merging ;)
Jokes aside, I'm trying to imagine what a pull request workflow would be for law making.
For example, there might be a test that checks that a law has adequate budget before applying it; or to get an error if it conflicts with another law.
Also (Italian here), I would be very happy to do "git blame" and discover who actually introduced a modification.
Yes, this would make us programmers so happy wouldn’t it :)
Catala is a fantastic project and a real attempt to bring computer science and law together. Which is not easy! That said, for practical projects in legaltech a modern pure Prolog system has a lot of useful properties. A project that attempts to use Scryer Prolog for this is VATmiral.
I've thought a lot about law-as-code, but my conclusion is always that bad actors will be given an advantage by being able to brute-force the code until they find a way to get away with whatever obviously-immoral-harmful stuff they want (imagine giga-corps spending a few millions on hardware to brute-force tax law - ROI probably even better than tunneling through mountains to grab stonks first..).
In the end it reminds me of a quote by Edmund Burke: "Bad men obey the law only out of fear of punishment; good men obey it out of conscience - and thus good men are often restrained by it, while bad men find ways around it."
Right, but if laws were developed in regulatory sandboxes, you'd also have the opportunity to red-team them.
Might be a design idea for future lawmakers.
I'm wondering if it might be impossible to write a law that both prevents the sprit of what we want it to prevent, while also not preventing the spirit of what we don't want to prevent. :)
It probably is impossible, but you could cover a lot of cases with more deliberate design. For the rest, you can leave it up to the judges to decide.
Then again, that might be exactly how (some) lawmakers think, but I'm not aware of it.
> The aim is not to formalise or put into code all the law, because that would make no sense, but we are interested in the law that is already executed automatically, such as the calculation of social benefits, tax or unemployment.
Can anyone explain why it's believed this "would make no sense"?
It does stand to reason that all law could be formalized. For example, consider the definition of murder in the first degree from 18 USC § 1111:
"Murder is the unlawful killing of a human being with malice aforethought."
You might say, well, "unlawful" and "malice" are fuzzy concepts; but we can take them to be facts that we input into the model. I guess we could write something like this in Catala:
In the calculation of social benefits and taxes, the facts input to the model are generally things like prices, depreciations, costs, areas of offices, percentages and so on, input numerically and sworn to be true. These numbers are then used to calculate an amount due (or in arrears). Performing the calculation in a way that is verified to conform to the law is a big part of the work.However, in other areas of law, determining the facts is actually where the real work is -- was there malice aforethought? A formalized legal machine could process these facts but it's not a big help. The models would just be a huge list of assumptions that have to be input and a minimal calculation that produces `true` or one of the alternatives of an enum.
Law isn't written to cover 100% of real life scenarios and potential cases, it's written with deliberate parts of ambiguity, that will ultimately be up to courts to set the precedents for, in various situations and context.
I think the idea is that you can't really cover 100% of real-life cases in "code", either legal or software, so the areas you'll leave this out of would be those "not-entirely-strict" parts.
The same can be said about driving but self-driving cars exist.
So is the "bitter lesson" that fuzzy overlords will be practically preferable to hand coded legislation?
A computer program takes digital bytes, runs some discrete logic on them, outputs some more bytes. Laws take messy real world stuff, run some subjective decision tree on them, and output some messy real world actions to take. If you model the former with the latter you end up 'shelling out' to human judgement every 2 words. Suppose you accidentally shoot somebody while duck hunting, the meaning or value of pretty much everything here can't be determined by a computer, so the code-law version of this random snippet of natural-language-law would be pretty useless:
> If it is found that the defendant did the killing or wounding, but that it was not intentional or negligent, the court shall dismiss the proceeding. Otherwise, if it is found that the defendant did the killing or wounding intentionally, by an act of gross negligence, or while under the influence of alcohol, the court shall issue an order permanently prohibiting the defendant from taking any bird or mammal.
Have you been around on the internet when they discovered AI LLMs ?
A lot of law is based around subjective gray lines. “How would a reasonable person behave in this unique situation?” Is at the root of a lot of legal situations.
Write a function for that, keeping in mind that “this situation” needs to be modeled with potentially infinite variables. Then try to define a “reasonable person”.
Hell, the reason most trials happen is because there is huge grey area, and the written laws are not obvious as to what the outcome should be.
Commercial law nuts and bolts is very algorithmic often.
Criminal law is often fundamentally subjective, incorporating questions of intent and remorse.
I assume it would fail to compile, or error out, because of myriad conflicts throughout the body of laws.
I think the primary reason is that laws are about human convention, not real objects which one can clearly and deliberately define. Like at the most basic level nothing exists at all except for quantum fields or something like that. Everything else we talk about on a regular basis, people, dogs, streets, businesses, etc, is defined by convention to a greater or lesser degree.
It is therefore quite hard to create a formal system to refer to objects in the world in a way which induces no contradictions with intuition. This is why we have courts, among other functions of government.
Basically, all human knowledge is an application of either math or philosophy, and law is philosophy, so cant be modeled by math
> Basically, all human knowledge is an application of either math or philosophy
Philosophy is not knowledge, it's pure speculation.
> law is philosophy, so cant be modeled by math
Law is not philosophy unless it was written based on sloppy speculations. In other words, what law is, depends on how it was written, it can certainly be modeled by logic and math methods can be developed for it too.
It's nothing new, lawyers have to master logic as part of their training.
Modelling intent, with math, is not going to happy. Law is based around the intent of those taking actions, and understanding intent is absolutely philosophy.
Understanding intent is understanding interest and that's not philosophy. If it's not about interest, it's psychiatry - not philosophy either.
Besides, only a lesser part of law is about intent, the major part is about punishing and avoiding harm, finding the true facts and applying the written law to them.
Down-voting can't change the truth, we've been led by the nose for far too long.
To avoid harm, you must identify intent.
To punish, you must establish intent.
Intent has been the core underiding feature of the law since the Magna Carta. To ignore or trivialise it is nothing short of advocating for the return of kings.
> Intent has been the core underiding feature of the law since the Magna Carta.
I've already explained that intent is another word for interest - material or political, it may not be as trivial as potato chips but it's far simpler than rocket science.
> To ignore or trivialise it is nothing short of advocating for the return of kings.
Another purely speculative assertion with zero meaning or practical value.
There's no logical path from trivializing your occultist and unknowable notion if intent to the return of kings. First, you've got to start with a proof that at present there aren't any kings... but philosophy's got no proofs.
Speaking of kinks (sic), wasn't Epstein one of them? Or at least under their protection... until he wasn't, as usual.
If intent were so simply explained, then the High Courts across the world would serve no function - as interpreting intent is their core role.
Material interest and intent only accidentally collide. Intent cannot be defined in that manner.
Almost every person beneath a capitalist system has a material interest in wealth. That does not translate to intent to seize it.
If intent does not matter, only interest, then there is no war crime in bombing boats. There is no arguing with the government's interpretations of law, as they will have a vested interest as to how it plays out.
The "test of intent" is not a part of law to be so offhandly thrown aside.
> Almost every person beneath a capitalist system has a material interest in wealth. That does not translate to intent to seize it.If intent does not matter, only interest, then there is no war crime in bombing boats.
That's a different topic, legislative intent is different from criminal intent, the latter does not change the fact of wrongdoing, only the severity of it. Bombing sailors in a wreckage situation is either a war crime or gross military incompetence which may lead to court-martial. This together with interest-as-motive are decided based on facts and logic, not philosophy - these arguments support my view, not yours.
You definition of philosophy does not seem to match the broader scientific one.
Philosophy is the science of understanding logic. Founded on Aristotles, Plato, and others. Rational process is derived directly from philosophy.
An appeal to facts and logic, is and always has been, an appeal to philosophy.
Past discussions:
1. (https://news.ycombinator.com/item?id=27059899) - May 2021 (126 comments) 2. (https://news.ycombinator.com/item?id=28633122) - Sept 2021 (40 comments) 3. (https://news.ycombinator.com/item?id=37546874) - Sept 2023 (277 comments)
Not sure I'm seeing any law-specific features either. Maybe if there were some tokens like 'jurisdiction' or 'jurisprudence', but it seems like yet another programming language.
I suspect this works better outside of common law legislation.
Huh I just finished a book by Jaron Lanier that described a hypothetical system literally just like this. Always fun to get a coincidence like this
Serious question:
Is there any money to be made with this yet? (Jobs, Contracting, Projects, etc)
If not: What's the plan to get this to be used?
Sure - just add an AI and money will flow.
I wonder what people who speak the actual Catala have to say about this semantic appropriation. It would be very easy for creators just to google it first.
Yeah, I speak Catalan, and we call the language "català" in Catalan, I mean, I would say "Jo parlo català" to say "I speak Catalan".
I agree that maybe do a quick Google search would avoid this strange appropiation.
How does this incorporate case law?
That's not so important in Napoleonic/Civil jurisdictions like France. Judges can consider prior rulings, but the law as-written is the main thing.
How's that account for language drift over centuries?
Napoleon's only been gone for about two hundred years, whereas Common Law has some real classics. For example https://en.wikipedia.org/wiki/Statute_of_Merton was a set of laws promulgated in 1235, some of which remained in force (at least nominally) until the 1980s. I don't know much about Canon Law, but that surely goes back even further.
All that to say, you can just do your best to understand the law in the the context in which it was written, and replace the text every now and again.
Reminds me of smart contracts
[flagged]
Not even unrelated, Catala (the law-language) seems to be a French project, supported by institutions in France, and Catalan seems to have a intertwined history with France: https://en.wikipedia.org/wiki/Catalan_language#France
funnily enough, the relation comes from a french jurist's last name
from their repo: https://github.com/CatalaLang/catala
> The language is named after Pierre Catala, a professor of law who pionneered the French legaltech by creating a computer database of law cases, Juris-Data.
Also in their website https://catala-lang.org/en/about#naming
Name that is almost certainly related to Catalonia as well.
Catala != Catalan
Try clicking my "Catala" link and looking at the first sentence. The Catalan word for Catalan is català.
Great. You would know that the accent can completely change the meaning of a word in that language as such an expert.
So we can just say that catala != català
That’s not correct, the accent is simply there to know how to pronounce the word, and while in some specific cases (diacritic accent) it is there to avoid confusion in words that are pronounced the same with different meaning, the presence or lack of accent does not as a rule change the meaning of a word.
In this case, catala and català mean the same thing, one is simply misspelled as all words with the strong syllable being last will always have an accent mark if they end in a vowel.
Your first paragraph insists that "the presence or lack of accent does not as a rule change the meaning of a word." While your second insists that "[the same word without an accent] is simply misspelled as all words with the strong syllable being last will always have an accent mark if they end in a vowel."
But your accent rule also isn't followed by the language you claim uses it as a hard and fast rule: in the case of the single syllable Catalan word ma (my, femenine) and mà (hand). Please square that with your declaration that " all words with the strong syllable being last will always have an accent mark if they end in a vowel." Seemingly ma is breaking your rules, as well as your assertion that missing the accent is only a spelling error. In this, and many other cases, the accent completely changes the meaning of the word which also contradicts your assertion I highlighted in paragraph 1. Maybe "as a rule" isn't the correct phrase given the multitude of words that can change meaning with an accent mark.
The broader thing you missed is that Catala is the last name of a person working on the project, and is not missing an accent. That is how the person's name is spelled. Even in Catalan. Català is a Catalan word refering to a different thing. In this case the accent is incredibly important since it helps us differentiate between a man's name and a language.
In both the figurative and spelling sense we must therefore conclude that, in reality:
Catala != Català
You clearly don’t even speak the language and are just fishing for an argument. I have already explained why your comment is incorrect, have nothing else to say to you on that subject if you insist that the accent mark will completely change the meaning without understanding that the accent in català follows the normal ortographical rules while the accent in mà is diacritic, a special rule that only applies to often monosyllabic words.
mà / ma does not break the general rule because the word does have an accent mark, it just also falls under the diacritic special rule.
On your point about the author’s last name, it’s fair, but also you’re ignoring that the last name comes from the same word and is thus a spelling variation from French/Occitan, further proving your assertion of Catala != Català as wrong.
> You clearly don’t even speak the language and are just fishing for an argument.
Please refrain from making negative assumptions about my language skills and motives. I am not a native speaker of the language, but I do read and understand it fine. This is not the place for passive or backhanded personal attacks.
> I have already explained why your comment is incorrect, have nothing else to say to you on that subject...
Since you made it personal, and then went on to say quite a bit on that subject I will provide my comments:
Thank you for acknowledging the validity of my points. I hear your argument, but it doesn't invalidate mine. Either an accent mark has no bearing on the meaning of a word or it does. I have demonstrated that it is absolutely and undeniably the case that an accent mark can change the meaning of a word in Catalan.
My original assertion is, verbatim: "...the accent can completely change the meaning of a word". You aren't arguing that ma and mà are the same word, despite your assertion that "the presence or lack of accent does not as a rule change the meaning of a word".
I don't address formal grammatical rules, and I am not arguing against your interpretation, it is correct AFAICT. I understand that there are rules for placing accent marks, which is why I asked you to explain the full rule when I was able to easily contradict the grammar rule. That doesn't contradict my argument.
The argument is simply that the placement of an accent changes the meaning of some words in Catalan. There was a side argument that if the last syllable is stressed it must have an accent on the vowel, which you asserted was true "as a rule". That was not true, as evidenced by you having to explain when it doesn't work "as a rule". It can be the case that accent marks have rules for when they are written, and also be the case that different words can have the same letters and differ only in the accent. Both of our arguments are correct.
In this exact case that is what is happening. Catala is a niche programming language named after a french man. Català is a language. The presence of the accent is distinguishing meanings between Catala and Català. I can write the following: "Parlo català, però no se res sobre el llenguage Catala", and the presence or absence of accents will mean the difference between that sentence being gibberish and that sentence meaning something. Likewise, Ma, si, dona, que, etc. can all have an accent added to them to give them a completely different meaning in Catalan. It is unequivocally true, and I don't know why you would assert otherwise.
Thanks for a great discussion.
Well, not in Catalan… (It is "català")