Claim
Vendor claim, demo, announcement, or public signal.
Methodology
We classify public claims, deployment signals, readiness, risk, and missing proof so buyers can see what is worth watching, tracking, or evaluating.
Evaluation Path
Vendor claim, demo, announcement, or public signal.
Customer signal, commercial agreement, pilot context, operating metric, or independent validation.
Evidence quality, readiness, use-case fit, missing proof, and buyer risk.
Ignore, watch, track, contact, or evaluate for a scoped pilot.
Score System
Scores help compare public evidence and buyer readiness. They are not technical certification, procurement approval, or vendor endorsement.
How real and substantiated is the robot?
Can a buyer realistically evaluate it for a defined use case?
How strong is the public evidence behind the claim?
Validation Ladder
The ladder shows how close a public signal is to operating evidence without overstating what the evidence proves.
Unverified claim or concept.
Vendor-stated capability.
Controlled demo or lab signal.
Joint test or evaluation signal.
External pilot signal.
Customer-confirmed operating signal.
Commercial agreement signal.
Repeated deployment signal.
Operating metrics disclosed.
Independently validated deployment evidence.
Public Claims
Vendor announcements, demos, and partnerships can be useful signals, but they do not prove operating deployment unless the customer, workflow, scale, metrics, or commercial context is clear.
Useful signal, but not operating evidence.
Relevant if customer, task, and operating context are named.
Stronger when workflow and commercial context are visible.
Stronger when uptime, intervention rate, cycle time, or cost data is disclosed.
Buyer Recommendation
Too speculative or weakly evidenced.
Relevant, but not buyer-actionable yet.
Meaningful signals exist, but proof remains incomplete.
Specific workflow or customer signal may justify direct engagement.
Strong enough for a scoped buyer discussion.
Red Flags
Update Process
Humanoids Watch does not certify robots, approve deployments, or replace technical diligence. It helps buyers separate public evidence from claims and identify what still needs verification.
Use The Methodology
Apply the scoring logic to deployment signals, robot profiles, use cases, and vendor watchlists.