GONZO
JP EN

Proof Layer Policy

Metrics Policy
Use numbers as support,
not as promises.

On the current Gonzo site, public metrics are treated as proof-layer support. They can reinforce comparison, trust, and specialist fit, but they should not replace the product story or imply guarantees beyond the public rule.

Return to FAQ / operating policy Open the compare page
  • Proof Layer
  • Source-Backed
  • Non-Promise
  • Public Guidance

Role

Public metrics support understanding. They do not replace the product story.

01

Comparison Support

Use metrics to reinforce the difference between routes such as Lite, Special, and the specialist branch.

02

Trust Support

Use them as supporting context under the logic and operating design, not as the top-line sales argument.

03

Never The Hero

Numbers do not become the hero promise, the product definition, or a stand-in for risk review.

Source Boundary

Only source-backed reference values from the registered product-description sources should be shown.

Allowed Now

  1. Values already stated in the existing product-description sources
  2. Short framing that keeps them in a proof-layer role
  3. Context that makes the source-backed boundary explicit

Not Allowed

  1. New unsupported performance claims
  2. Guarantee language or certainty framing
  3. Unverified broker or compliance claims
Layer Current rule
Visible values source-backed reference metrics only
Interpretation comparison / trust support only
Hero use not allowed
Expanded claims policy-controlled

Boundary

The policy is also about what we do not say.

WE CAN SAY

  • The numbers are reference values
  • They support comparison and trust
  • They are grounded in existing registered source copy

WE DO NOT SAY

  • Guaranteed outcomes
  • Legal/compliance approval beyond review status
  • Unsupported broker or regulatory claims

Expression Principles

Use the same metrics standard across every public surface.

Always Do

  1. Use only source-backed reference values
  2. Keep them in a proof-layer role
  3. Lead with logic and operating design

Never Do

  1. Turn metrics into outcome guarantees
  2. Add unsupported performance claims
  3. Mix in unverified broker or compliance claims

Next Step

After reading the policy, move back to comparison or detail.

This page fixes the metric-handling frame. Product choice should still happen through selector, compare, and detail routes.