Published package / CLIR
doctrine.conflict_of_laws
v0.1.0Коллизионный вопрос: нейтральный словарь применимого права для Рима I, Рима II и практики Суда Европейского союза
A package can be printed as a standalone module in a general-purpose language that answers without the rules engine: an answer and its status, with no proof, hashes or canonical document. Everything on this page comes from the generation plan built with the index; the gallery computes nothing of its own.
Generation plan
The plan builds: the package can be printed as a module.
- plan format
- law-backend-plan/0.9
- capabilities
- aggregate, defeasible, negation, priority
Checked against package scenarios
15 of 15 scenarios matched on ts, py, go
- answer statuses
- FALSE_ONLY 3 · NEITHER 5 · TRUE_ONLY 7
Target languages
gopyts
refuse this plan · 13
bslверсия плана не поддержана эмиттером: 'law-backend-plan/0.9' (поддержана law-backend-plan/0.7)RUcsверсия плана не поддержана эмиттером: 'law-backend-plan/0.9' (поддержана law-backend-plan/0.7)RUdartверсия плана не поддержана эмиттером: 'law-backend-plan/0.9' (поддержана law-backend-plan/0.7)RUerlверсия плана не поддержана эмиттером: 'law-backend-plan/0.9' (поддержана law-backend-plan/0.7)RUexверсия плана не поддержана эмиттером: 'law-backend-plan/0.9' (поддержана law-backend-plan/0.7)RUjavaверсия плана не поддержана эмиттером: 'law-backend-plan/0.9' (поддержана law-backend-plan/0.7)RUktверсия плана не поддержана эмиттером: 'law-backend-plan/0.9' (поддержана law-backend-plan/0.7)RUluaверсия плана не поддержана эмиттером: 'law-backend-plan/0.9' (поддержана law-backend-plan/0.7)RUphpверсия плана не поддержана эмиттером: 'law-backend-plan/0.9' (поддержана law-backend-plan/0.7)RUrbверсия плана не поддержана эмиттером: 'law-backend-plan/0.9' (поддержана law-backend-plan/0.7)RUrsверсия плана не поддержана эмиттером: 'law-backend-plan/0.9' (поддержана law-backend-plan/0.7)RUscalaверсия плана не поддержана эмиттером: 'law-backend-plan/0.9' (поддержана law-backend-plan/0.7)RUswiftверсия плана не поддержана эмиттером: 'law-backend-plan/0.9' (поддержана law-backend-plan/0.7)RU
./law dev backend corpus/clir/doctrine-conflict-of-laws.lawir.json --target ts --target py --target go --out DIR
Module interface
Questions are public relations with a producing rule; inputs are the facts a question reads. Function names follow the language: ask_… in Python, ask.… in TypeScript, Ask… in Go.
Questions · 3
| Name | Parameters | Meaning | Reads | Sources |
|---|---|---|---|---|
| conflicting_characterisations | text | the issue is characterised as contractual and non-contractual at the same time | contractual_issuenon_contractual_issue | section/6 |
| route_complete | text | the route is complete: the applicable law is established and unique | applicable_lawcontractual_issuedistinct_legal_systemsnon_contractual_issue | section/6 |
| route_conflicted | text | the route is conflicted: the interface received two incompatible statements about one issue | applicable_lawcontractual_issuedistinct_legal_systemsnon_contractual_issue | section/6 |
Inputs · 4
| Name | Parameters | Meaning |
|---|---|---|
| applicable_law | text, text | the law applicable to the issue |
| contractual_issue | text | the issue is characterised as concerning a contractual obligation |
| distinct_legal_systems | text, text | the case asserts that these are two different legal systems |
| non_contractual_issue | text | the issue is characterised as concerning a non-contractual obligation |