## Reference images

Study these alongside the description below: hierarchy, rhythm, spacing, colour. Build for the product you are asked about, using this design language.

- Component: https://kage-design-assets.t3.tigrisfiles.io/components/relic/11197dbe-e39c-44cc-b0a1-5cdca0c05213-1789279382-7.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/relic/11197dbe-e39c-44cc-b0a1-5cdca0c05213-1789279305759-full.webp
- Component on Kage: https://kage.design/component/relic-testimonials

## Before you start
Ask what evidence supports the user's product, whether it is open source or independently verifiable, and what proof readers need before converting. Use only substantiated proof.

Design a credibility section with a two-column intro: a strong headline on the left and a short proof-oriented paragraph plus dark pill CTA on the right. Under it, place four equal white cards with a compact promise, a small metadata label, and a short explanation. Use `#f5efe3` background, white cards `#fffdf8`, `#171714` text, muted `#6c665c`, and a black CTA `#111210`; use 16–20px radii, 20px gaps, subtle borders, and a calm editorial rhythm. Ensure the CTA has a clear external-link or repository affordance when appropriate, but do not imply endorsements that do not exist.

Never use logos, product names, copy, illustrations, or imagery from the reference.