How to Read Explainable Results

Match score vs confidence

Match score ranks in-stack tools on your answers — higher means stronger alignment with stated constraints or beliefs.

Confidence reflects answer completeness — sparse Quick mode answers produce lower confidence and wider gaps between picks.

Low confidence is not failure — it means retake in Deep mode or add open-text context rather than guessing.

Never treat match score as guarantee of success — especially for prop challenges or investment outcomes.

Why-recommend bullets

Each bullet ties to a rule or belief weight — e.g., news trading allowed, US-regulated exchange, or data ownership priority.

Read all bullets — one strong fit on your top priority may outweigh minor misses elsewhere.

Featured #1 match shows why-not for runners-up when enabled — near-misses are explainable, not hidden.

Possible concerns

Concerns are honest negatives — higher fees, stricter rules, or missing features relative to your profile.

A tool can rank #1 with concerns — it means best fit, not perfect fit.

If concerns collide with a hard requirement you forgot to enter, retake and mark that constraint explicitly.

Acting on results

Use /out/ affiliate links for disclosure tracking — they never changed ranking order.

Open compare page when #1 and #2 scores are close — difference is often one hard constraint.

Save your /match/[id] link to revisit — snapshots contain match data only, no account info.

Verify live pricing and rules on official vendor sites before purchase.

Retake guidance

Retake when priorities shift — new monetization model, region move, or strategy change.

Deep mode adds secondary beliefs and open-text keyword matching — use when Quick mode feels generic.

Editorial-standards documents engine types: constraint (prop), belief (newsletter/website), use-case (crypto).