Primary evidence rule
The user's inspection text, uploaded report, and matched evidence outrank generic content ideas. If a feature makes the packet weaker or noisier, it does not belong in the product surface.
LifeVerdict exists to produce a usable negotiation artifact. Editorial and product decisions are judged by whether they improve the packet, not whether they inflate surface area.
The user's inspection text, uploaded report, and matched evidence outrank generic content ideas. If a feature makes the packet weaker or noisier, it does not belong in the product surface.
Affiliate or monetization pressure should not shape the packet. The primary buyer flow stays free during validation, and no commercial relationship should alter lead-item selection, cost scoping, or agent-ready language.
We deliberately prefer narrower asks over inflated full-repair narratives. Cosmetic items, weak preference asks, and broad contractor-list content should not be allowed to dilute the reviewed ask.
Changes to data sources, lender-visible logic, or evidence handling should be documented clearly. Support pages are trust infrastructure for the tool and must stay aligned with the real product thesis.
The product should clearly distinguish between direct evidence, model-derived sizing, and user judgment. It should never imply certainty that it does not have.
Discovery pages can support the product, but they should reinforce inspection negotiation intent. If a page makes the packet harder to understand, trust, or use, it fails the standard.