gold
SELECT T2.expense_description FROM budget AS T1 INNER JOIN expense AS T2 ON T1.budget_id = T2.link_to_budget ORDER BY T1.remaining LIMIT 1
- T1.remaining
- ascending
sha256:d687f7bc4c156b0bc020cf1fb939f8da66f6271209bd35ae1e79355191a14cc8
R-ORD GOLD-ONLY arbitrary-cut not-a-function-of-the-data
student_club · dev_20251106-00000-of-00001 from https://huggingface.co/datasets/birdsql/bird_sql_dev_20251106/resolve/3c11fb193e5439b338e23677fa0aae11e8b85db9/data/dev_20251106-00000-of-00001.json (commit 3c11fb19, downloaded 2026-09-07)
What are the expenses of the budget with the lowest remaining?
the hint the set supplies: expense of budget refers to expense_description; lowest remaining refers to MIN(remaining)
This question was audited without a prediction beside it, so there is nothing to compare the gold with. The probes below read the gold alone.
read by hand, 2026-09-07: wrong the gold does not answer its question on this data
two budgets share the lowest remaining amount and carry different expense descriptions; the question asks for expenses and the gold returns one
a maintainer's reading of this question, out of classification.json, copied from plans/reports/bird-dev-sqlite-260907/classification.json. It is not a verdict and nothing above it was computed from it.
SELECT T2.expense_description FROM budget AS T1 INNER JOIN expense AS T2 ON T1.budget_id = T2.link_to_budget ORDER BY T1.remaining LIMIT 1
sha256:d687f7bc4c156b0bc020cf1fb939f8da66f6271209bd35ae1e79355191a14cc8
from evidence-gold.json, 1 row
| expense_descriptionTEXT |
|---|
| Water, chips, cookies |
A smell is a mechanical reason to read this gold statement again. It is a heuristic: it does not state that the statement is wrong, and a maintainer decides.
this statement orders by a text column holding only numbers, and ordering it as a number gives a different answer, so the gold may be sorting 9.5 above 10
no ORDER BY key resolves to a text column
{
"heuristic": true,
"reason": "no ORDER BY key resolves to a text column",
"keys": [
{
"key": "T1.remaining",
"column": "budget.remaining",
"declared_type": "REAL",
"not_applicable": "the column is not declared as text"
}
]
}
this statement cuts its result at a LIMIT that does not decide which rows come back, so a different but equally correct statement can return other rows and score zero
from smells.json, 2 rows
| Water, chips, cookies | -24.25 |
| Pizza | -24.25 |
{
"heuristic": true,
"cut": 1,
"offset": 0,
"distinct_kept": false,
"unbounded_sql": "SELECT T2.expense_description, T1.remaining AS attestql_ordering_key_0 FROM budget AS T1 INNER JOIN expense AS T2 ON T1.budget_id = T2.link_to_budget ORDER BY T1.remaining",
"unbounded_rows": 32,
"projected_columns": [
"expense_description"
],
"ordering_key_columns": [
"attestql_ordering_key_0"
],
"ordering_keys": [
{
"key": "T1.remaining",
"direction": "asc",
"nulls": "first",
"nulls_first_in_effect": true,
"returned_rows_null_in_this_key": 0,
"fires": false
}
],
"tied_at_the_cut": {
"positions": [
0,
1
],
"tied_rows": 2,
"distinct_projected_answers": 2,
"rows": [
[
{
"type": "str",
"value": "Water, chips, cookies"
}
],
[
{
"type": "str",
"value": "Pizza"
}
]
]
},
"case": "tie-at-the-cut"
}
rerun over the same rows in another physical order this statement gives another answer, so its result depends on how the rows are stored and not only on the data
from smells.json, 1 row
| Pizza |
{
"heuristic": true,
"rule": "R-ORD",
"baseline_result_hash": "sha256:d687f7bc4c156b0bc020cf1fb939f8da66f6271209bd35ae1e79355191a14cc8",
"baseline_result": {
"columns": [
{
"name": "expense_description",
"declared_type": "TEXT"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Water, chips, cookies"
}
]
],
"result_hash": "sha256:d687f7bc4c156b0bc020cf1fb939f8da66f6271209bd35ae1e79355191a14cc8"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"budget",
"expense"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "not_equal",
"differs": true,
"result_hash": "sha256:fc71fbf1592918f648d07d10d9b8dc7a52b0c78837354da7a7b882b947e7f38d",
"result": {
"columns": [
{
"name": "expense_description",
"declared_type": "TEXT"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Pizza"
}
]
],
"result_hash": "sha256:fc71fbf1592918f648d07d10d9b8dc7a52b0c78837354da7a7b882b947e7f38d"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}
SELECT T2.expense_description FROM budget AS T1 INNER JOIN expense AS T2 ON T1.budget_id = T2.link_to_budget ORDER BY T1.remaining LIMIT 1
result_hash sha256:d687f7bc4c156b0bc020cf1fb939f8da66f6271209bd35ae1e79355191a14cc8 recomputed from this JSON: match
record_hash sha256:775ed8961b795c57d16721ce05e36f59fd9b9d1b05428e96761acc394f091871 recomputed from this JSON: match
from evidence-gold.json, 1 row
| expense_descriptionTEXT |
|---|
| Water, chips, cookies |
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/dev/dev_databases/student_club/student_club.sqlite | size=2641920 under the session settings and over the data this record's fixture digest names, and compare the two results under R-ORD