Mission Control

Artifacts

K
← Back to artifacts

Lantronix Phase 1 Hardware-First Reanalysis

Research ArtifactApprovedCreated Apr 27, 20264 min readFull screen ↗

Lantronix Phase 1 Hardware-First Reanalysis

Recommendation

Use heuristic-v2-hardware-first-us as the default concerns_lantronix rule.

This rule keeps the US-first and target-vertical framing from Phase 1, but changes the relevance gate to match Pete's new standard:

  • pure-play application software is out
  • hardware-related companies are in
  • a narrow lower-level software exception remains for embedded, autopilot, navigation, datalink, autonomy, and payload-adjacent system software

Rule Change Summary

Old behavior

The previous rule was broad enough to pull in many US software and integrator records as long as they touched the target verticals.

New behavior

A company is concerns_lantronix: true only when it is:

  1. US-based
  2. active in at least one target vertical: Defense & Military, Public Safety, Infrastructure Inspection, Energy & Utilities, or Agriculture
  3. hardware-related through a manufacturer or component-supplier role, or through a hardware-heavy integrator role, or through the narrow lower-level software exception

Before / After Counts

  • Total companies reviewed: 125
  • concerns_lantronix: true before: 60
  • concerns_lantronix: true after: 55
  • Net change: -5

Flipped from true to false

These were previously included by the broad v1 rule, but are now excluded because they are application-layer software or non-hardware service/integration plays:

  1. DroneSense by Versaterm
  2. KBR
  3. RIIS, LLC.
  4. Zephyrs Ai, Inc
  5. TruWeather Solutions
  6. DroneDeploy
  7. Kespry
  8. PrecisionHawk

Flipped from false to true

These were false under the prior pilot overrides, but now qualify cleanly under the hardware-first rule:

  1. Honeywell
  2. Northwest UAV
  3. Kratos Unmanned Aerial Systems, Inc.

Retained true Because They Still Fit the New Rule

  • Skydio
  • AeroVironment
  • Silvus Technologies
  • Echodyne
  • Doodle Labs
  • Hoverfly Technologies
  • Parallel Flight Technologies
  • Skyfish
  • Markforged
  • Maxtena
  • Amprius Technologies
  • Antcom Corporation
  • Glenair, Inc.
  • DeltaHawk Engines
  • Regal Rexnord Aerospace & Defense Solutions
  • Event 38 Unmanned Systems
  • Sentera
  • Inspired Flight
  • Watts Innovations
  • Censys Technologies
  • Zipline

Lower-level or embedded-software exception examples

  • Near Earth Autonomy, autonomy and hazard-avoidance stack close to the aircraft layer
  • Point One Navigation, precision RTK/GNSS positioning layer
  • Flyhound, payload-adjacent signal-triangulation system mounted to the aircraft
  • General Dynamics Mission Systems, defense datalink / C-UAS / embedded mission-systems case
  • Technology Service Corporation, sensor-systems / C-UAS integrator case

Borderline Cases That Still Need Pete's Judgment

  1. Flyhound
  • Kept true here because the offering reads closer to payload-adjacent sensing and signal processing than to workflow software.
  • If Pete wants the exception narrowed to only autopilot and navigation, this could move to false.
  1. Technology Service Corporation
  • Kept true because the record points to sensor systems and C-UAS hardware-heavy integration.
  • If Pete wants to exclude more defense integrators without a cleaner product layer, revisit it.
  1. General Dynamics Mission Systems
  • Kept true because the record includes datalink encryption and C-UAS system relevance.
  • Same caveat as TSC: this is a hardware-adjacent mission-systems call, not a pure OEM/component-supplier call.
  1. Ghost Robotics and Saronic
  • Both remain hardware-relevant under the broader uncrewed framing, but they are not clean aerial-UAS examples.
  • Keep them if Pete wants broad mission-systems adjacency. Revisit if he wants a stricter aerial-only subset.
  1. Fathom Manufacturing and WindShape
  • Still false under the current category framing.
  • They are hardware-adjacent enough to revisit later if Lantronix wants a wider manufacturing-and-test supplier map.

Files Updated

Logic and rule docs

  • /Users/vinny/.openclaw/workspace/scripts/lantronix_broader_migrate.py
  • /Users/vinny/.openclaw/workspace/artifacts/lantronix_phase1_company_filter_model.md
  • /Users/vinny/.openclaw/workspace/artifacts/lantronix_phase1_category_gap_map.md
  • /Users/vinny/.openclaw/workspace/artifacts/lantronix_phase1_internal_report_layer_v1.md
  • /Users/vinny/.openclaw/workspace/artifacts/lantronix_phase1_hardware_first_reanalysis_2026-04-27.md

Company records changed

  • /Users/vinny/.openclaw/workspace/data/lantronix-uas-workbench-phase1/records/companies/company-dronesense-by-versaterm.json
  • /Users/vinny/.openclaw/workspace/data/lantronix-uas-workbench-phase1/records/companies/company-kbr.json
  • /Users/vinny/.openclaw/workspace/data/lantronix-uas-workbench-phase1/records/companies/company-riis-llc.json
  • /Users/vinny/.openclaw/workspace/data/lantronix-uas-workbench-phase1/records/companies/company-zephyrs-ai-inc.json
  • /Users/vinny/.openclaw/workspace/data/lantronix-uas-workbench-phase1/records/companies/company-truweather-solutions.json
  • /Users/vinny/.openclaw/workspace/data/lantronix-uas-workbench-phase1/records/companies/company-dronedeploy.json
  • /Users/vinny/.openclaw/workspace/data/lantronix-uas-workbench-phase1/records/companies/company-kespry.json
  • /Users/vinny/.openclaw/workspace/data/lantronix-uas-workbench-phase1/records/companies/company-precisionhawk.json
  • /Users/vinny/.openclaw/workspace/data/lantronix-uas-workbench-phase1/records/companies/company-honeywell.json
  • /Users/vinny/.openclaw/workspace/data/lantronix-uas-workbench-phase1/records/companies/company-northwest-uav.json
  • /Users/vinny/.openclaw/workspace/data/lantronix-uas-workbench-phase1/records/companies/company-kratos-unmanned-aerial-systems-inc.json

Validation Checks

Direct record spot-checks

Validated directly in the source records after the record updates:

  • company:dronesense-by-versaterm -> concerns_lantronix: false
  • company:kbr -> concerns_lantronix: false
  • company:riis-llc -> concerns_lantronix: false
  • company:honeywell -> concerns_lantronix: true
  • company:northwest-uav -> concerns_lantronix: true
  • company:kratos-unmanned-aerial-systems-inc -> concerns_lantronix: true

Count reconciliation

The reanalysis uses the prior Phase 1 baseline of 60 true records and applies:

  • 8 flips from true to false
  • 3 flips from false to true

Result:

  • 60 - 8 + 3 = 55

Execution note

A direct script rerun was prepared in scripts/lantronix_broader_migrate.py, but I could not execute it from this subagent because exec approval was required and Discord chat approvals were unavailable in this session. The changed records above were updated directly, and the counts were reconciled against the documented 60-company baseline.

Confidence

Confidence: medium-high.

The core rule change is clear and applied consistently. The remaining uncertainty is not about pure application software, those calls are straightforward. The uncertainty is concentrated in a small set of integrator-heavy and payload-adjacent records that Pete may want to tighten further.