Use a category-letter response grid, then compare only the accepted words within each category. The useful result is a ledger that explains why an answer is accepted, rejected, unresolved, shared, or unique.
Declare one round and three categories
This original classroom packet uses one fixed letter, B, and three categories:
| Category ID | Declared criterion |
|---|---|
| Animal | A common animal name beginning with B |
| Object | A common classroom object name beginning with B |
| Action | A base-form action verb beginning with B |
The teacher reviews the category definitions and acceptable language before distribution. For this fixture, brush means a classroom art brush. No specific object has been observed.
Hasbro's product overview describes category-plus-letter answers and comparison for uniqueness. We use that broad idea with independently authored categories and policy, not its commercial lists, boards, logos, timing, die, or complete rulebook. Hasbro category-letter game overview
Duolingo's teacher resource places this kind of game in vocabulary-practice context. We have read its page, not the linked instructions PDF, and make no claim to reproduce that activity or its results. Duolingo teacher-resource context
There is no pressure timer, random letter, or automatic vocabulary-gain claim in this packet.
Keep actual student rows blank
Give learners a native response grid with one cell per category. Actual names, responses, category explanations, and teacher feedback remain blank until supplied.
Use separate anonymous-looking codes A, B, and C for the following fictional demonstration rows. The codes do not imply collected or anonymized real student records.
| Model row | Animal | Object | Action |
|---|---|---|---|
| A | bear | book | build |
| B | bear | brush | bounce |
| C | bird | desk | bake |
These are prepared teaching examples. Keep them and the teacher key separate from student print content until the review stage.
The worked grid shows a deliberate letter mismatch and a deliberate duplicate. It does not supply a universal answer bank for every class.
Review category and initial letter first
For the prepared key, bear and bird fit the declared animal category and B. book and the stated art-brush sense of brush fit the object category and B. build, bounce, and bake are accepted base-form action verbs for this example.
desk fits the classroom-object category, but starts with D. Report “Category fits; initial letter does not.” That is a letter issue, not a duplicate issue.
Use separate fields for category review, initial-letter check, and teacher acceptance. A computer can compare an initial character under a declared text policy; it should not pretend that a matching B proves semantic category membership.
An unfamiliar or disputed word remains Needs teacher review. Keep its original spelling and explanation. Do not reject it merely because it is absent from the tiny worked key, or accept it merely because its first letter matches.
The teacher's policy should also state how proper names, multiword answers, variants, and ambiguous meanings will be handled. This demonstration contains simple common words; it does not resolve those broader questions automatically.
Normalize only the agreed text differences
For this packet, comparison trims outer whitespace and ignores case. Thus “ bear ” and “BEAR” share the normalized word bear.
Do not automatically stem plurals, merge synonyms, remove punctuation, or reinterpret a proper name. Those changes require a separately declared policy and renewed review.
Keep original response text beside the normalized comparison word. Normalization helps identify repeated strings; it does not establish that an answer is a valid animal or verb.
Use only accepted responses for the category's comparison set. A rejected desk response does not earn credit because nobody else wrote desk. An unresolved response is not automatically promoted to accepted or unique.
Compare within the same category and round
For the prepared, fully reviewed grid:
| Category | Accepted responses | Occurrence result |
|---|---|---|
| Animal | bear, bear, bird | bear occurs twice; bird once |
| Object | book, brush | Each occurs once; desk excluded |
| Action | build, bounce, bake | Each occurs once |
Both bear responses remain valid accepted animal words. They are shared, so they fail an optional uniqueness-credit condition. bird is unique within the Animal category of this one B round.
book and brush are unique accepted Object responses. build, bounce, and bake are unique accepted Action responses.
Do not compare an Object answer against all Animal and Action answers and call that the same-category test. Keep category and round IDs in the comparison key.
If the teacher chooses the original optional credit policy, award one credit to an accepted response that occurs exactly once in its category and round. The prepared grid then has six such response cells: bird, book, brush, build, bounce, and bake. Shared bear cells receive no uniqueness credit, while still being valid.
That tally belongs to the illustrative grid and chosen policy. It is not an observed class score, winner, grade, or a claim to implement the commercial game's full rules.
Hold disputed answers without finalizing their effects
If a response is still awaiting category review, display that uncertainty. Compare the currently accepted responses, but label the category's uniqueness outcome provisional until review is complete.
A later accepted response can create a duplicate. It would be misleading to finalize a credit while a potentially matching response is still unresolved.
When a word, category, letter, or acceptance decision changes, recompute the affected comparison. Keep earlier review records tied to their earlier source/policy revision; do not silently retain a “unique” badge from the previous set.
Human explanation review stays separate from the string comparison. A written justification's presence does not prove its category claim.
Make the review page explain its limits
An optional local reading view can switch between a blank learner packet and the prepared worked key. It can display acceptance states, normalized words, counts, and shared/unique outcomes for the fictional data.
It should not collect actual class responses or perform unrestricted semantic grading. The all-key page is visible to anyone who can open it; keep student distribution separate from the teacher's prepared review.
Reset restores the original demonstration and clears current review feedback. It does not erase native classroom responses or turn pending actual work into accepted answers.
At the actual article width, show category, B criterion, acceptance reason, and uniqueness status together. At 360 pixels, stack the review records with category labels. The companion demonstrates the rendered comparison. Print proof and actual classroom results remain separate checks.
Copy this complete prompt
Create one complete, self-contained US-English HTML companion for “Letter B · category review”. Return the full HTML document, with inline CSS and any JavaScript needed for the local interactions. Use the original scenario, named records, numbers and expected cases below.
Design the page for this task: use clearly labeled input or source records, a readable result or worked example, and an adjacent explanation of the evidence. Use a restrained visual hierarchy, left-aligned text, readable tables or stacked records, and a responsive layout at 720px and 360px. Provide meaningful labeled controls for Prepared teacher review; Blank learner copy; Reset demonstration; Select learner text. Use keyboard-accessible native controls and visible focus. Keep the complete content readable without an external dependency.
The following brief supplies the substantive content and constraints. Native-format requests describe the material to represent or copy manually; this HTML must not pretend to create DOCX, XLSX, PDF, PPTX, H5P or another native file, run Python/Flask/Django/Snowflake/Power BI, connect a live service, send messages, or perform an authorized real-world action. Where the task requires a native source, actual observation or separate approval, retain that requirement and leave unsupplied evidence blank.
Prepare an original fixed-letter category response packet and review ledger for “Classroom Scattergories: Separate a Valid Answer From a Unique One.”
The authoritative artifacts are a native blank student grid, declared teacher category policy, and accepted-response comparison ledger. Do not copy commercial lists/boards/logos/rulebook, introduce a random die/timer, collect student records, or claim measured vocabulary improvement.
Use one B round and three declared categories:
Animal: common animal name. Object: common classroom object name. Action: base-form action verb. Each response must begin with B. In the prepared key, brush means a classroom art brush. Broader proper-name/multiword/variant policies require explicit teacher review.
Actual student names/responses/explanations and teacher feedback remain blank. Separate fictional prepared rows:
A = bear / book / build. B = bear / brush / bounce. C = bird / desk / bake. These are not collected anonymized student records.
Prepared category/letter review:
bear and bird accepted for Animal/B;
book and stated art-brush sense of brush accepted for Object/B;
build, bounce, bake accepted for Action/B.
desk fits Object but fails B. Record category fit and initial-letter fit separately. Do not call desk a duplicate error or award it uniqueness credit.
Maintain round ID, category, original response, letter check, teacher category acceptance, normalized word, occurrence count, shared/unique/unresolved status, reason, and policy/source revision. Unseen/disputed answers remain Needs teacher review; matching B does not establish semantics. Absence from this tiny key does not automatically prove a word wrong.
Normalize ONLY outer whitespace and case for comparisons. “ bear ” and “BEAR” compare as bear. Do not stem, merge synonyms, remove punctuation, or guess proper-name treatment. Preserve original text.
Compare only accepted words within the SAME category and round:
Animal: bear occurs twice, bird once. Object: book and brush occur once each; exclude desk from comparison. Action: build, bounce, bake occur once each. Both bear responses remain valid but shared, not wrong. Reject/unresolved words do not earn credit simply because their text is unique.
Optional original credit policy is one credit per accepted response occurring once in its category/round. The fully reviewed fictional grid has six credited cells: bird, book, brush, build, bounce, bake. It is not a real score, winner, grade, or implementation of the full commercial rules.
If a category has unresolved responses, display accepted-set comparisons as provisional and hold final uniqueness credits for that category until review finishes. Later acceptance can change duplicate counts. Human explanation/category review is separate from mechanical string comparison.
Changes to response/category/letter/acceptance/policy invalidate stale comparison feedback and require affected counts to be reviewed. Preserve prior native review history by revision rather than overwriting actual observations.
An optional local reading view can switch blank learner packet versus worked key and show fictional acceptance/duplicate records. Do not implement classwide response collection, automatic semantic grading, stored results, or secure hidden teacher keys. Reset restores the original fictional set and clears current demonstration feedback; native actual responses remain untouched.
At the actual article width show category+B first, acceptance reason, and valid-shared versus accepted-unique status together. At 360 pixels and the actual narrow article container stack labeled records without page-level horizontal overflow. Any reading controls need keyboard use, focus, selected state, messages, and real local effects.
Before completion, verify desk letter mismatch, both bear responses valid/shared, only accepted same-category counts, six optional credits, case/trim-only normalization, disputed-answer hold, revision invalidation, learner/key print separation, reset, and article/narrow layout. Implementation, print proof, rendered reference comparison, and actual classroom responses remain pending.
Native category-letter grid and teacher-reviewed ledger remain primary. Do not promise live response collection, saved results, semantic grading, or vocabulary mastery.
COMPLETE AUTHORED SCENARIO AND EXPECTED CASES
The following is the supplied reading/teaching/calculation record to represent in the companion. Preserve its particular content, examples, source references and unknowns. Wording about a future native implementation refers to that native task, not permission to omit this HTML companion.
# Classroom Scattergories: Separate a Valid Answer From a Unique One
Two learners write bear for the animal category. Both answers fit the letter B and the category. If the review marks them wrong because they match, it confuses vocabulary acceptance with uniqueness.
Use a category-letter response grid, then compare only the accepted words within each category. The useful result is a ledger that explains why an answer is accepted, rejected, unresolved, shared, or unique.
## Declare one round and three categories
This original classroom packet uses one fixed letter, B, and three categories:
| Category ID | Declared criterion |
| --- | --- |
| Animal | A common animal name beginning with B |
| Object | A common classroom object name beginning with B |
| Action | A base-form action verb beginning with B |
The teacher reviews the category definitions and acceptable language before distribution. For this fixture, brush means a classroom art brush. No specific object has been observed.
Hasbro's product overview describes category-plus-letter answers and comparison for uniqueness. We use that broad idea with independently authored categories and policy, not its commercial lists, boards, logos, timing, die, or complete rulebook. [Hasbro category-letter game overview](https://consumercare.hasbro.com/en-us/product/classic-scattergories-game-party-game-for-adults-and-teens-ages-13-and-up-board-game-for-2-plus-players/A575A605-E267-4F93-B389-3861C0ACAE8C)
Duolingo's teacher resource places this kind of game in vocabulary-practice context. We have read its page, not the linked instructions PDF, and make no claim to reproduce that activity or its results. [Duolingo teacher-resource context](https://duolingoschools.zendesk.com/hc/en-us/articles/6570887180813-Scattergories-game-instructions)
There is no pressure timer, random letter, or automatic vocabulary-gain claim in this packet.
## Keep actual student rows blank
Give learners a native response grid with one cell per category. Actual names, responses, category explanations, and teacher feedback remain blank until supplied.
Use separate anonymous-looking codes A, B, and C for the following fictional demonstration rows. The codes do not imply collected or anonymized real student records.
| Model row | Animal | Object | Action |
| --- | --- | --- | --- |
| A | bear | book | build |
| B | bear | brush | bounce |
| C | bird | desk | bake |
These are prepared teaching examples. Keep them and the teacher key separate from student print content until the review stage.
The worked grid shows a deliberate letter mismatch and a deliberate duplicate. It does not supply a universal answer bank for every class.
## Review category and initial letter first
For the prepared key, bear and bird fit the declared animal category and B. book and the stated art-brush sense of brush fit the object category and B. build, bounce, and bake are accepted base-form action verbs for this example.
desk fits the classroom-object category, but starts with D. Report “Category fits; initial letter does not.” That is a letter issue, not a duplicate issue.
Use separate fields for category review, initial-letter check, and teacher acceptance. A computer can compare an initial character under a declared text policy; it should not pretend that a matching B proves semantic category membership.
An unfamiliar or disputed word remains Needs teacher review. Keep its original spelling and explanation. Do not reject it merely because it is absent from the tiny worked key, or accept it merely because its first letter matches.
The teacher's policy should also state how proper names, multiword answers, variants, and ambiguous meanings will be handled. This demonstration contains simple common words; it does not resolve those broader questions automatically.
## Normalize only the agreed text differences
For this packet, comparison trims outer whitespace and ignores case. Thus “ bear ” and “BEAR” share the normalized word bear.
Do not automatically stem plurals, merge synonyms, remove punctuation, or reinterpret a proper name. Those changes require a separately declared policy and renewed review.
Keep original response text beside the normalized comparison word. Normalization helps identify repeated strings; it does not establish that an answer is a valid animal or verb.
Use only accepted responses for the category's comparison set. A rejected desk response does not earn credit because nobody else wrote desk. An unresolved response is not automatically promoted to accepted or unique.
## Compare within the same category and round
For the prepared, fully reviewed grid:
| Category | Accepted responses | Occurrence result |
| --- | --- | --- |
| Animal | bear, bear, bird | bear occurs twice; bird once |
| Object | book, brush | Each occurs once; desk excluded |
| Action | build, bounce, bake | Each occurs once |
Both bear responses remain valid accepted animal words. They are shared, so they fail an optional uniqueness-credit condition. bird is unique within the Animal category of this one B round.
book and brush are unique accepted Object responses. build, bounce, and bake are unique accepted Action responses.
Do not compare an Object answer against all Animal and Action answers and call that the same-category test. Keep category and round IDs in the comparison key.
If the teacher chooses the original optional credit policy, award one credit to an accepted response that occurs exactly once in its category and round. The prepared grid then has six such response cells: bird, book, brush, build, bounce, and bake. Shared bear cells receive no uniqueness credit, while still being valid.
That tally belongs to the illustrative grid and chosen policy. It is not an observed class score, winner, grade, or a claim to implement the commercial game's full rules.
## Hold disputed answers without finalizing their effects
If a response is still awaiting category review, display that uncertainty. Compare the currently accepted responses, but label the category's uniqueness outcome provisional until review is complete.
A later accepted response can create a duplicate. It would be misleading to finalize a credit while a potentially matching response is still unresolved.
When a word, category, letter, or acceptance decision changes, recompute the affected comparison. Keep earlier review records tied to their earlier source/policy revision; do not silently retain a “unique” badge from the previous set.
Human explanation review stays separate from the string comparison. A written justification's presence does not prove its category claim.
## Make the review page explain its limits
An optional local reading view can switch between a blank learner packet and the prepared worked key. It can display acceptance states, normalized words, counts, and shared/unique outcomes for the fictional data.
It should not collect actual class responses or perform unrestricted semantic grading. The all-key page is visible to anyone who can open it; keep student distribution separate from the teacher's prepared review.
Reset restores the original demonstration and clears current review feedback. It does not erase native classroom responses or turn pending actual work into accepted answers.
At the actual article width, show category, B criterion, acceptance reason, and uniqueness status together. At 360 pixels, stack the review records with category labels. The companion demonstrates the rendered comparison. Print proof and actual classroom results remain separate checks.
Implement the local companion rather than returning a text-only plan. Preserve every numerical fixture and the distinction between illustrative expectations and actual evidence. Any native-runtime or classroom tests mentioned above remain tests to perform in the proper environment; do not mark them passed. Keep edits and practice responses in this open page only, without claiming persistent storage. Provide invalid/missing-input feedback and reset behavior that agree with this specific brief. Do not claim accessibility certification, learning gains, real approvals or test results that were not observed.
Keep the prepared category review with the source
The companion provides an HTML review copy. Include category policy, acceptance reasons, and shared/unique status so a repeated valid answer is not presented as a vocabulary error.