Evidence before endorsement

Enterprise readiness depends on your workload, risks and procurement requirements. A vendor claim is a starting point for verification.

Four distinct evidence levels

  1. Not assessed: no usable official text has been reviewed.
  2. Not found or needs clarification: the inspected pages lack a claim or include qualifications. This does not prove the feature is absent.
  3. Company-published: an attributable claim with a source excerpt. It is not an audited control.
  4. Independently verified: requires a dated, scoped review artifact or buyer-run test. The automated research pipeline does not assign this status.

Software checks

Security assurance, identity, permissions, auditability, data handling, reliability and measured outcomes. Request audit scope and exceptions, test access removal and tenant isolation, and validate accuracy on your own representative workload.

Construction robotics checks

Safety, field deployments, measured productivity, operating limits, service and workflow integration. Include setup, human intervention, downtime and rework in a supervised site pilot.

What the dates mean

A source review date records when text was inspected, not when an audit was issued or when a feature shipped. Evidence over 30 days old is flagged for rechecking; that threshold does not mean newer evidence is verified. Undated excerpts remain undated.

How to use a company page

Open its evidence checks, inspect the original sources, and download the procurement brief. Record an owner, scope, test result and artifact for each requirement before deciding.