SSolarc Labs
All free tools

Evidence standard · Truth before GEO theatre

Free tool evidence methodology

Solarc separates inspectability from citation prediction. Evidence can make a page easier to verify, understand and cite; it does not guarantee ranking or citation by a search engine or AI system.

Five evidence classes

What a strong free-tool page should make inspectable

1

Route facts

The page states the utility purpose, category and canonical route so a reader can identify exactly what the tool claims to do.

2

Implementation provenance

Where the catalog has the data, we expose the engine name, source class, license and related repository metadata instead of hiding the implementation origin.

3

Runtime and privacy boundary

Tool-specific pages describe where processing happens and what is or is not sent elsewhere. We do not infer that every Solarc utility is offline, serverless or dependency-free.

4

References and assumptions

Calculators, converters and validators should expose formulas, entered assumptions, reference tables or limitations when those facts materially affect interpretation.

5

Real-world evidence only

Screenshots, benchmarks, first-hand tests, dates and case evidence are published only when they were actually collected. We do not generate fake experience to imitate E-E-A-T.

What we refuse to claim

No fake experience. No citation guarantee.

  • E-E-A-T is not treated as a guaranteed Google ranking or AI-citation switch.
  • A Solarc page does not claim that Google, ChatGPT, Gemini or another system will cite it.
  • We do not fabricate first-person usage, professional credentials, customer outcomes, screenshots, tests or review dates.
  • A regulated, tax, fee, marketplace, finance or carrier value is not presented as safely current merely because a calculator can accept it.

Acceptance standard

Minimum evidence for a citation-worthy utility page

  • A clear canonical purpose and a useful output, transformation, checklist or reference — not a doorway page.
  • Implementation provenance where the catalog can substantiate it.
  • Explicit assumptions and limitations when an output can be misread as authoritative.
  • A runtime and privacy boundary that does not overclaim local or offline processing.
  • A path for correcting stale facts or reporting an evidence problem.

Found an evidence problem?

Report a stale reference, incorrect assumption, provenance mismatch or privacy-boundary problem. Corrections are more valuable than adding decorative authority signals.

Contact Solarc Labs