Lantronix Company Relevance Model

Executive Summary

The Phase 1 workbench now uses a hardware-first relevance rule for concerns_lantronix.

The goal is to keep the broader UAS universe intact while making default Lantronix-facing views materially cleaner. Pure-play application software companies are no longer Lantronix-relevant by default. Hardware-related companies remain relevant. A narrow software exception remains for lower-level, embedded, autonomy, navigation, and autopilot-like software that sits close to the aircraft or mission system layer.

Relevance Model Definition

We use a single primary field on the company record to control default inclusion:

Field Semantics

• concerns_lantronix:
• true: Included in default Phase 1 Lantronix analysis because the company is hardware-related, or qualifies under the lower-level software exception.
• false: Excluded from default Lantronix views, but retained in the database for market context, benchmark review, and false-negative checks.

Hardware-First Rule

A company should be marked concerns_lantronix: true when all of the following hold:

1. US-first framing still applies: the company is US-based.
2. Target-vertical framing still applies: the company touches at least one of these verticals:

• Defense & Military
• Public Safety
• Infrastructure Inspection
• Energy & Utilities
• Agriculture

1. The company is hardware-relevant, using one of these paths:

• Direct hardware role: manufacturer or component supplier.
• Hardware-integrator role: integrator with clear hardware, sensing, avionics, datalink, payload, propulsion, rugged compute, or counter-UAS system signals.
• Lower-level software exception: software that is closer to embedded autonomy, autopilot, navigation, flight control, datalinks, or aircraft/payload sensing, not application workflow software.

A company should be marked concerns_lantronix: false when it is primarily:

• application-layer workflow software
• cloud analytics or mapping software
• public-safety operations software
• weather/risk analytics software
• consulting, training, or generic services without a hardware-adjacent product layer

Practical Interpretation

Count as Lantronix-relevant

• Drone OEMs and airframe manufacturers
• component suppliers
• avionics, sensing, navigation, RF, propulsion, ruggedization, and embedded-compute players
• lower-level autonomy and aircraft-adjacent software such as autopilot, navigation, or mission-assurance systems

Do not count as Lantronix-relevant by default

• pure-play DFR and fleet-ops software
• pure mapping and photogrammetry platforms
• workflow and analytics layers that sit above the aircraft stack
• non-hardware consulting or service firms

Pilot Mapping Changes Under v2

The questioned pilot cases now resolve as follows:

• Remain true: Silvus, Doodle Labs, Echodyne, Near Earth Autonomy, Parallel Flight, Hoverfly, Skyfish, Point One Navigation
• Flip from true to false: DroneSense by Versaterm
• Flip from false to true: Northwest UAV, Honeywell, Kratos Unmanned Aerial Systems

Classification Logic Reference

The source-of-truth script is:

• /Users/vinny/.openclaw/workspace/scripts/lantronix_broader_migrate.py

The current logic label is:

• heuristic-v2-hardware-first-us

Future Scoring Integration

This boolean remains the coarse filter. More nuanced scoring can still sit above it in later phases.

• Filter Step: concerns_lantronix == true
• Rank Step: strategic relevance, technical differentiation, NDAA posture, segment fit, and evidence quality