mostlyright-data 0.29.5__tar.gz → 0.29.6__tar.gz

{mostlyright_data-0.29.5 → mostlyright_data-0.29.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mostlyright-data
-Version: 0.29.5
+Version: 0.29.6
 Summary: Mostly Right hosted CLI for reviewed datasets
 Project-URL: Homepage, https://mostlyright.md/
 Project-URL: Documentation, https://mostlyright.md/docs/guides/cli/

{mostlyright_data-0.29.5 → mostlyright_data-0.29.6}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mostlyright-data"
-version = "0.29.5"
+version = "0.29.6"
 description = "Mostly Right hosted CLI for reviewed datasets"
 readme = "README.md"
 requires-python = ">=3.11"

{mostlyright_data-0.29.5 → mostlyright_data-0.29.6}/skills/mr-data-build/references/5-draft-one-recipe-document-one-call.md

@@ -455,11 +455,12 @@ from the accepted subset — `Cel`, `ug/m3`, `km/h`, `hPa`, `{count}` and the re
 out in [Units](https://mostlyright.md/docs/reference/units/). Write the code rather than a name:
 `ug/m3` composes and `microgram_per_cubic_meter` does not.
 
-**Nothing resolves the code, so there is no `UNIT_*` refusal to lean on.** The recipe schema bounds
-the length of `unit` and nothing else; registration checks only that `units[].column` names a
-declared column and answers `422 RECIPE_DOCUMENT_INCOHERENT` at `/units/N/column` when it does not;
-the run never reads `units` at all. A code outside the subset therefore costs nothing at build time
-and costs every reader afterwards, and a column declared in metres that holds feet is caught by
+**Registration resolves the code and reads no data.** The recipe schema bounds the length of
+`unit`; registration then checks that `units[].column` names a declared column, answering
+`422 RECIPE_DOCUMENT_INCOHERENT` at `/units/N/column` when it does not, and resolves each
+`units[].unit` against the subset, answering the same code at `/units/N/unit` when it cannot.
+`mr-data recipe` does not resolve the code locally, so that refusal arrives from registration. The
+run does not read `units`, so a column declared in metres that holds feet is caught by
 nothing. Convert in the statement, then declare the unit of what the column ends up holding. Leave a
 column out of `units` rather than declare something approximate — a density, a rate, anything whose
 unit is genuinely new. `none` is not a unit and does not become one. Remember that the two

{mostlyright_data-0.29.5 → mostlyright_data-0.29.6}/skills/mr-data-build/references/making-a-table-incremental.md

@@ -105,8 +105,9 @@ Studio records the answer as one classification per source:
 | a `window` carrying a `request` | `window` | `acquire_incremental` |
 | none of those | `resync_only` | `resync_required` |
 
-The rows are in Studio's precedence order, and the first match wins. A source that states both
-`closed: true` and a request window is `closed`, and its window is never read. One `resync_only`
+The rows are in Studio's precedence order, and the first match wins. A source may not state both
+`closed: true` and a request window: registration refuses that pair with
+`422 RECIPE_DOCUMENT_INCOHERENT` at `/sources/N/closed`. One `resync_only`
 source makes the whole table resync-only, however truthful its siblings are. Say which sources you
 left `resync_only` and why, because a recipe that never asked the question registers the same way
 as one that did.