Skip to content
docs
Arxo ↗

Interpretation boundaries

For LLMs3 sections

What the construct does NOT do in 0.2: scope, reserved values, neighbouring constructs, and the selection rule.

  • Not select by status. status (proposed … binding … rejected) never activates a reading by itself: the selection policy is set by the jurisdiction profile. A status without a group is a description, not a fork.
  • Not mix results. Analysis mode counts each alternative separately (results_by_interpretation): results never mix. The language gives no “average” of two readings.
  • Not resolve evaluative features. A dispute over a norm’s meaning is a reading; “plainly excessive”, intent, a disputed reading of a fact go to their channels (judgment, a court fact, a reading): an evaluative element goes to its channel, not by default into a reading fork.
  • Not extinguish the independent. An unresolved group never touches queries outside the dependence closure: truth, collect, and positions get COMPUTED when the reading choice does not affect the answer. For weak_permission and calendar operations no dependence is defined at all.
  • Not repair conflicting editions. The language allows holding KkReading of ART_KK and RuReading of ART_RU side by side and requires a divergence report — the machine never merges texts or picks the “right” language.
  • Three group policies: exactly_one, any_of, compose_explicitly. No fourth; no default without selection — the policy is declared explicitly.
  • Eight statuses: proposed, reviewed, official, binding, persuasive, disputed, rejected, superseded.
  • extends is set composition, not mutation: exclude must be explicit and visible in provenance; the reference may be qualified (extends pkg::Baseline).
  • Nested members are declarations, not text: rule, definition, presumption, fiction, classification, priority (the grammar’s exhaustive list, not “anything goes”).
  • A reading vs priority: different readings of one norm vs a clash of two operative norms.
  • A reading vs the judgment channel: theory vs fact.
  • A group vs a status: decides vs describes.
  • include vs extends: a ready rule taking part in one’s own reading vs composition with another’s reading.
  • See the selection table in README.md.

Documentation for Arxo. Writings — blog.arxo.io.

Anonymous visit counts on stats.arxo.io, no cookies.