Evidence and validation

Know what each proof point establishes

Specifications, demonstrations and application results answer different questions. Kikobot separates them so engineering decisions are made on the right evidence.

Evidence ladder

From a catalogue value to an accepted application

01

Published specification

A datasheet value supports comparison under its stated conditions. It does not by itself guarantee output in a complete robot, machine or production cell.

02

Hardware demonstration

An official video shows that the pictured hardware and behaviour were demonstrated. It is not presented as a customer result or a universal cycle-time claim.

03

Application validation

The relevant payload, path, duty, tooling, environment and interfaces are checked against the proposed configuration before order.

04

Acceptance evidence

Where acceptance testing forms part of the project, the metric, test method, sample, duration and pass condition are agreed in the proposal.

Current public record

What is—and is not—published today

Missing evidence is stated plainly rather than replaced with a broad claim. Request the evidence required for your decision during evaluation.

Published

CI and DI brochures with model-level payload, reach or workspace, repeatability, speed and interface specifications.

Not currently public

Named customer deployment results, application cycle studies and certification files are not currently presented as public evidence.

Published

KH ratio-level electrical and mechanical ratings, stated as typical at 25 °C; peak torque is identified as a five-second rating.

Not currently public

Torque-speed curves, thermal derating, external-load limits and life-test reports are not currently public on this site.

Published

Official C1, C2 and D1 hardware demonstrations plus current product specifications from the portfolio brochure.

Not currently public

The demonstrations do not establish a supplied curriculum, software-version guarantee or performance result for a buyer's experiment.

Request evidence for an evaluation

What are you trying to build?

Choose the path that matches your project so the first conversation starts with the right technical context.