mostlyright-data 0.31.4__tar.gz → 0.31.5__tar.gz

{mostlyright_data-0.31.4 → mostlyright_data-0.31.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mostlyright-data
-Version: 0.31.4
+Version: 0.31.5
 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.31.4 → mostlyright_data-0.31.5}/skills/mr-data-build/SKILL.md

@@ -282,7 +282,10 @@ merely to obtain a green run. Read [recovery details](references/agent-protocol.
 10. For new tables with search intent, inspect search readiness and test meaningful queries against
     the observed version as [search preparation](references/preparing-table-search.md) describes.
     Search preparation runs independently: pending or failed indexing never means the data build
-    failed, and declared metadata alone never proves observed search quality.
+    failed, and declared metadata alone never proves observed search quality. Before delivery,
+    run a battery of at least 40 queries the table's users would type through `search explain`
+    and fix every miss in the recipe
+    ([query battery](references/preparing-table-search.md#run-a-query-battery-before-you-deliver)).
     Report rows and coverage actually verified, checks, limitations and the stable dataset link.
     End with what would make the table better: the remaining enhancements, deterministic ones
     first, each naming the column it reads and what it would add, and the model that would do it.

{mostlyright_data-0.31.4 → mostlyright_data-0.31.5}/skills/mr-data-build/references/preparing-table-search.md

@@ -327,9 +327,45 @@ can lag a new live version by a few minutes. Retry then. A query holds at most 1
 means the package did not answer and the fallback scan did. The `note` says why. Fix that before
 you judge ranking. `try` runs on published tables only, against their live version.
 
-Check each kind of query the table should answer: an exact title, a misspelled title, a person, a
-brand, a category word, a decade, a sort word, and a plot paraphrase. Record a few checks with
-their actual results in the dataset's verification notes.
+### Run a query battery before you deliver
+
+A few spot checks miss most gaps. Before you deliver a table with search, write a battery of at
+least 40 queries that the people who use the table would type, and run every one through
+`search explain`. Take the queries from the brief and the product, not from the column names.
+Cover each kind:
+
+| Kind | Examples |
+|---|---|
+| A name, title or ticker | "nvidia", "tesla stock", "dune" |
+| A kind of row, singular and plural | "etfs", "validators", "token" |
+| A category or theme word | "ai companies", "chip stocks", "horror" |
+| A threshold with a unit | "revenue growth over 50", "pe under 15", "apy above 7%" |
+| A superlative on each sortable measure | "most dividends", "lowest commission" |
+| A superlative with a time window | "best performers last 30 days", "biggest gainers today" |
+| The product's own slang | "hottest stocks", "trending", "blue chips", "meme coins" |
+| A sort by a named column | "top validators by stake", "cheapest by pe" |
+| Two conditions together | "dividend yield over 3 and pe under 15" |
+| A paraphrase of a description | "companies that make chips" |
+
+Write down the plan each query should get: the filters, the order and the words left to search.
+Then compare what `search explain` answers. A query passes when its plan holds the filter and the
+order you wrote and searches no leftover word that only ranks or joins the query, such as "top",
+"with" or "today". Judge the plan, not the rows: a wrong plan can still return rows.
+
+Fix each miss in the recipe, then run the whole battery again:
+
+- A word the table has no meaning for ("hottest", "trending"): give it a sort alias or an alias
+  on the column the brief means, and say the word in that column's description.
+- A generic word an alias binds to one column ("best", "top", "biggest") that captures a more
+  specific query ("best performers", "biggest losers today"): replace it with specific phrases
+  such as "top stocks" and "biggest companies".
+- A window no column holds ("last 20 days"): add a column for it, or state in the brief that the
+  table answers only the windows it carries.
+- A phrase the 128 alias or 64 sort alias cap pushed out: rank the vocabulary so the phrases users
+  type most come first, and drop a phrase another alias already covers word for word.
+
+Keep the battery with the recipe and rerun it after every rebuild. Record the pass count and each
+known miss in the dataset's verification notes.
 
 ## 12. Write evaluation cases