Published package / CLIR
logic.core
v0.1.0Общий словарь логических понятий: система, язык, исчисление, правило, метод, шаг, условие, обоснование
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, status:monotone
Checked against package scenarios
Not checked: the package scenarios have not been run against generated modules. A plan that builds does not yet show that the answers coincide.
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/logic-core.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 · 33
| Name | Parameters | Meaning | Reads | Sources |
|---|---|---|---|---|
| accepts_principle | text, text | the system accepts the principle | attitude_to_principle | section/10 |
| agrees_here | text, text, text | the two systems agree on the principle: both accept it | attitude_to_principle | section/1 |
| answer_condition | text, text, text, text | answer to under-what-conditions: the condition with its wording | requires_conditionterm_name | section/13 |
| answer_difference | text, text, text, text | answer to how-do-they-differ: the named principle and how the difference is established | attitude_to_principlediffers_by_principle | section/1 |
| answer_grade | text, text, enum | what the piece of knowledge is: definition, source claim, or engine computation | knowledge_grade | section/19 |
| answer_language | text, text | in which formal language the system or calculus works | calculus_languagesystem_language | section/2 |
| answer_limit | text, text, text | limit of the method: part of the how-to answer, not a footnote to it | method_limit | section/12 |
| answer_method_system | text, text | for which system the method is described | method_in_system | section/12 |
| answer_part | text, dec, text, text | answer to what-are-the-parts: the numbered part and the kind of link | contains_stephas_conclusionhas_premiseschema_child | section/12section/7section/4 |
| answer_result_form | text, text | expected result form of the method | method_result_form | section/12 |
| answer_source | text, text, text | answer to which-source: the fragment locator and the item through which it was reached | contains_stepdefined_viadischarges_assumptionhas_conclusionhas_premisemethod_goalrepresents_systemrequires_conditionrule_of_calculusschema_childschema_slot_refstated_bystep_dischargesstep_needs_principlestep_opens_contextstep_uses_conceptstep_uses_ruleuses | section/15section/18 |
| answer_step | text, dec, text, text, text | answer to how-to-apply: the numbered step together with its readable wording | contains_stepterm_name | section/12 |
| answer_step_dependency | text, text, text | dependency between steps of one method | contains_stepstep_depends_on | section/12 |
| answer_use_ground | text, text | which earlier application the presented application relies on | use_ground | section/9 |
| answer_used_in | text, text, enum | answer to where-used: the calculi the rule belongs to, and in which status | rule_of_calculus | section/11 |
| answer_what_is | text, text, text, text | answer to what-is: name and gloss in one language | glossterm_name | section/17 |
| attitude_unrecorded | text, text | the present description has not settled the attitude, and says so | attitude_to_principle | section/10 |
| differs_here | text, text, text | the two systems differ on the principle: one accepts it, the other rejects it | attitude_to_principle | section/1 |
| explains | text, text | one unfolding step: by what the item is explained | contains_stepdefined_viadischarges_assumptionhas_conclusionhas_premisemethod_goalrepresents_systemrequires_conditionrule_of_calculusschema_childschema_slot_refstep_dischargesstep_needs_principlestep_opens_contextstep_uses_conceptstep_uses_ruleuses | section/18 |
| foreign_variable | text, text | the schematic variable does not belong to the named owner | item_keyslot_scope | section/5 |
| grounded_in_source | text | the explanation of the item reaches a pinned source fragment | contains_stepdefined_viadischarges_assumptionhas_conclusionhas_premisemethod_goalrepresents_systemrequires_conditionrule_of_calculusschema_childschema_slot_refstated_bystep_dischargesstep_needs_principlestep_opens_contextstep_uses_conceptstep_uses_ruleuses | section/18 |
| has_provenance | text | the item carries at least one pinned source locator | stated_by | section/18 |
| instruction_available | text | the rule has a displayable instruction: at least one premise and a conclusion | has_conclusionhas_premise | section/8 |
| own_variable | text, text | the schematic variable belongs to the named owner | slot_scope | section/5 |
| reach_count | text, dec | how many items the unfolding reaches | contains_stepdefined_viadischarges_assumptionhas_conclusionhas_premiseitem_keymethod_goalrepresents_systemrequires_conditionrule_of_calculusschema_childschema_slot_refstep_dischargesstep_needs_principlestep_opens_contextstep_uses_conceptstep_uses_ruleuses | section/18 |
| reaches | text, text | reachable by unfolding: transitive closure of the explanation step | contains_stepdefined_viadischarges_assumptionhas_conclusionhas_premisemethod_goalrepresents_systemrequires_conditionrule_of_calculusschema_childschema_slot_refstep_dischargesstep_needs_principlestep_opens_contextstep_uses_conceptstep_uses_ruleuses | section/18 |
| rejects_principle | text, text | the system rejects the principle | attitude_to_principle | section/10 |
| rule_applied_in | text, text | the rule is actually applied in the presented reasoning | presented_stepuse_of_rule | section/16 |
| schema_arity | text, dec | number of immediate constituents of the schema | schema_childschema_shape | section/4 |
| schema_variable | text, text | the schematic variable occurs in the schema | schema_childschema_slot_ref | section/5 |
| shown_conclusion | text, text | a conclusion actually presented by the reasoning; describing a rule yields none | presented_stepuse_conclusion | section/16 |
| source_claim | text, text | claim attributed to a source with the given locator | knowledge_gradestated_by | section/19 |
| step_ground | text, text | ground of the step, of any of the three kinds | step_needs_principlestep_uses_conceptstep_uses_rule | section/15 |
Inputs · 36
| Name | Parameters | Meaning |
|---|---|---|
| attitude_to_principle | text, text, enum | attitude of the system to the principle: accepted, rejected or not settled here |
| calculus_language | text, text | the calculus works in this formal language |
| contains_step | text, dec, text | the method contains a step at the given position |
| defined_via | text, text | the item is defined through another item |
| differs_by_principle | text, text, text | the two systems differ in their attitude to the named principle |
| discharges_assumption | text, text | the rule discharges an assumption of the given form |
| gloss | text, text, text | short gloss of the item in the given language |
| has_conclusion | text, text | the conclusion of the rule is a schema |
| has_premise | text, dec, text | the rule has a premise at the given position, and the premise is a schema |
| item_key | text, text | stable machine key of the item |
| knowledge_grade | text, text, enum | provenance grade of a piece of knowledge about the item |
| method_goal | text, text | goal of the method: the form of statement it teaches to justify or use |
| method_in_system | text, text | the method is described for this logical system |
| method_limit | text, text, text | limit of the method: what it does not deliver |
| method_result_form | text, text | expected form of the result of the method |
| presented_step | text, dec, text | a presented step of the reasoning: case data, not package content |
| represents_system | text, text | the calculus represents the logical system |
| requires_condition | text, text | the item requires an applicability condition |
| rule_of_calculus | text, text, enum | the rule belongs to the calculus as basic, derived or admissible |
| schema_child | text, dec, text | immediate constituent of the schema at the given position |
| schema_shape | text, text | shape of the schema node |
| schema_slot_ref | text, text | the slot node of the schema is occupied by the named schematic variable |
| slot_scope | text, text | scope of the schematic variable: the rule, principle or method declaring it |
| stated_by | text, text | locator of the pinned source fragment stating the item |
| step_depends_on | text, text | the step depends on the result of another step |
| step_discharges | text, text | the step discharges a previously introduced assumption of the given form |
| step_needs_principle | text, text | the step requires the system to accept the named principle |
| step_opens_context | text, text | the step opens a subderivation with an assumption of the given form |
| step_uses_concept | text, text | the step is justified by unpacking the definition of a concept |
| step_uses_rule | text, text | the step is justified by a rule of a calculus |
| system_language | text, text | the system is considered in this formal language |
| term_name | text, text, text | readable name of the item in the given language |
| use_conclusion | text, text | which conclusion the presented application states |
| use_ground | text, text | which earlier application this one relies on |
| use_of_rule | text, text | which rule the presented application names |
| uses | text, text | the item uses another item without being defined through it |