# Sources: boundaries

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

## Does not do

- **Not prove formalization correctness.** An anchor is tracing:
  it lands in the node's `anchors` and in the proof graph, but does not change
  the conclusion. Checking "norm matches the article" stays human; the machine
  checks only bytes and addresses (`LDC-E5102`/`LDC-E5103`).
- **Not store bytes.** Publication bytes are not part of CLIR:
  moving a package to another store changes not one hash. Anyone waiting for
  the document inside CLIR mistakes the level: the document is in the nearby
  publication, CLIR holds only `uri`, `mediaType`, `documentHash`,
  `retrievedAt`.
- **Not cover the unformalized.** Fragments are opened only for norms:
  `Fragment.texts` enter the semantic hash whole, and a fragment for a
  norm-free chapter moves the package hash by layout edits. Coverage
  (`SOURCE_ONLY` / `ANCHORED` / `SEMANTIC` / `EXECUTABLE`) is computed from
  CLIR, not marked by the author; without a pinned publication text coverage
  is "undefined", not 100%.
- **Not execute `@id` on sources.** An explicit StableId on `source`, `edition`
  and `fragment` is not applied (warning `LDC-E1372`); the package-derived `namespace#Name` holds. On `rule`, `priority`,
  norm templates, `assert` and `calendar` the annotation executes.
- **Not derive pinning status.** `materialization_status` is declared,
  otherwise `LDC-E5207`; without the declaration there is no hash duty
  (`LDC-E5205`).

## Reserved and closed

- The anchor attribute lists are closed: nine `relation`, four `coverage`
  (outside them — `LDC-E1373`).
- The morphological slot dictionary is closed per language family
  (`ru-*`: `genitive`, `dative`, `accusative`, `instrumental`, `prepositional`
  and `_plural`; extras — `LDC-E8203`).
- `kind` on `source` is a jurisdiction-profile symbol, not a core enum;
  `jurisdiction` and `authority` are institute identifiers, not terms:
  no computation is built on them.
- `local_path` is a nonsemantic path inside the package directory:
  absolute or with `..` — `LDC-E5204`.

## Neighbours and the selection rule

- `@source` vs `origin` in `assert`: norm address vs fact provenance.
  See the selection table in `README.md`.
- `fragment` vs whole publication: a sample for norms vs byte
  storage.
- `edition PINNED_*` vs `ABSTRACT_ONLY`: a claim with bytes and hashes
  vs honest unpinnedness. There is no third ("pin later, claim now"):
  that is `LDC-E5205`/`LDC-E5206`/`LDC-E5207`.
- `label` vs fragment `text`: presentation outside `semanticHash` vs
  official text inside the hash whole.