Trust
Trust starts with supportable claims
RedHover publishes only statements whose scope and evidence status are understood. Product vision, implemented capability, accepted runtime, and public permission remain separate categories. Missing customer proof, certifications, or operational receipts are not replaced with logos, ratings, numbers, or general assurances.
Internal evidence paths, private operational details, and unpublished sources never render.
Evidence principles
Every statement retains its evidence status
Public language may simplify a supported fact, but it must not strengthen the scope or maturity.
State the scope and maturity
Target architecture, implemented capability, accepted runtime, and public permission are evaluated separately.
An earlier stage does not prove a later one.
Make missing evidence a visible boundary
Unconfirmed customer, operational, certification, or audit evidence is not hidden behind substitute signals.
WCAG 2.2 AA remains a target until a complete audit supports a stronger statement.
Do not guarantee external outcomes
Search, AI, and publication goals are described as controllable preparation, not promised third-party results.
Indexing, ranking, citation, Launch round-trip, and external-platform behavior are not promised.
Public evidence framework
What makes a statement supportable
Visible content explains the categories; internal sources and private validation details stay outside publication.
Target model
An approved direction is not operation
Product roles and intended connections can be explained as architecture.
They prove no implementation, activation, or accepted runtime.
Implementation
Existing code is not public availability
An implemented capability can be described within its validated development scope.
Local tests or build success prove neither deployment nor customer operation.
Accepted runtime
Operating claims need their own receipts
Live, availability, or customer status becomes public only with matching accepted evidence.
No customer, deployment, availability, or production acceptance is currently claimed.
External validation
Audit and third-party outcomes remain separate
Accessibility, search visibility, AI answers, and Launch compatibility each require their planned validation.
A target, technical preparation, or compatibility plan is not conformance, ranking, or round-trip proof.
Customer logos, ratings, metrics, certificates, partner marks, and general success assurances do not replace matching evidence.
Questions and boundaries
Evaluate public statements clearly
The answers explain what missing or bounded evidence means for this website.
Why does RedHover show no customer logos or outcome figures?
No approved public evidence supports customers, outcomes, and their publication rights. Substitute logos, ratings, and numbers are therefore not invented.
Does a product description mean the capability is live?
No. Product vision, implementation, accepted runtime, and public permission remain separate categories.
Does RedHover claim certification or complete WCAG conformance?
No certification is claimed; WCAG 2.2 AA remains the target until a complete audit supports stronger language.
Are search, AI, or Launch outcomes guaranteed?
No. Technical preparation and planned compatibility validation guarantee neither indexing, ranking, citation, nor a lossless Launch round-trip.