GOVERNATLAS / OUR EDITORIAL METHOD

How we review
product evidence.

What a reviewed claim means, how we handle missing evidence and why inclusion never amounts to certification.

GovernAtlas publication standard

Evidence before assertion.

GovernAtlas is designed to report what a preserved source supports at a known point in time. It does not certify legal compliance or fill evidence gaps with generated conclusions.

What does “reviewed” actually mean?

It means a published statement has passed the applicable source and editorial review gates. It does not mean GovernAtlas has installed the product, reproduced a vendor’s test, completed a security audit or assessed your legal obligations. Read the classification beside the statement: a reviewed vendor assertion remains a vendor assertion.

Use a dossier to identify what a current source supports and which questions your own evaluation must answer. Use our guides for proposed methods and working materials. A test described in a guide is a suggested activity unless a separate, explicitly scoped report states that we performed it.

How does a source become a published statement?

  1. Identify the subject. Resolve the product, organization and current identity. A company homepage may not establish that an older product or edition remains available.
  2. Capture the material. Preserve a source observation with its URL, capture context and artifact hash. A hash identifies captured bytes; it does not prove that the source’s claims are true.
  3. Review the proposed wording. Check that the observation supports the statement, its scope and its attribution. Avoid transferring a parent company’s capability, another edition’s feature or a linked project’s result to the subject.
  4. Publish through the editorial gates. Current approved wording and source provenance become eligible for the public view. Private candidates and unresolved records remain excluded.
  5. Revisit and correct. Review and expiry state govern continued visibility. Corrections enter review with a retained reason rather than silently replacing history.

01

Source before claim

Every factual claim must reference a preserved observation from an identified source.

02

Classification is explicit

Vendor assertions, first-party assertions, regulatory records, independent verification, and GovernAtlas analysis are never presented as interchangeable.

03

Machines propose; people publish

Automated capture and change detection can create private candidates. Only an authorized human review can publish wording.

04

Unknown stays unknown

Missing evidence is not converted into a negative result, estimate, score, or inferred capability.

05

Freshness is enforced

Claims and records carry review and expiry state. Stale evidence is removed from current public views.

06

History is preserved

Corrections, withdrawals, disputes, and retractions remain auditable instead of being silently overwritten.

Evidence classifications

Vendor asserted
A statement made in vendor-owned public material; not independently verified.
First-party asserted
A statement from a product or project’s own first-party material. The Algorithm’s statements about its own products also retain explicit first-party attribution.
Regulatory record
A record from an official regulator, legislature, government body, or standards authority.
Independently verified
A claim supported by an eligible independent primary source and approved review.
GovernAtlas analysis
A clearly identified interpretation based on cited evidence, never presented as source language.

Corrections and disputes

Anyone may submit a correction with supporting evidence. A correction does not automatically change a public record; it enters the same review and audit process. Material errors are corrected or retracted with a retained reason and timestamp.

Why can a source be insufficient?

An inaccessible page, an ambiguous identity, an announced acquisition or an undated description can leave a material question unanswered. We may retain a private hold while seeking better evidence. Missing evidence is not a negative product finding, and absence from this directory is not evidence of poor quality.

For example, an old documentation page can establish what was described at that time while failing to establish current sales availability. A security statement about an organization may not apply to every product or deployment. We narrow the wording, seek a suitable source or withhold the claim; we do not bridge the gap with an inference presented as fact.

How should you read dates, classifications and evidence hashes?

The observation date concerns the captured source. The review date concerns our editorial review. Neither is automatically a product release date or the date a vendor last verified a feature. A source may change after capture. Inspect the current source and confirm material requirements with the supplier before relying on them.

Classifications describe the authority behind a particular statement, not a numerical trust score for the whole company. A long dossier, a large claim count or a recognizable logo is not independent verification. Compare the actual scope and limitations of the evidence needed for your decision.

Who writes the analysis, and can companies pay to change it?

GovernAtlas publishes editorial interpretations and proposed buying methods separately from attributed product facts. We identify primary references and avoid presenting proposed demonstrations as completed benchmarks. Where a product is associated with The Algorithm, first-party attribution must remain explicit.

Visitor reading, reviewed dossiers, guides and public tools are free. Commercial services must be disclosed and do not purchase a favorable classification, an editorial conclusion or a product ranking. Accurate identity and reviewed corrections are not conditional on payment. Read the commercial and ownership disclosures ↗

How can you challenge a record?

Send the product or page URL, the precise statement at issue and a source supporting your correction. Explain whether the issue concerns identity, wording, edition, availability, date or classification. Avoid sending credentials or confidential customer data. Submission starts a review; it does not automatically publish a replacement.

Submit an evidence-backed correction ↗

For a buying decision, begin with our category briefs, inspect the product dossiers and take a working evaluation guide into your review.