Version 3.0
Last updated: July 18, 2026
Next scheduled methodology review: October 2026
Status: Current public methodology
Humanoid Analytics tracks one of the fastest-moving and most heavily promoted technology markets in the world. Our purpose is simple: to separate observable commercial progress from demonstrations, announcements, projections, and hype.
A robot shown in a controlled video is not the same as a robot working for a customer. A partnership announcement is not the same as a paid pilot. A shipment claim is not the same as an operational deployment. A funding round can strengthen a company without proving that its robots work reliably or economically.
Our evidence standards make these differences visible. Every material classification is based on the strength of the underlying sources, the type of activity observed, customer and commercial verification, measurable operating evidence, continuity, and recency.
These standards apply equally to public articles, free trackers, paid subscriptions, CSV exports, custom research, investor briefs, corporate intelligence, deployment reviews, and sponsored content.
Methodology at a Glance
Humanoid Analytics evaluates market claims through five separate lenses:
- Claim status: Is the claim confirmed, partially confirmed, unverified, delayed, or contradicted?
- Evidence Score: How strong is the best current public evidence of real-world commercial activity?
- Confidence level: How certain are we that the underlying facts and classification are accurate?
- Lifecycle status: Is the activity planned, active, completed, expanded, inactive, or stale?
- Source quality: Is the evidence based on customer confirmation and official records, or mainly on company statements and promotional material?
These measures answer different questions. A company can have a highly credible laboratory demonstration with a low Evidence Score. It can also have a major deployment claim with low confidence because the customer, payment status, scale, autonomy, or operating results have not been independently confirmed.
Humanoid Analytics uses one public 0 to 10 Evidence Score. Investor relevance, strategic relevance, funding, valuation, technical capability, and sponsor relationships are not additional score components.
Scope and Audience Neutrality
Humanoid Analytics serves investors, financial professionals, corporate strategy teams, competitive-intelligence teams, business-development professionals, and industrial deployment teams.
The same evidence rules apply to every audience.
- A paying customer does not receive a different classification.
- An investor request does not change the scoring threshold.
- A sponsor does not receive favorable treatment.
- A company response may add evidence but does not control the conclusion.
- A custom watchlist uses the same standards as a public tracker.
Audience relevance may change which evidence is highlighted. It must never change claim status, source tier, deployment level, lifecycle, confidence, score components, score ceiling, or final Evidence Score.
What We Track
Humanoid Analytics covers:
- Humanoid robotics companies and major corporate programs
- Robots, enabling technologies, and product platforms
- Customer pilots, paid pilots, and operational deployments
- Repeat deployments, fleet expansion, and commercial-scale use
- Funding, valuations, acquisitions, IPOs, and strategic investments
- Ownership changes and major financial transactions
- Manufacturing facilities, production targets, output, and shipment claims
- Partnerships, supply chains, and distribution agreements
- Technology demonstrations and performance claims
- Pricing, labor substitution, uptime, service cost, and operating economics
- Safety, autonomy, teleoperation, reliability, and human supervision
We focus on evidence that helps answer practical questions:
- Which robots are moving beyond controlled demonstrations?
- Which companies have identifiable customer activity?
- Which deployments are paid, operational, repeated, or expanding?
- Which claims are supported by customers or independent evidence?
- Which companies are producing and delivering robots rather than announcing capacity?
- Which applications appear capable of delivering measurable economic value?
- Which funding and transaction claims have actually closed?
- Which important claims remain unverified, delayed, stale, or contradicted?
Unit of Evidence
The primary unit of analysis is a structured, dated, source-linked evidence event.
Every material event should identify:
- The exact claim
- The organization or person making the claim
- The event date and publication date
- The company, robot, customer, investor, partner, and location when relevant
- Source URLs and source tiers
- Claim status
- Deployment level
- Lifecycle status
- Confidence level
- Evidence Score components
- Any applicable score ceiling
- Final Evidence Score
- Missing proof
- Previous classification and change reason
- Last-checked date
- Methodology version
An article is a presentation layer. The underlying evidence event and revision history are the analytical record.
Claim Status
Every material claim may receive one of five statuses.
| Claim status | Definition |
|---|---|
| Confirmed | The central claim is supported by strong, directly checkable evidence such as customer confirmation, a financial or regulatory record, procurement documentation, or multiple reliable independent sources. |
| Partially confirmed | Important elements are supported, but scale, payment status, timing, operating status, autonomy, customer identity, transaction completion, or another material detail remains unverified. |
| Unverified | The claim is public but depends mainly on a company statement, promotional content, anonymous sourcing, or reporting that cannot be independently checked. Unverified does not mean false. |
| Delayed | A previously announced launch, production target, pilot, deployment, financing, acquisition, or other milestone has not occurred within the stated period, or later evidence indicates postponement. |
| Contradicted | Stronger available evidence conflicts with the central claim, timeline, quantity, operating status, transaction status, or commercial characterization. |
Claim status is assigned at the claim level, not automatically to an entire company. A company may have a confirmed funding close, a partially confirmed customer pilot, and an unverified production target at the same time.
Claim status describes support for the claim. It does not describe whether the development is favorable, investable, or strategically attractive.
Source Quality
Sources are evaluated according to independence, specificity, direct knowledge, and verifiability.
| Source tier | Typical sources | Weight |
|---|---|---|
| Tier 1, direct or official evidence | Regulatory filings, financial statements, public procurement records, court records, transaction records, direct customer confirmation, official records, or operating data attributable to the customer site | Very strong |
| Tier 2, strong independent evidence | Independent reporting with named sources, site access, photographs or video from the operating environment, identifiable documents, or detailed research from a credible institution | Strong |
| Tier 3, detailed first-party disclosure | Company announcements, investor materials, product documentation, executive statements, or demonstration material containing specific dates, quantities, customer names, and operating details | Moderate |
| Tier 4, promotional or incomplete evidence | Edited demonstrations, event presentations, vague partnership announcements, unsourced media summaries, social posts, or claims without sufficient operating context | Weak |
| Tier 5, unverifiable information | Anonymous claims, copied lists without traceable sourcing, AI-generated summaries presented as evidence, rumors, or marketing language without checkable facts | Not sufficient on its own |
Source Interpretation Rules
- A high source tier verifies only what the source can directly establish.
- A regulatory filing is strong evidence that a statement was formally made, but a forward-looking operating target remains a forward-looking claim.
- A company announcement can confirm its own announcement, but it cannot independently confirm customer operation.
- A customer statement is strong evidence of activity at that customer, but it may not establish fleet-wide performance.
- Multiple articles that repeat the same company announcement do not create independent corroboration.
- A sponsor-provided document remains first-party evidence unless a customer, official record, or independent source corroborates it.
- An unnamed source may inform research direction but cannot independently support a high-confidence material classification.
- AI output is never a source.
Source tier does not determine truth by itself. It determines how much verification the source provides and how heavily it should influence a classification.
The Humanoid Analytics Evidence Score
The official name is the Humanoid Analytics Evidence Score, shortened to Evidence Score.
The Evidence Score is a 0 to 10 assessment of the strongest current documented public evidence of real-world commercial activity associated with a specific company, robot, or deployment.
It measures commercial evidence. It does not measure:
- Technical sophistication
- Product quality
- Safety certification
- Total addressable market
- Management quality
- Brand visibility
- Funding strength
- Valuation attractiveness
- Long-term potential
- Expected investment return
- Overall company quality
The Evidence Score is not an investment rating, credit rating, technical certification, vendor recommendation, or buy, sell, or hold opinion.
Evidence Score Components
The raw score is calculated across five dimensions.
1. Source Quality, 0 to 3 Points
| Points | Requirement |
|---|---|
| 3 | Direct customer confirmation, official record, regulatory filing, or strong independent evidence from the operating environment |
| 2 | Detailed, attributable first-party disclosure or commercial agreement with identifiable parties and specific facts |
| 1 | Company-only statement, demonstration, event presentation, or secondary reporting with limited verification |
| 0 | Untraceable, anonymous, or unverifiable information |
2. Real-World Operation, 0 to 3 Points
| Points | Requirement |
|---|---|
| 3 | Repeated or continuing operation in a real customer environment beyond a limited trial |
| 2 | Active or completed customer pilot in a real operating environment |
| 1 | Planned pilot, internal testing, controlled demonstration, preorder, or shipment without operating proof |
| 0 | No evidence that the robot has operated outside development or promotional settings |
3. Commercial Commitment, 0 to 2 Points
| Points | Requirement |
|---|---|
| 2 | Paid pilot, purchase, repeat order, expansion, disclosed revenue, or binding commercial deployment |
| 1 | Named pilot, customer agreement, preorder, or shipment linked to an identifiable customer, with payment status unclear |
| 0 | No identifiable customer or commercial commitment |
4. Measurable Operating Proof, 0 to 1 Point
| Points | Requirement |
|---|---|
| 1 | A specific operating metric such as active units, hours worked, tasks completed, throughput, uptime, error rate, productivity, intervention rate, labor impact, or deployment duration is disclosed with sufficient context |
| 0 | No meaningful operating metric, or a metric lacks enough context to interpret |
Production capacity, units ordered, units shipped, social-media views, funding, valuation, and benchmark performance outside a customer workflow are not operating metrics for this component.
5. Continuity and Current Verification, 0 to 1 Point
| Points | Requirement |
|---|---|
| 1 | Evidence shows repeat use, expansion, follow-on activity, or current verification within the applicable review period |
| 0 | The event has no follow-up, is outside the review interval, or cannot support a current-status claim |
Current verification means that the relevant activity or status has been checked within its review interval. It does not turn a demonstration into a deployment.
Evidence Gates and Score Ceilings
The component total is the raw score. Evidence gates and ceilings prevent weak sources or non-operating signals from producing an overstated final score.
The published Evidence Score is the lower of:
- The raw component total
- The applicable evidence ceiling
When several ceilings apply, use the lowest ceiling.
| Evidence condition | Maximum published score |
|---|---|
| Tier 5 or no traceable supporting source | 0 |
| Promotional, demonstration, or internal evidence with no identifiable external customer | 4 |
| Planned pilot, memorandum, letter of intent, preorder, purchase announcement, or shipment without operating proof | 6 |
| Company-only claim of customer operation without customer, official, or strong independent corroboration | 6 |
| Active customer pilot with corroboration but no proof of repeat or continuing use | 8 |
| No measurable operating metric | 8 |
| Event is stale for current-status purposes | Excluded from the current score; historical score retained |
Minimum Gates for Scores of 7 to 10
A score of 7 or higher requires:
- An identifiable external customer or operating organization
- Evidence of activity in a real customer environment
- Customer, official, or strong independent corroboration
- A current, non-stale event
A score of 9 or higher additionally requires:
- Confirmed commercial commitment
- Measurable operating proof
- Repeat, continuing, expanded, or sufficiently sustained activity
- High confidence
A score of 10 requires:
- All five score dimensions at their maximum
- No unresolved material contradiction
- A current additional source review
Commercial-scale deployment is not established by the score alone. It also requires evidence of meaningful recurring activity across multiple sites, customers, fleets, or workflows.
Funding, valuation, production targets, sponsor relationships, visibility, and technical ambition never raise an Evidence Score or remove a ceiling.
Evidence Tiers
| Score | Evidence tier | Interpretation |
|---|---|---|
| 9 to 10 | Operating proof with metric | Strong current evidence of real customer operation, commercial commitment, measurable activity, and continuity |
| 7 to 8 | Named customer deployment evidence | Credible current pilot or deployment evidence involving an identifiable customer, but questions about scale, economics, metrics, or repetition may remain |
| 5 to 6 | Commercial signal, limited operating proof | A meaningful customer, shipment, preorder, or planned-deployment signal exists, but real operation or payment evidence is incomplete |
| 3 to 4 | Demonstration or product signal only | The product is visible, orderable, demonstrated, or associated with internal activity, but external customer operation is not established |
| 0 to 2 | Insufficient commercial evidence | Prototype, early concept, vague claim, untraceable claim, or no qualifying commercial event |
The underlying event record, ceiling, lifecycle, confidence, and missing proof must be consulted for context.
Event Score, Current Score, and Historical High
Three concepts must remain separate.
Event Score
The score assigned to one specific evidence event under the methodology version recorded at the time of assessment.
Current Evidence Score
The highest final score among qualifying current events that are active, expanded, recently completed, or otherwise verified within the applicable review interval.
The current score must display:
- The supporting event
- Event date
- Last-checked date
- Lifecycle status
- Confidence
- Methodology version
- Any applied ceiling
Historical High
The highest validated event score previously achieved, even if the supporting event is now completed, inactive, or stale.
A historical high must never be displayed as current commercial evidence without a clear historical label.
If no event qualifies as current:
- Display current status as not currently verified, stale, or not available.
- Preserve the last verified event and its historical score.
- Do not silently present the historical high as the current score.
New evidence may upgrade or downgrade an event. Every material change must preserve the prior value, new value, source, date, reason, and methodology version.
Deployment Evidence Levels
The Evidence Score is complemented by a plain-language deployment level.
| Deployment level | Definition |
|---|---|
| Lab demonstration | Capability shown in a controlled development environment with no customer-use evidence |
| Public demonstration | Capability shown at an event, in a promotional video, or through a staged public presentation |
| Internal testing | Testing by the developer or an affiliated organization without independent customer-deployment evidence |
| Planned customer pilot | A named customer or partner has announced a future trial, but operating activity has not yet been shown |
| Active customer pilot | A robot is being evaluated in a real customer environment, with payment or production use unclear |
| Paid pilot | Payment, commercial terms, procurement, or revenue involvement has been confirmed or reliably reported |
| Operational deployment | The robot is performing useful work in a real operating environment beyond a staged demonstration or limited evaluation |
| Repeat deployment | The customer has extended, renewed, repeated, or expanded the initial deployment |
| Commercial-scale deployment | Deployment spans multiple sites, customers, fleets, or workflows at a scale that indicates meaningful recurring commercial activity |
Movement between levels is based on new evidence. A future agreement does not become an active pilot solely because its scheduled date has arrived. Operating evidence must be observed or confirmed.
A deployment level and Evidence Score must not be treated as interchangeable. The level describes the kind of activity. The score describes the strength of the evidence supporting current commercial activity.
Confidence Level
Confidence measures the reliability of the classification, not the commercial maturity of the company.
| Confidence | Standard |
|---|---|
| High | At least one Tier 1 source, or multiple consistent Tier 2 sources, supports the classification. Material details are specific and no major conflict remains unresolved. |
| Medium | The classification is supported by a detailed Tier 2 or Tier 3 source with partial corroboration, but one or more important details remain uncertain. |
| Low | Evidence is company-only, promotional, vague, stale, difficult to verify, or materially disputed. |
A high-confidence prototype is still a prototype. A low-confidence deployment claim may still be important, but it must not be treated as proven commercial activity.
Confidence applies to the specific classification. It is not a confidence forecast about company success.
Lifecycle and Recency
Historical events do not disappear when they become old, but they must not be presented as evidence of current activity without recent confirmation.
Each event may be marked as:
- Planned: Announced but not yet shown to have started
- Active: Currently operating or being executed
- Completed: The stated pilot, deployment, or transaction concluded
- Expanded: Follow-on activity, additional units, sites, tasks, or customers are confirmed
- Inactive: Activity ended, was discontinued, or is no longer operating
- Stale: The event remains historically valid, but current status has not been verified within the applicable review period
Review intervals depend on claim type:
| Claim type | Target review interval |
|---|---|
| Active deployment, manufacturing output, or shipment claim | 90 days |
| Pilot, preorder, commercial agreement, or production plan | 120 days |
| Prototype or public demonstration | 180 days |
| Funding, acquisition, or completed historical transaction | Reviewed when new information emerges |
If an active-status claim cannot be refreshed within 12 months, it is marked stale. If no supporting activity is found for 24 months, it may be removed from current rollups while remaining in the historical record.
A stale event retains its event score and historical value but is excluded from the current Evidence Score.
Financial and Transaction Evidence
Funding and transaction intelligence is important to investors and corporate strategy teams, but it remains separate from the Evidence Score.
Funding Event Status
| Status | Definition |
|---|---|
| Targeted | The company is seeking or considering financing. No commitment is established. |
| Announced | A financing has been publicly described, but completion or receipt of funds has not been sufficiently established. |
| Committed or signed | Binding commitments or signed transaction documents are reported, but closing conditions may remain. |
| First close | An initial portion of a financing has closed; additional capital may still be targeted. |
| Closed | Completion is supported by a filing, financial statement, investor confirmation, detailed company disclosure, or consistent attributable sources. |
| Withdrawn or terminated | The planned financing or transaction was cancelled, expired, or did not proceed. |
| Unknown | Public evidence is insufficient to determine transaction status. |
Funding event status and claim status must both be recorded. A company may announce a targeted raise with a confirmed claim status, while the financing itself remains targeted rather than closed.
Financing Type
Distinguish:
- Primary equity issued by the company
- Secondary share sale between existing and new holders
- Debt financing
- Convertible note or similar instrument
- Grant, subsidy, prize, or government support
- Strategic investment
- Mixed financing
- Undisclosed structure
Only primary capital and applicable debt or grants should be described as capital raised by the company. Secondary proceeds paid to selling shareholders must not be counted as new company capital.
Financial Recording Rules
- Distinguish amount sought, committed, and closed.
- Distinguish current-round proceeds from cumulative company funding.
- Do not double-count an extension, second close, or previously disclosed tranche.
- Identify the currency and the date used for any conversion.
- Preserve the original-currency amount.
- Label estimates, reported ranges, and undisclosed values.
- Distinguish pre-money and post-money valuation when known.
- Do not treat valuation as cash raised.
- Distinguish equity value, enterprise value, purchase price, and consideration when reporting acquisitions.
- Identify whether a named investor led, participated in, advised on, or merely held a prior investment.
- Separate announced, signed, approved, and closed acquisition stages.
- Record whether transaction values include stock, cash, earnouts, debt, or undisclosed consideration when known.
Funding can change runway, ownership, hiring capacity, or manufacturing resources. It does not prove customer operation and does not increase the Evidence Score.
Manufacturing, Orders, Shipments, and Deployment
These stages must remain separate:
| Stage | What it establishes | What it does not establish |
|---|---|---|
| Capacity target | A stated future output ambition | Installed capacity, actual production, delivery, or demand |
| Facility announced | A plan for a manufacturing site | Construction, tooling, production, or output |
| Facility under construction or tooling | Observable implementation progress | Completed capacity or production volume |
| Trial or pilot production | Early units are being produced | Stable serial production or customer delivery |
| Serial production stated | The company says repeat production has begun | Actual output unless unit evidence is provided |
| Units produced | A number of units has reportedly been completed | Shipment, payment, customer receipt, or operation |
| Units shipped | Units reportedly left the producer | Customer receipt, acceptance, payment, or operation |
| Units delivered | An identifiable recipient reportedly received units | Useful work, uptime, autonomy, or commercial success |
| Units operating | Robots are shown or confirmed performing work | Payment, reliability, economics, or continued use unless separately evidenced |
| Repeat or expanded deployment | Follow-on customer activity is established | Commercial scale across the wider market |
Recording rules:
- Capacity is not output.
- Output is not shipment.
- Shipment is not delivery.
- Delivery is not operation.
- Operation is not automatically paid deployment.
- An order, preorder, reservation, memorandum, or letter of intent is not revenue unless accounting or transaction evidence supports that conclusion.
- State whether unit counts are cumulative, annual, quarterly, monthly, or point-in-time.
- Distinguish internally produced units from third-party manufactured units when material.
- Record the customer, destination, date, acceptance status, and operating context when public.
- Treat affiliate or founder-controlled deployments as internal evidence unless an arm’s-length customer relationship is established.
Manufacturing and shipment evidence may support commercial interpretation, but it affects the Evidence Score only through the published components and applicable ceilings.
Standards by Claim Type
Different claims require different evidence.
| Claim area | Stronger evidence | Weaker evidence |
|---|---|---|
| Customer activity | Customer confirmation, procurement record, paid pilot, repeat order | Logo use, memorandum, generic partnership |
| Deployment | Robots operating in a real customer environment with dates and tasks | Laboratory video, event demonstration, future rollout statement |
| Manufacturing | Operating facility, production output, supplier records, delivered units | Factory rendering, future capacity target, opening announcement |
| Shipments | Units linked to recipients, delivery dates, and operating status | Aggregate shipment claim without recipients or use context |
| Funding | Filing, financial statement, investor confirmation, or detailed closed-transaction disclosure | Target raise, rumored valuation, unspecified strategic financing |
| Acquisition or ownership | Filing, signed agreement, regulatory approval, or closing confirmation | Rumor, exploratory statement, or unnamed-source speculation |
| Technology | Repeated task performance in realistic conditions with runtime, assistance, and failure information | Edited demonstration without autonomy, assistance, or failure disclosure |
| Economics | Price, uptime, supervision, service cost, productivity, payback, and renewal evidence | Broad labor-replacement or cost-saving claim |
| Safety | Incident record, test protocol, certification, customer procedure, or attributable operational data | General statement that a system is safe |
Autonomy and Human Assistance
Humanoid robot performance must not be described as autonomous unless available evidence supports that characterization.
Where material, Humanoid Analytics distinguishes among:
- Fully autonomous operation
- Supervised autonomy
- Human-in-the-loop assistance
- Remote intervention
- Continuous teleoperation
- Scripted or preprogrammed behavior
- Unknown or undisclosed control mode
Teleoperation and human assistance can be commercially useful. They are not treated as failures. They must, however, be disclosed when they materially affect claims about autonomy, labor substitution, cost, safety, or scalability.
A claim of autonomy should identify, when available:
- Task boundaries
- Operating environment
- Human monitoring
- Intervention frequency
- Recovery procedure
- Runtime
- Failure conditions
- Whether footage is continuous or edited
Audience Relevance and Derived Analysis
Each evidence event may include three relevance fields.
Investor Relevance
Possible implications for:
- Screening and diligence
- Funding-versus-commercial-progress comparison
- Capital efficiency
- Ownership and transaction risk
- Portfolio monitoring
- Thesis questions
Strategic Relevance
Possible implications for:
- Competitors
- Customers
- Partners
- Suppliers
- Market entry
- Product positioning
- Acquisition targets
Deployment Relevance
Possible implications for:
- Vendor selection
- Pilot design
- Procurement
- Integration
- Reliability
- Safety
- Economics
Relevance fields are analyst interpretation. They must:
- Be labeled as analysis or inference
- Identify the supporting evidence
- State important missing information
- Avoid personalized investment recommendations
- Never change the Evidence Score
Derived Comparisons
Funding-versus-progress, capital-efficiency, peer, and commercial-readiness comparisons must:
- Identify the underlying fields and event dates
- Use consistent currencies and time periods
- Distinguish disclosed facts from estimates
- State calculation methods and assumptions
- Avoid false precision when data is incomplete
- Identify material differences in company stage, geography, product, and business model
- Preserve unknown or undisclosed values rather than inventing estimates
A derived comparison is not a new evidence score unless it is formally added through a future public methodology revision.
How Conflicting Evidence Is Handled
When sources conflict, Humanoid Analytics does not silently choose the most favorable or most recent claim.
We apply the following rules:
- Direct customer evidence and official records generally outweigh company marketing.
- A later source does not automatically outweigh an earlier source if it is less direct or less specific.
- The disputed elements are separated from facts that remain supported.
- Both positions are documented when the conflict cannot be resolved.
- The claim is marked partially confirmed, delayed, or contradicted when the evidence requires it.
- Confidence is reduced until the material conflict is resolved.
- The lower applicable score or ceiling is used when a conflict affects a high-score requirement.
- Material conflicts remain visible in the revision history.
Research and Review Process
Material tracker entries follow a consistent workflow:
- Capture the claim: Record the exact statement, date, organization, and source.
- Decompose the claim: Separate customer identity, quantity, timing, payment, transaction status, autonomy, operating status, and performance into checkable elements.
- Collect sources: Prioritize direct customer evidence, official records, and reliable independent reporting.
- Classify the sources: Assign source tiers based on independence, specificity, and verifiability.
- Classify financial or manufacturing status: Keep funding, transaction, production, shipment, delivery, and deployment stages separate.
- Calculate the raw score: Apply the five published score components.
- Apply gates and ceilings: Record every applicable ceiling and reason.
- Assign status and confidence: Determine what is known, uncertain, delayed, stale, or contradicted.
- Record recency: Publish the event date, last-checked date, and lifecycle status.
- Assess relevance: Add investor, strategic, and deployment relevance without changing the score.
- Review material classifications: Scores of 7 to 10, commercial-scale claims, material contradictions, and records involving an active sponsor receive an additional source and conflict recheck.
- Monitor and correct: Update classifications when stronger or newer evidence becomes available.
No material claim status, Evidence Score, confidence level, ceiling, or correction may be published without human review of the underlying sources.
Public Display and Export Requirements
Whenever an Evidence Score is displayed, the accessible supporting record should include:
- Final Evidence Score
- Evidence tier
- Score component breakdown
- Applied ceiling and reason, if any
- Claim status
- Deployment level
- Lifecycle status
- Confidence
- Event date
- Last-checked date
- Current or historical label
- Source basis
- Key missing proof
- Methodology version
CSV exports, paid reports, watchlists, comparisons, and alerts must preserve these fields or provide a direct link to them. A score must not be separated from the context required to interpret it.
The methodology remains public. Payment provides depth, history, workflow, monitoring, exports, comparisons, and decision support, not a more favorable classification.
Worked Example
The following hypothetical example shows how evidence can progress without overstating commercial maturity.
Stage 1: Laboratory Demonstration
A company publishes an edited video of one robot performing a task in its own laboratory. No customer, duration, payment, or operating metric is disclosed.
- Source quality: 1
- Real-world operation: 0
- Commercial commitment: 0
- Measurable operating proof: 0
- Continuity and current verification: 1
- Raw score: 2
- Applicable ceiling: 4 for demonstration evidence with no external customer
- Final Evidence Score: 2, insufficient commercial evidence
- Claim status: Confirmed demonstration, unverified commercial readiness
- Confidence: High that the demonstration occurred, low regarding commercial relevance
Stage 2: Named Customer Pilot
The developer and a named manufacturer confirm that a pilot is active at the customer’s facility. The robot performs a defined task, but payment, scale, uptime, and productivity are not disclosed.
- Source quality: 3
- Real-world operation: 2
- Commercial commitment: 1
- Measurable operating proof: 0
- Continuity and current verification: 1
- Raw score: 7
- Applicable ceiling: 8 because repeat or continuing use is not established
- Final Evidence Score: 7, named customer deployment evidence
- Claim status: Confirmed pilot, partially confirmed commercial status
- Confidence: High
Stage 3: Company-Only Expansion Claim
The developer states that ten robots are operating under a paid agreement and publishes uptime and task-volume figures. The named customer does not confirm the expansion, and no official or strong independent corroboration is available.
- Source quality: 2
- Real-world operation: 3
- Commercial commitment: 2
- Measurable operating proof: 1
- Continuity and current verification: 1
- Raw score: 9
- Applicable ceiling: 6 for a company-only claim of customer operation
- Final Evidence Score: 6, commercial signal with limited corroborated operating proof
- Claim status: Partially confirmed
- Confidence: Medium or low, depending on the supporting detail
- Missing proof: Customer, official, or strong independent confirmation of the expanded paid operation and metrics
The ceiling prevents detailed first-party claims from producing a high score without independent operating evidence.
Stage 4: Repeat Paid Deployment With Metrics
The customer confirms that ten robots have operated across three sites for six months under a paid agreement. The customer reports task volume, uptime, and expansion into an additional workflow.
- Source quality: 3
- Real-world operation: 3
- Commercial commitment: 2
- Measurable operating proof: 1
- Continuity and current verification: 1
- Raw score: 10
- Applicable ceiling: None below the raw score
- Final Evidence Score: 10, operating proof with metric
- Claim status: Confirmed
- Confidence: High
Separate Funding Event
If the same company closes a major funding round during any stage:
- Record the financing status, type, amount, currency, investors, and valuation terms.
- Classify the funding claim independently.
- Explain how the financing may affect runway, manufacturing resources, or ownership.
- Do not add points to the Evidence Score.
Corrections
Humanoid Analytics updates articles, trackers, exports, and classifications when new or stronger evidence becomes available.
Material factual corrections should include:
- Date of correction
- Previous statement or classification
- Corrected information
- Reason for change
- Evidence supporting the correction
- Previous and new score components
- Previous and new ceiling
- Previous and new final score
- Effect on current or historical status
- Methodology version
Silent changes are limited to spelling, formatting, broken links, and other edits that do not alter the substance of a claim.
Changes to funding amounts, transaction status, customer identity, deployment status, Evidence Score, confidence, lifecycle, manufacturing stage, sponsor disclosure, or commercial classification must be documented.
Suggested correction format:
Correction, [date]: This entry previously stated [previous information]. It has been updated to [corrected information] based on [source or new evidence]. The Evidence Score changed from [old score] to [new score] because [component, ceiling, lifecycle, or evidence reason].
Company Responses and Right of Correction
Companies, customers, investors, researchers, and readers may submit supporting evidence or request a correction. Requests should identify the specific statement, provide a source, and explain the proposed change.
Humanoid Analytics reviews submitted evidence but does not guarantee a requested classification. Companies do not receive advance approval over independent analysis, Evidence Scores, comparisons, or editorial conclusions.
Submitting evidence, purchasing access, advertising, or sponsoring content does not create a right to favorable treatment.
Independence, Customer Relationships, and Sponsorship
Humanoid Analytics does not offer paid rankings or allow commercial relationships to determine evidence classifications.
Commercial relationships must never affect:
- Tracker inclusion
- Source selection
- Claim status
- Source tier
- Deployment level
- Lifecycle status
- Confidence
- Score components
- Score ceilings
- Final Evidence Score
- Corrections
- Missing-proof analysis
- Competitor comparisons
- Independent editorial conclusions
Required Controls
- Record material financial, advisory, sponsorship, research, data, and partnership relationships internally.
- Complete a conflict review before publishing material analysis of an active sponsor or commissioned-research subject.
- Disclose a material relationship alongside relevant public content when appropriate.
- Label sponsored content clearly at the top.
- Keep sponsored content visually and editorially separate from independent analysis and tracker classifications.
- Treat sponsor-supplied claims as first-party evidence unless independently corroborated.
- Allow sponsors to request factual corrections, but not to rewrite classifications or independent conclusions.
- Never sell favorable rankings, scores, labels, comparisons, or source treatment.
- Do not allow sponsored work to delay required corrections or customer-independent research.
Suggested disclosure format:
Disclosure: Humanoid Analytics has [relationship] with [organization]. The organization did not determine the source assessment, evidence classification, score, comparison, or editorial conclusion.
Subscriber and custom-research relationships may be confidential. Confidentiality does not remove the requirement to disclose a material conflict when public coverage would otherwise be misleading.
Use of Artificial Intelligence
Artificial intelligence may assist with:
- Source discovery
- Transcription
- Translation
- Document comparison
- Data extraction
- Entity normalization
- Duplicate detection
- Draft structuring
AI output is not evidence and is not cited as a source.
No material claim status, Evidence Score, confidence level, ceiling, financial status, or correction may be published without human review of the underlying sources.
When translation affects a material classification, the original-language source should be retained where possible. Extracted numbers, dates, names, and quotations must be checked against the source.
What We Do Not Treat as Commercial Proof
The following may be important signals, but none proves commercial readiness on its own:
- Demo videos
- Trade-show appearances
- Founder or executive interviews
- Funding rounds and high valuations
- Partnership announcements and memorandums
- Customer logos without confirmation
- Future production targets
- Factory renderings or announced capacity
- Preorders without delivery evidence
- Shipment claims without customer or operating context
- Aggregate unit claims without dates or recipients
- Generic statements about AI, autonomy, embodied intelligence, or labor replacement
- Technical benchmarks that do not reflect real operating conditions
- Sponsored claims without independent evidence
Funding can reduce financing risk. Demonstrations can show technical progress. Partnerships can create future opportunities. Preorders can indicate demand. Manufacturing investment can improve future capacity. These signals matter, but they must be described accurately and must not be presented as proof of real-world commercial adoption.
Our Editorial Standard
Humanoid Analytics is evidence-first.
We distinguish:
- Technical achievement from commercial proof
- A planned pilot from an active pilot
- An active pilot from a paid deployment
- Installed capacity from actual output
- Output from shipments
- Shipments from customer operation
- Funding from commercial traction
- Current evidence from historical achievement
- Sponsored communication from independent analysis
We preserve uncertainty when the public record does not support a stronger conclusion.
The humanoid robotics market will not be proven by videos, valuations, or announcements alone. It will be proven by robots performing useful work reliably, safely, and economically in real operating environments.