data: 8 candidate questions for the empty Categories 0/4/6/8 (verified: false, verification worksheet attached) - #3
Open
isaac-maya wants to merge 1 commit into
Conversation
…ory-1 heavy-water row (verified: false, verification worksheet; sources re-verified 2026-09-05)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ties to: the open gap in the repo README (README.md): Categories 0/4/6/8 have no items.
What it does: adds 8 new questions for those categories, each with a source I opened and checked, plus a verification worksheet (docs/VERIFICATION_WORKSHEET_CATS048.md) so each row can be signed off one by one. All unverified. Sign-off stays with the maintainer.
Why: the categories are empty, and the questions cover the cases the benchmark is meant to test: two cameras that are identical hardware except frame rate (a trap pair), servers at two ends of the APP range, the post-2021 heavy-water rule change, and a fracking pump inside a Russia-sanctions entry, flagged and explained in the notes. It is an example of a real problem worth discussing, not something to hide.
One row is Category 1, not 0/4/6/8: deuterium oxide sits under 1C298 because the 2021 rule moved non-reactor deuterium out of the old Category-0 nuclear family — the restructuring is exactly why Category 0 is now thin, so the row rides with the backfill and its notes flag the category.
I also built a synthetic underwater camera to test a boundary in the regulations. It is not in the data file, so every shipped row is a real item. Happy to add it as a labeled slice if useful.
One honest note: the validator (scripts/build_dataset.py validate) passed my file, then my own stricter check caught two of my descriptions leaking. Both fixed here. The tooling fix is a separate PR.
Open to keeping or dropping any row after review.