# Measure formalization depth

## Intent

I want to distinguish covered text from executable norms.

## Wrong form and why it stays silent

Adding the text of all articles does not mean expressing their consequences. Removing Accept keeps byte coverage, but filed no longer derives accepted: NEITHER instead of TRUE_ONLY. A separate static mutation below checks the edition address.

```text title="Incorrect form"
fragment Unused in Missing
```

## Correct form

```law
language "law.core" version "0.2";
package recipe.i08 version "1.0.0";
namespace "urn:recipe:i-sources:08";
source Act { kind policy; }
edition E of Act { language ru; officiality unofficial; materialization_status ABSTRACT_ONLY; in_force [@2026-01-01, infinity); }
fragment F in E { kind article; locator "article/1"; text ru unofficial """Статья 1. Заявление принимается."""; }
fragment Unused in E { kind article; locator "article/2"; text ru unofficial """Статья 2. Уведомление обязательно."""; }
entity Person;
relation filed(p: Person);
relation accepted(p: Person);
@source(F)
rule Accept strict { for p: Person; when filed(p); then accepted(p); }
```

## Frozen execution scene

| Variant | Depth |
|---|---|
| F with a rule | EXECUTABLE |
| Unused without nodes | SOURCE_ONLY |
| Accept removed | F becomes SOURCE_ONLY |

Execution: filed → accepted yields TRUE_ONLY; without the whole Accept rule — NEITHER (evaluates.without).

```python
>>> import runpy
>>> checks = runpy.run_path("docs/recipes/i-sources/resources/check.py")
>>> checks["measure"](https://github.com/arxohq/law/blob/master/docs/recipes/i-sources/8)
True
```

## Counterfactual

The `teaches` mutation reproduces `LDC-E5102`. Additional variants are checked by the shown adapter call.

## Boundary

law_measure distinguishes accounting of articles, depth, and the share of bytes. That share is not a percentage of legal correctness.

## Pitfall

Full coverage of two articles is compatible with SOURCE_ONLY of one of them.