mostlyright-data 0.21.0__tar.gz → 0.21.2__tar.gz

{mostlyright_data-0.21.0 → mostlyright_data-0.21.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mostlyright-data
-Version: 0.21.0
+Version: 0.21.2
 Summary: Mostly Right hosted CLI for reviewed datasets
 Project-URL: Homepage, https://mostlyright.md/
 Project-URL: Documentation, https://mostlyright.md/docs/guides/cli/
@@ -135,6 +135,7 @@ worker executables or image publisher.
 - [Aggregate a stream into bars](https://mostlyright.md/docs/recipes/stream-to-bars/)
 - [Use a public dataset](https://mostlyright.md/docs/guides/use-public-datasets/)
 - [Certified document extraction](docs/DOCUMENT-EXTRACTION.md)
+- [Use a table to drive a stream's market roster](docs/TABLE-DRIVEN-DISCOVERY.md)
 
 Use `mr-data --help` for the full command list and options. Commands that support
 `--json` write one JSON object.

{mostlyright_data-0.21.0 → mostlyright_data-0.21.2}/README.md

@@ -123,6 +123,7 @@ worker executables or image publisher.
 - [Aggregate a stream into bars](https://mostlyright.md/docs/recipes/stream-to-bars/)
 - [Use a public dataset](https://mostlyright.md/docs/guides/use-public-datasets/)
 - [Certified document extraction](docs/DOCUMENT-EXTRACTION.md)
+- [Use a table to drive a stream's market roster](docs/TABLE-DRIVEN-DISCOVERY.md)
 
 Use `mr-data --help` for the full command list and options. Commands that support
 `--json` write one JSON object.

{mostlyright_data-0.21.0 → mostlyright_data-0.21.2}/pyproject.toml

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

{mostlyright_data-0.21.0 → mostlyright_data-0.21.2}/skills/mr-data-build/SKILL.md

@@ -586,7 +586,7 @@ dataset from the Kathmandu one the earlier stages follow, chosen because its num
 count.)
 
 ```sh
-mr-data dataset set DATASET_ID --name "Hourly weather at Prague Airport (LKPR), 2000-2026" \
+mr-data dataset set DATASET_ID --name "Prague airport weather history (LKPR), 2000-2026" \
   --category climate-environment --topics "weather,prague,czech republic,metar,iowa environmental mesonet" \
   --license "CC-BY-4.0" --json
 ```
@@ -615,13 +615,26 @@ interpret them.
 | `--topics` | JSON-LD `keywords`, the `Topics:` line answer engines fetch, the `topic` filter in the public API and MCP | 3 to 8 topics, each at most 40 characters |
 
 **Title rules**
-1. Shape: subject, place, period. `Hourly weather at Prague Airport (LKPR), 2000-2026`.
-2. At most 60 characters. Count them.
-3. Use the words a person would type: the common place name, and the official identifier in
-   parentheses once if one exists (ICAO code, station id, ticker, constituency name).
-4. Never: a brand, the word "dataset" or "data", a colon, a pipe, an exclamation mark, a version
-   number, a run date.
-5. Sentence case. No trailing full stop.
+1. Lead with what a person would type to find it: the subject and its place in plain words, in
+   the order a searcher says them. `Denver weather history since 2020`, not `weather history for
+   Denver`. `Kalshi Dogecoin hourly price markets, live order book`. `Kalshi market settlement
+   rules, 2026`.
+2. Never open with a grain word (hourly, daily, 15-minute), a mechanism (order book,
+   observations, reports, METAR), a station code, or a publisher that is not itself the subject.
+   Those come later in the title, or in the opening paragraph. A venue whose own markets, books
+   or rules are what the dataset holds IS the subject and leads: `Kalshi Dogecoin hourly price
+   markets`. A publisher that only relays somebody else's measurements is not the subject and
+   never leads: write `Prague airport weather history`, not `Iowa Environmental Mesonet hourly
+   weather`.
+3. At most 60 characters. Count them. Sentence case, no trailing full stop. The official
+   identifier once, in parentheses, only where people search by it and it fits (ICAO code,
+   station id, ticker, constituency name).
+4. Period last, after the subject and the place: `since 2020`, `2000-2026`, `live`. Where the
+   title ends on the mechanism, the period sits in front of it: `live order book`.
+5. Never: a brand that is not the subject, the word "dataset" or "data", a colon, a pipe, an
+   exclamation mark, a version number, a run date. A run date is the day the build ran; the
+   period the data covers is not one, even where it is the current year.
+6. The place or the subject word is what tells two titles in the set apart, never a code alone.
 
 **Primary category — required before recipe registration**
 Run `mr-data dataset categories --json` to read the fixed vocabulary and its definitions,
@@ -676,8 +689,8 @@ seconds -- not a paragraph, and not a report. Use exactly this shape, in this or
 section out only when there is genuinely nothing to say (shown indented here; the document
 itself carries the headings at column one):
 
-    A plain opening paragraph: what the data contains, what question or model it supports, and
-    the facts a reader needs before using it.
+    A plain opening paragraph: what this is, what it is for, and then the facts a reader needs
+    before using it.
 
     ## Coverage
     - Window: the exact dates and the time zone.
@@ -701,33 +714,52 @@ That is six sections: the opening paragraph, and the five headings under it.
 
 **Opening paragraph** (everything before the first `##` heading)
 
-Write as an engineer explaining a useful table to another engineer. The opening may have more than
-two sentences. Start with the concrete records the dataset contains. Then say which question the
-records help answer or which model they can support. Include geography, time range, row grain,
-update cadence and material limitations when those facts are known. Put a join, transformation or
-source caveat here only when it changes how somebody should use the data.
-
-1. The first two sentences must distinguish this dataset from every other dataset in the set. If
-   both sentences could describe another dataset unchanged, rewrite them.
-2. Use ordinary verbs such as contains, tracks, joins, updates, records and returns. Vary sentence
-   length, and use short sentences for the important facts.
-3. Preserve every established fact. Never invent coverage, freshness, quality, licensing or an
-   intended use.
-4. Write `Mostly Right`, with a space, except inside a literal identifier that uses another form.
-5. Use no Markdown in the opening paragraph. Do not use generic openings such as `This dataset
-   provides`, marketing claims such as `comprehensive`, `powerful` or `high-quality`, or abstract
-   phrases such as `enables insights`, `facilitates analysis` or `serves as a valuable resource`.
-6. Do not explain page design or metadata fields. Do not use em dashes, semicolons, bold labels or
-   fake quotations. Explain the data before implementation details.
-
-After the build establishes each fact, an airport-weather opening can read:
-
-    Hourly weather observations from 20 airport stations across the United States. Each row records
-    one station report with temperature, dew point, wind, visibility, and observation time. Use it
-    to compare observed conditions across stations and time or train a short-term weather model.
-    The table keeps multiple reports within an hour when conditions change, so aggregate it before
-    using one row per station-hour. Mostly Right refreshes the recent window and preserves older
-    observations.
+Its first 155 characters are the snippet a search engine usually prints under the title, its first
+300 the meta description that search engine read to build it, its first 240 the summary an answer
+engine quotes. The order is fixed: what it is, what it is for, then the facts.
+
+1. Sentence one says what this is, in the words a searcher uses, with the place where there is
+   one and the period as a searcher writes it (`since 2020`, `2000-2026`, `live`). Keep it under
+   155 characters, because the snippet cuts there and a sentence that fits is printed whole.
+   `Denver weather history since 2020: every airport report from Denver International (KDEN) with
+   the official daily high and low.`
+2. Sentence two says what it is for: the question it answers or the model it feeds, concretely.
+   `Built for daily temperature forecasting and for checking the weather at any hour.`
+3. Then the facts a reader needs before opening a row: grain, cadence, the material limitation,
+   and the exact window where sentence one could carry only a year. `One row per report, about 30
+   a day, refreshed each morning with the previous day added.`
+4. Never open with the grain, the row, the mechanism, a station code, a publisher that is not
+   itself the subject, a date, or the words "records", "observations", "each row", "rows". Those
+   belong in sentence three. This governs first position only; `records` and `returns` are still
+   good verbs later in the paragraph.
+5. Name the subject the way people search it once (weather history, hourly weather, order book,
+   settlement rules) and the official term once (METAR, SPECI, YES bid), in that order.
+6. Everything that already holds still holds. The first two sentences distinguish this dataset
+   from every other dataset in the set; if both could describe another dataset unchanged, rewrite
+   them. Use ordinary verbs such as contains, tracks, joins, updates, records and returns, and
+   vary sentence length. Preserve every established fact, and never invent coverage, freshness,
+   quality, licensing or an intended use. Write `Mostly Right`, with a space, except inside a
+   literal identifier that uses another form. Use no Markdown. Do not use generic openings such as
+   `This dataset provides`, marketing claims such as `comprehensive`, `powerful` or
+   `high-quality`, or abstract phrases such as `enables insights`, `facilitates analysis` or
+   `serves as a valuable resource`. Do not explain page design or metadata fields, and do not use
+   em dashes, semicolons, bold labels or fake quotations.
+
+After the build establishes each fact, a daily-weather opening can read:
+
+    Denver weather history since 2020: every airport report from Denver International (KDEN) with
+    the official daily high and low. Built for daily temperature forecasting and for checking the
+    weather at any hour. One row per report, about 30 a day, refreshed each morning with the
+    previous day added. A METAR arrives more often than hourly when conditions change, so
+    aggregate before using one row per hour.
+
+And a market opening, on the same three steps:
+
+    Kalshi Dogecoin hourly price markets, live: the order book behind every price-range contract,
+    as traders posted their quotes. Built for studying how traders price hourly moves and for
+    backtesting market making against quotes that really rested. One row per market-second while a
+    YES bid rests, written as each quote lands. Quiet seconds are empty, and recording has run
+    since 10 September 2026, only while a market is open.
 
 **Body rules** (the five sections under the headings)
 1. Every sentence must stay true and complete when quoted alone, away from the page. Never
@@ -746,16 +778,20 @@ code blocks, no links to internal tools, no headings beyond
 the ones above. Spell out the names a reader would search for -- the place, the identifiers in
 every common form, the programme and the publisher -- once each, under Coverage and under
 Source and rights, and never as a keyword list. A one-line description is a defect to fix in the
-revision, not a style choice. Give `table.description` the grain and the window.
+revision, not a style choice. Give `table.description` the same order in one sentence: what
+the table is, then its grain and its window.
 Every statement in the opening and body must preserve an established fact. Never add unsupported
 coverage, freshness, quality, licensing or intended use.
 
 **Check before writing.** Fix and re-check until every line passes:
-- title: at most 60 characters, contains the place, contains no colon, pipe or exclamation mark,
-  no brand, no "dataset" or "data", no version number, no run date
-- opening paragraph: at least two distinct sentences, with the concrete records first and the
-  question or model they support next; include known geography, time range, grain, update cadence
-  and material limitations; no Markdown, banned style or invented fact
+- title: leads with the search phrase, the subject and its place in the order a searcher says
+  them, and does not open with a grain word, a mechanism, a station code or a publisher that is
+  not the subject; at most 60 characters, contains the place where the subject has one, contains
+  no colon, pipe or exclamation mark, no outside brand, no "dataset" or "data", no version
+  number, no run date
+- opening paragraph: sentence one is under 155 characters and says what this is, with the place
+  and the period; sentence two says what it is for; grain, cadence and the material limitation
+  appear only after those two; no Markdown, banned style or invented fact
 - category: exactly one fixed ID saved and verified before recipe registration
 - topics: 3 to 8 descriptive tags, no duplicates, lowercase, at most 40 characters each
 - licence: an SPDX identifier the sources actually grant, or `--license` left off

{mostlyright_data-0.21.0 → mostlyright_data-0.21.2}/src/mostlyright/data_harness/thin/stream_venue.py

@@ -202,6 +202,20 @@ RESOURCE_MEMBERS: tuple[str, ...] = (
     "event_shape_descriptor",
     "bookmark",
     "expected_watermark",
+    "table_discovery",
+)
+
+# Only the public dependency summary is rendered. An API adding transport or snapshot fields
+# beneath this object must not make signed sessions or private source rows appear in CLI output.
+TABLE_DISCOVERY_MEMBERS: tuple[str, ...] = (
+    "table_id",
+    "table_version_id",
+    "resolution_id",
+    "status",
+    "source_completed_at",
+    "freshness_checked_at",
+    "freshness_deadline_at",
+    "last_error_code",
 )
 
 #: The members one registered document is rendered under, spelled the way Studio spells them.
@@ -705,7 +719,18 @@ def resource(record: Mapping[str, Any], *, id_member: str) -> dict[str, Any]:
     rendered: dict[str, Any] = {id_member: record.get(id_member)}
     for member in RESOURCE_MEMBERS:
         if member in record:
-            rendered[member] = record[member]
+            if member == "table_discovery":
+                summary = record[member]
+                if isinstance(summary, Mapping):
+                    selected = {
+                        name: value
+                        for name in TABLE_DISCOVERY_MEMBERS
+                        if isinstance(value := summary.get(name), str) and 0 < len(value) <= 256
+                    }
+                    if "table_id" in selected and "status" in selected:
+                        rendered[member] = selected
+            else:
+                rendered[member] = record[member]
     return rendered
 
 

{mostlyright_data-0.21.0 → mostlyright_data-0.21.2}/src/mostlyright/data_harness/thin/v4.py

@@ -54,16 +54,16 @@ from mostlyright.data_harness.thin.transport import ThinLaneError
 #: WHY A LATER NUMBER IS SAFE TO SEND, AND AGAINST WHICH STUDIO. Studio's ``common.schema.json``
 #: gives command bodies ``request_schema_version`` -- deliberately wider than the ``4.0.0``
 #: envelope constant every V4 RESPONSE still stamps -- and the pinned copy of it admits ``4.0.0``,
-#: ``4.1.0``, ``4.2.0``, ``4.3.0``, ``4.4.0``, ``4.5.0`` and ``4.6.0``. Every command this module
-#: sends binds
+#: ``4.1.0``, ``4.2.0``, ``4.3.0``, ``4.4.0``, ``4.5.0``, ``4.6.0`` and ``4.7.0``. Every command
+#: this module sends binds
 #: that wider definition
 #: (``test_every_command_this_client_stamps_binds_the_wide_request_version``), so a body carrying
 #: this number is accepted by a Studio AT OR AFTER THE PINNED COMMIT.
 #:
 #: ⚠ AND NOT BY ONE BEFORE IT. Studio validates the body against that enum at request time, so
 #: this number is a DEPLOY ORDERING and not just a pin: ``4.2.0`` entered the enum in studio#531,
-#: ``4.3.0`` in studio#533, ``4.4.0`` in studio#552, ``4.5.0`` in studio#644 and ``4.6.0`` in
-#: studio#659, and a release of
+#: ``4.3.0`` in studio#533, ``4.4.0`` in studio#552, ``4.5.0`` in studio#644, ``4.6.0`` in
+#: studio#659 and ``4.7.0`` in Studio's legacy-normalization lane, and a release of
 #: this package that reaches a Studio older than those turns four commands -- ``dataset activity``,
 #: ``table rename``, ``table archive`` and ``dataset archive`` -- into ``422``s that used to be
 #: accepted. That is the whole reason this constant may only be raised in the ``make repin`` commit
@@ -92,6 +92,12 @@ from mostlyright.data_harness.thin.transport import ThinLaneError
 #: repinned against those bytes stamps it on every command it sends, which is why the enum in
 #: ``common.schema.json`` had to admit it and why the deploy ordering above covers it too.
 #:
+#: ⚠ ``4.7.0`` ADDS THE PUBLIC REQUEST/CANCEL SURFACE FOR STUDIO'S SOURCE-FREE LEGACY
+#: NORMALIZER. It is deliberately recorded in ``UNUSED_STUDIO_PATHS``: choosing the two legacy
+#: predecessor coordinates is Studio's recovery flow, and the thin client neither holds nor
+#: lists those reader inputs. The pin still rises because ordinary command bodies stamp the exact
+#: version Studio's common request grammar now declares.
+#:
 #: ⚠ AND THE WORKER SIDE OF THAT DELETION IS A DEPLOY ORDERING OF ITS OWN, in the OPPOSITE
 #: direction from the one above. ``run_execution_v4``'s job parser compares an EXACT field set, and
 #: ``source_collection_protocol``, ``source_collection`` and ``source_collection_inputs`` are no
@@ -99,8 +105,8 @@ from mostlyright.data_harness.thin.transport import ThinLaneError
 #: ``JOB_INVALID`` outright, which in production was every refresh a collection epoch was offered
 #: for rather than only the collection runs. This package must not reach a Studio older than the
 #: commit it pins; ``docs/V4-WORKER-PROTOCOL.md`` states it beside the layout's own ordering rule.
-PINNED_V4_OPENAPI_SOURCE_SHA256 = "b88ef1ea9535232f331bb1337d6a9d0def27e4759fb0a2f46085e481dabc395d"
-PINNED_V4_CONTRACT_VERSION = "4.6.0"
+PINNED_V4_OPENAPI_SOURCE_SHA256 = "2a83dda60e84c166f95ea18af747985bfeeb5887cb48d2c72d4335e83720dc37"
+PINNED_V4_CONTRACT_VERSION = "4.7.0"
 
 # --------------------------------------------------------------------------------------------
 # The routes
@@ -612,7 +618,7 @@ DECLARED_V4_PATHS: frozenset[str] = frozenset(
         # authentication alone -- see `CATALOG_SEARCH_PATH` for why a `workspace_id` would state
         # an isolation the answer does not have -- and the document version it arrived in,
         # `4.5.0`, was the pinned version when this route was promoted (the pin has since
-        # moved on to `4.6.0`). `thin/v4_catalog.py` was
+        # moved on to `4.7.0`). `thin/v4_catalog.py` was
         # written against the frozen cross-repo contract while Studio built its half, for the
         # reason the dataset surface was: a 422 is measured against a shape.
         CATALOG_SEARCH_PATH,