research artifact

Lantronix Phase 1 Hardware-First Reanalysis

2026-04-27

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:

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

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

Lower-level or embedded-software exception examples

Borderline Cases That Still Need Pete's Judgment

  1. Flyhound
  1. Technology Service Corporation
  1. General Dynamics Mission Systems
  1. Ghost Robotics and Saronic
  1. Fathom Manufacturing and WindShape

Files Updated

Logic and rule docs

Company records changed

Validation Checks

Direct record spot-checks

Validated directly in the source records after the record updates:

Count reconciliation

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

Result:

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.