Four effective states
- Internal only: absent from every public output and client payload.
- Catalog only: useful inline record and supported comparison fields, but no standalone URL.
- Public noindex: a standalone reference route excluded from sitemap and carrying
noindex,follow. - Public index: requires catalog, route, and automated index entitlement plus a matching explicit owner fingerprint approval.
Capabilities belong to fields
A product can remain useful while a particular value is pending, absent, ambiguous, conflicting, noncanonical, stale, or not standards-attributed. Display, filter, compare, chart, and current-market capabilities are evaluated separately.
Market comparisons answer buying questions
Product pages lead with the reported value and a plain-language comparison with “Typical.” An open-on-tap explanation defines Typical as the middle value, states the data rule, and lists every current pad included. Each comparison names its product count and appears only when at least five pads can be compared.
Paired facts use intersection
A chart point or deterministic difference exists only when every constituent supports that operation and their variant scopes are compatible. Pairing a valid field with an invalid one cannot make the invalid field canonical.
Owner feedback stays separate
The pilot records only a rating aggregate, review count, exact-model scope, source, and observation date from a brand-owned product page. It cannot affect field capabilities, sorting, filtering, market comparisons, recommendations, or publication.
Build-time aging
Current price functions use a 30-calendar-day evidence window and the actual UTC build clock. Static production artifacts must be regenerated at least every 14 days so stale values can age out.