# Name a package and parameters for a reader

## Intention

I want to give the reader names for the package, a relation, and its parameter.

The owner node and the parameter each carry their own label.

## Incorrect form and why it stays silent

A top-level package label cannot be passed off as a working form: `label ru-KZ official "Filing check";` yields LDC-E1321. A relation label must not omit status.

```text title="Incorrect form"
label ru-KZ "Проверка подачи";
```
Otherwise the official name is indistinguishable from a translation.

## Correct form

Relation and parameter labels live in their own bodies. A top-level package label is currently rejected with LDC-E1321; its surface form is deferred.

```law
language "law.core" version "0.2";
package recipes.n.r09 version "0.1.0";
namespace "urn:recipe:n-package:09";

entity Person;
relation filed(p: Person { label ru-KZ official "заявитель"; }) {
    label ru-KZ official "подал заявление";
}
relation received();
assert received();
```

## Frozen execution scene

| Facts | Question | Answer |
|---|---|---|
| received() | received() | TRUE_ONLY |
| Same, relation label removed | received() | TRUE_ONLY |

## Counterfactual

`teaches` removes the required official status and requires a diagnostic. `evaluates.without` removes the relation label entirely: the logical outcome is preserved — a label is not a norm.

## Boundary

Equal outcomes do not prove equal hashes: labels are excluded from the semantic hash, while the content hash includes them. Morphological forms are presentation, not an inference mechanism.

## Pitfall

The remainder of a step and the remainder of the whole division cannot be distinguished by a single relation label. The fix is the parameter's own label; moving it onto the owner is not enough.