Framework
Verified vs claimed
Eight diagnostic questions for evaluating any humanoid robot maker. Each angle anchors a foundational DEPLOY signal as worked example. Use this page as a reference when comparing maker claims to verifiable deployment evidence.
Humanoid robotics is structurally susceptible to marketing-versus- deployment gaps. The category sells the same vocabulary ("autonomous," "commercial deployment," "scaled operations") across radically different verification states. The eight questions below partition that vocabulary into verifiable postures, so a comparison between two makers can be sharper than "both claim commercial deployment."
Angle 1 of 8
Framing without disclosure
Did a major public demonstration frame conditions differently from how the demo actually operated?
A maker demonstrates a capability publicly without disclosing the conditions under which the demonstration occurred. The verified-vs-claimed gap is between what the demo showed and what was actually true behind the demo. Operators should be skeptical of framing where the maker has the means to disclose operating conditions but chooses not to until disclosure is forced.
Applies when
- A public demonstration occurred with the maker's framing implying autonomous or unassisted operation.
- Subsequent reporting or disclosure revealed material conditions (teleoperation, scripted scenes, post-production cuts) the original framing omitted.
- The omission would have materially changed how a sophisticated operator interpreted the demo.
Worked example: DEPLOY foundational signal
Compare to: Disclosure as strategy. The opposite posture for the same underlying autonomy gap: discloses upfront rather than letting disclosure get forced.
Angle 2 of 8
Disclosure as strategy
Has the maker proactively disclosed teleoperation, supervised autonomy, or scope limits as part of the product's go-to-market positioning?
A maker explicitly discloses operational conditions (teleoperation, supervised autonomy, limited deployment scope) as part of the product's go-to-market positioning rather than hiding them. Disclosure shapes pricing, target market, and roadmap, signaling editorial confidence that an audience told the conditions upfront will value the offering anyway.
Applies when
- The maker proactively documents the gap between full autonomy and current operation.
- The disclosure is part of the product launch communication, not a defensive footnote added after press scrutiny.
- The disclosure shapes pricing, target market, or roadmap (not just legal risk mitigation).
Worked example: DEPLOY foundational signal
Compare to: Framing without disclosure. The inverse posture for the same underlying autonomy gap.
Angle 3 of 8
Depth with one customer
Does the maker have one customer deployment that has produced verifiable operational throughput data over months?
A maker produces verifiable operational throughput data from one customer deployment, anchoring commercial readiness through depth of a single relationship rather than breadth of pilots. The single-customer depth is editorial evidence; the throughput figure is verification. Contract structure matters: paid, multi-year, SLA-bound relationships count, paid pilots do not.
Applies when
- A single customer deployment has been operating long enough to produce throughput metrics (rule-of-thumb 6+ months).
- Those metrics are independently verifiable via the customer's disclosure or third-party reporting.
- The contract structure is real commercial (paid, multi-year, SLA-bound), not a pilot.
Worked example: DEPLOY foundational signal
Compare to: Enterprise breadth pre-throughput. The opposite shape: many customers, no throughput data yet.
Angle 4 of 8
Enterprise breadth pre-throughput
Does the maker have multiple high-profile customer pilots without any of them producing verifiable throughput data yet?
A maker locks in multiple high-profile customer pilots before any single deployment has produced verifiable throughput data, anchoring commercial-readiness narratives through customer count rather than operational results. The verification gap is that customer count alone signals commercial intent, not commercial outcome. Operators should treat customer-count framings as evidence of commercial credibility but not of operational delivery.
Applies when
- The maker has secured at least three named customer pilots.
- No individual deployment has produced multi-month throughput data.
- Editorial coverage frames the customer count as primary evidence of commercial readiness.
Worked example: DEPLOY foundational signal
Compare to: Depth with one customer. The inverse: one customer with throughput data, rather than many without.
Angle 5 of 8
Engineering credibility versus commercial verification
Does the maker carry a long engineering track record but no independent commercial deployment?
A maker has decades of credible engineering work but no independent commercial deployment, anchoring claims on engineering reputation rather than verified customer outcomes. The verification gap is that engineering credibility, however genuine, does not substitute for commercial verification. Deployments inside the maker's or parent corporation's own facility do not count as commercial customer deployment under the maker-facility rule.
Applies when
- The maker has a multi-decade public engineering track record.
- No commercial customer has independently disclosed deployment results.
- Parent-corporation or related-party facility deployments are research, not customer pilot, under the maker-facility rule.
Worked example: DEPLOY foundational signal
Compare to: OEM acceptance as verification. The resolved version: engineering credibility plus end-product OEM acceptance.
Angle 6 of 8
OEM acceptance as verification
Are robots deployed at a manufacturing facility producing finished goods accepted by the customer's quality control for retail sale?
A deployment's verification standard is end-product OEM acceptance: vehicles, devices, or finished goods accepted by the customer's normal quality control processes for delivery to retail. Structurally higher bar than logistics cycle-counting, because the end product carries the customer's brand warranty and the full engineering chain of acceptance behind it. An operational data envelope spanning seasonal mix and engineering change orders is the verification.
Applies when
- The deployment is at a manufacturing facility producing finished goods for sale, not a logistics or warehouse facility.
- The customer's QC processes have accepted the robot's contributed work.
- Operational data spans sufficient time to cover seasonal variation and engineering change orders (rule-of-thumb 6+ months).
Worked example: DEPLOY foundational signal
Compare to: Depth with one customer. Different verification bars for 'deployed in production': logistics cycles versus end-product OEM acceptance.
Angle 7 of 8
Pricing honesty as strategy
Does the maker price at hardware cost without bundling commercial-deployment infrastructure, and explicitly disclaim commercial-deployment readiness?
A maker prices a humanoid at hardware cost without bundling commercial-deployment infrastructure (RaaS contracts, integration services, enterprise software), and explicitly disclaims commercial-deployment readiness. The structural inverse of every other verified-vs-claimed angle: instead of over-claiming or under-disclosing commercial readiness, the maker under-claims and prices accordingly. Useful as a reference point for what a humanoid actually costs to manufacture when commercial-deployment infrastructure is unbundled.
Applies when
- The price is dramatically below commercial-deployment humanoid pricing (rule-of-thumb under $50,000).
- The maker's communications consistently frame the product as a research, education, or developer platform rather than a deployed worker.
- The absence of customer-deployment claims is explicit, not omission.
Worked example: DEPLOY foundational signal
Compare to: Enterprise breadth pre-throughput. The inverse: pricing reflects commercial-deployment infrastructure that does not yet have verified throughput.
Angle 8 of 8
Engineering trajectory claim pre-deployment
Did the maker frame an engineering demonstration as trajectory evidence toward commercial deployment, and has the trajectory subsequently been tested?
A maker presents engineering progress demonstrations explicitly framed as evidence of capability trajectory toward commercial deployment, attaching editorial accountability to subsequent events to demonstrate the trajectory has converged. Distinct from pure engineering-credibility framings because the trajectory claim implies near-term commercial deployment; subsequent events become implicitly held against that trajectory rather than against pure engineering milestones.
Applies when
- A public capability demonstration is framed as progress evidence, not a research milestone.
- The framing implies near-term commercial deployment, not multi-decade research horizon.
- Subsequent events at the same maker are implicitly evaluated against the trajectory claim.
Worked example: DEPLOY foundational signal
Compare to: Engineering credibility versus commercial verification. The time-sequential version: trajectory claim at event N tested at event N+1, versus point-in-time engineering credibility without commercial deployment.
Using the framework
When evaluating any humanoid maker, run the maker through the eight diagnostic questions in order. A maker may occupy more than one angle simultaneously; the angles are not mutually exclusive. The framework is a vocabulary for naming the gap between what a maker claims and what is currently verified, not a scoring rubric. Two makers occupying the same angle can have radically different commercial trajectories; the angle names the verification posture, not the commercial outcome.
New angles get added when an event surfaces a verified-vs-claimed posture not yet covered by the existing eight. Additions are deliberate; the canon stays small enough to remain useful as a reference rather than expanding into a catalog. Operator feedback on missing distinctions, or proposals for new angles, are welcome via the DEPLOY subscriber channel.
Editorial discipline
These angles are one layer of DEPLOY's broader editorial discipline. The discipline also covers primary-source verification (every URL in every signal is verified before publication), multi-source confirmation at distinct editorial functions, the maker-facility rule (deployment inside a maker's or parent corporation's own facility is research, not commercial customer deployment), and inverse-index cross-linking that lets the citation graph compound across signals. The angles above are the most reader-visible layer of that discipline; the rest operates at the editorial production level.