Invisible-finish SPF concept
Example match: deeper skin tones + no-fragrance preference
- Evidence
- Testing protocol placeholder
- Commerce
- No product · no affiliate link
- Selected budget
- All concept budgets
No displayed listing, review, partner, offer, price, availability, or outcome should be treated as real.
How facts and examples are separated ↗Look / Decision engine
Product Finder
Filter products by concern, finish, formula, shade or texture compatibility, budget, ownership, and evidence.
All product names and results are examples. There are no live affiliate links, tests, reviews, prices, or rankings.
Recommendation-engine interaction
Filter the decision record.
Razor-bump routine concept
Example match: sensitive skin + electric shave
- Evidence
- Ingredient/source fields required
- Commerce
- No product · no sponsor
- Selected budget
- All concept budgets
Moisture routine concept
Example match: dry hair + low-manipulation goal
- Evidence
- Panel and expert fields required
- Commerce
- No price · no review
- Selected budget
- All concept budgets
01
Recommendation record
Why this—not just what
A production recommendation will expose the matching logic and disclose what evidence is missing.
- Match reasons
- Testing protocol
- Expert and community evidence
- Affiliate and sponsor status
02
Commerce firewall
Payment cannot improve the score
Sponsored visibility, affiliate availability, editorial recommendation, and product rating remain separate fields.
- Sponsored label
- Affiliate disclosure
- Editorial criteria
- Correction history
Authenticity contract
Structure can be complete before claims are real.
Where genuine evidence exists, the site publishes it with source, vintage, identifier, and limitation. Where a marketplace, review, recommendation, partnership, price, benefit, event, or score lacks real-world support, the interface remains a clearly labeled example.
Audit genuine datasets ↗Read the commercial firewall ↗