The language products are written in.
Not a catalogue — the grammar. It covers two things at once: every kind of thing a product can be, and everything a storefront registers about it — a price, a stock level, a review. Drawn as a structure, read in plain English.
A adhesive or sealant is a kind of product. It earns its place by answering questions its parent does not: adhesive chemistry, adhesive duty, bond strength class and component system. On top of everything every product answers — like material, brand, and weight.
A review is not a lone value: each one is a bundle that carries its own review rating, review headline and review author. The same precision the kinds get, applied to prices, stock, reviews, and condition.
fig.1 the tree, drawn
The kind-tree is a real structure: every class hangs under the parent whose questions it refines. See the whole tree →
- Product root · every product is one
- powered product +5 questions
- apparel +4 questions
- footwear +7 questions
- computing device +1 question
- container +1 question
- dinnerware +2 questions
index browse the language
Kinds →
The tree of product types — from Product down to specific things — each answering its own set of questions. Drawn, with the parent it refines.
02Properties →
The questions a product can answer, grouped by concern — identity and measurement, but also pricing, availability, condition, and what buyers say.
03Vocabularies →
The words that answer them — materials, colours, brands, units. Closed where physics bounds them, growing where sellers coin them.
04Blueprint →
How the language is built and why — the laws it obeys, and the one rule that decides a kind from a value.
// read live from the pool — every page is server-rendered, structural, and shows the model exactly as it stands. The language is being seeded now; it grows as you watch.