Tools
Tools
2 of them. Both run on the catalog rather than on a rule of thumb, both print the rules they follow, and both turn off any input that cannot change their answer, with the reason written out on the page.
Claim Lookup
Two inputs: the word, and where to look.
Pick one of the 8 claim words and a part of the catalog. It returns the status of the word, the thing it does not promise, how many listings in that scope use it and which, and where to look instead.
The 4 rules it runs on
- The word list is the eight claim words this site tracks. The category list is the six catalog categories, plus all six together.
- A listing counts as using a word when the word, or a direct variant of it, appears in the listing text or the product name. Nothing is inferred from the photographs and nothing is inferred from the category.
- The count shown is the number of listings inside the chosen scope that use the chosen word. It is computed from the catalog, never typed in.
- The status is a property of the word, not of the scope, so changing the category never changes it.
Closure Finder
Three inputs, each a yes or a no.
Three questions about how a shoe has to behave, answered against what the 66 listings actually state about closure. It returns kinds of closure, the listings that name them, and what each kind does not give you.
The 5 rules it runs on
- Hands free when putting it on = yes keeps only the kinds a listing describes as going on without hands: slip-on or slip-in, and elastic laces.
- Adjustment needed = yes keeps only the kinds that move and stay where they are put: laces, buckles and adjustable straps. Elastic stretches and returns, so it is not counted here.
- Wet surface = yes keeps only the kinds that at least one listing in this catalog pairs with a water word. That is the whole of the wet-use language the catalog contains, and it is a fact about vocabulary rather than about grip.
- Answering no to a question applies no filter at all. Three answers of no return every closure kind in the catalog.
- The three filters intersect. Some combinations return nothing, and where that happens the result says so rather than relaxing a rule.
Why an input sometimes goes gray
Both tools check, on every selection, whether an input could change the answer at all. If no other value of that input would alter a single field of the result, the control is disabled and the reason is printed beside it. That is a stronger test than asking whether an input matters somewhere: an input can matter in one selection and be entirely inert in the next, and it is the next one you are looking at.