Markdown for LLMs

Judgment channel: forms from the corpus

The source Markdown for this article. Copy it into your assistant or download it as a text file.

# Judgment channel: forms from the corpus

Analysis of real fragments: package identifier, act name, the key fragment, form verdict
(exemplary / disputed / wrong form choice) and why.

## Law

### 1. Turkish Constitution — four art. 13 judges (exemplary, inspected)

Package `tr.constitution` — Turkish Constitution (Türkiye), art. 13:

```law
// текста здесь нет — текст ясен, неизвестен РЕЗУЛЬТАТ применения критерия к
// конкретной мере. ... Пока суждение не предъявлено, ограничение остаётся
// в REQUIRES_JUDGMENT ...
external judgment relation restriction_preserves_essence_of_right(restriction: Restriction, right: FundamentalRight) {
    authority Court;
    label tr official "Madde 13. ...";
    label ru unofficial "Статья 13. Ограничение не посягает на сущность основного права";
}
```

Then three more relations (`..._letter_and_spirit`,
`..._democratic_and_secular_order`, `..._proportionality`, lines 219–235).
Exemplary twice: the right channel chosen (the comment records the
"judgment vs reading" fork) and the organ named that decides under
the Constitution (art. 148). Labels in two languages — the channel presented to
the lawyer twice.

### 2. EU Regulation 261/2004 — extraordinary circumstances (exemplary, inspected)

Package `eu.transport.air_passenger_rights` — EU air passenger rights rules (European Union):

```law
@source(EU261_ART_5_P3)
pub external judgment relation extraordinary_circumstances(f: Flight) {
    label en official "the cancellation was caused by extraordinary circumstances ...";
    authority Court;
}
```

Exemplary: one open question for the whole norm; the
`carrier_exempt_from_compensation` head with no producer in the package — on purpose
(the file's comment): until CJEU practice decomposes the question, the organ has
nothing to read but the judgment. The same comment records the boundary: when the case
world carries a practice package, the question is written there — the channel narrows with facts,
never cancels.

### 3. RK Criminal Code — an answer on another's channel (exemplary, inspected)

Package `kz.corpus.criminal_code` — Kazakh Criminal Code (Kazakhstan), art. 102 scenario:

```law
// Ст. 102 УК: своего канала статья не заводит — превышение пределов
// необходимой обороны оценивает суд по ст. 32 п. 3 (DECISION-0194, остаток
// пилота). Делом подано последствие защиты, ответ суда пришёл по каналу
// ст. 32 — состав ст. 102 образован.
assert "j0": necessary_defense_limits_exceeded(...) { origin adjudicated; }
...
expect truth_status == TRUE_ONLY;
expect evaluation_status == COMPUTED;
expect judgment_requests(0);
```

Exemplary: the channel is opened by the article whose organ decides; the consumer (art. 102)
reads the answer instead of duplicating the relation. The `judgment_requests(0)`
expectation records closedness — a sample for this directory's tests.

## Custom

### 4. The "Ochered" queue — a collective organ with a disputed reading nearby (exemplary, inspected)

Package `usus.corpus.ochered` — "Ochered" queue custom (customary practice):

```law
external judgment relation absence_adjudged_excessive(q: Queue, p: Person) {
    authority TheQueue;
    label ru-KZ unofficial "сама очередь коллективно признала данную отлучку чрезмерной (ст. 6)";
}
```

Exemplary: the organ is not a court (`authority TheQueue` — an
institution identifier, checked by equality). In the same file nearby —
`interpretation RollCallReading` / `JudgmentReading` with
`disputed` status: the same indeterminacy ("what counts as an excessive absence")
decomposed at once along two channels — the presumption holds the place,
the readings argue the criterion, the judgment closes the case. Three channels in
one file without mixing.

## Science and standards

### 5. CJEU practice as a narrowing package (form boundary, data of the file above)

The comment in the cancellation rule above describes a form absent from this
package: an external practice package
writes into the same relation, and the text's undecomposed question stops being
a question. Verdict: the channel/fact boundary moves — judgment
is needed while there is no knowledge; knowledge arrives and the channel stays declared but
no more queries come (cf. `judgment_requests(0)` in item 3). A form in which
a judgment relation would be deleted as unneeded would be a mistake:
practice leaves and the question returns.

## Corpus measurement 05.09.2026

Corpus-wide count over 508 packages:

| Form | Occurrences | Packages |
|---|---|---|
| `external judgment relation … { authority …; label …; }` | 366 | 140 |

The remaining rows of that measurement (vocabulary, constants, keys,
imports) belong on the [vocabulary](/constructs/vocabulary/) page and are not repeated here.