properties /identity

WHAT JOB THE PRODUCT IS SOLD TO DO - bonding, threadlocking, thread sealing, gasketing, retaining, leak sealing, potting. THIS IS THE FOLD, and it is the answer to the queue's central question for H5. The trade sells a threadlocker, a gasket maker, a windscreen sealant, an epoxy, an exhaust paste and a radiator stop-leak as six different goods; the pool files them as ONE KIND answering this property. That is the 2026-08-25 amendment biting for the FIFTH proposal running, after b153 lost FuelFilter, b154 lost five named fluid trades, b155 lost the whole trade vocabulary of plug types and b156 lost the pad and the shoe. THE QUEUE ASKED SPECIFICALLY whether a sealant differs from an adhesive by function enough to be a sibling class, and the answer is no, on the makers' own published evidence: Henkel prints exactly this distinction in a field it calls `Application`, filling it with `Bonding` on one sheet and `Sealing` on the next, from one product family, in one house, in one format - which is a property with two values, not two classes. LOCTITE AA 3491 settles the cardinality by itself: Henkel publishes its Application as `Bonding, Potting or Sealing`, three duties on one product, so this is cardinality MANY, exactly as `fluid_duty` had to be when TotalEnergies published Rubia SX 40 for engines, gearboxes and hydraulic circuits. A duty is not a fitment [REFINE-LOG 2026-08-25]: it names a job and no vehicle, which is `filtration_duty`'s and `fluid_duty`'s reasoning verbatim. Required, because it is the fact the shelf sorts on and nothing else in the grammar carries it. Concern identity - a threadlocker and a wood glue are two listings, never two cells of one buy box.