Lantronix UAS Research Workbench Phase 1
Build phase 1 as an internal research workbench inside OpenClaw and Mission Control. The core decision is to optimize for three consulting outputs, competitive landscape, competitive positioning with technical differentiation, and target customer segments, using a structured US-first dataset built around companies, products, customer segments, and evidence. Do not build a standalone app yet.
1. Problem Statement and Goal
Pete needs a reliable way to produce Lantronix deliverables without missing important competitors, adjacent players, products, or customer opportunities. The current UAS work has real value, but it started from an arbitrary first source set and was shaped partly by a broader product idea in UAS Strategic Intelligence Platform. That creates two problems:
- the current 125-company seed set is useful but incomplete and uneven
- the current model does not cleanly separate "track this company" from "include this company in default Lantronix reporting"
- the existing spec leans toward a future product before the internal consulting workflow is tight
The goal of phase 1 is simple: create an internal Lantronix research workbench that lets Pete produce credible, repeatable strategy outputs for Lantronix leadership, especially the SVP Engineering, VP Product, and EVP Product & Strategy, while keeping the system narrow enough to improve fast.
2. Success Metric
Phase 1 is successful when all of the following are true:
- Pete can generate the first three report types from the system: competitive landscape, competitive positioning with technical differentiation, and target customer segments.
- The system provides high-confidence coverage of the US categories that matter to Lantronix, while retaining a broader tracked UAS universe for false-negative checks and later analysis.
- Each important claim in a report can be traced to a source or evidence note.
- Pete can filter companies and products by at least segment, product type, platform domain, target customer, geography, NDAA/compliance posture, and strategic relevance.
- Before or shortly after kickoff, Pete has a credible market map and a sharp question set for Lantronix, not just a bigger raw list.
3. Current State
What exists today:
- Mission Control project:
project-uas/ UAS Strategy & Research - Existing parent task: JAM-15 UAS Strategic Intelligence Platform
- Existing research tasks: JAM-17, JAM-23, JAM-24, JAM-26, JAM-27, JAM-29
- Existing data:
data/uas-companies/all_enriched.jsonwith about 125 enriched records - Existing schema:
data/uas-companies/schema.md - Existing framing artifacts:
- UAS Strategic Intelligence Platform
- Lantronix Strategy Engagement Draft
What is missing:
- no phase-1 consulting spec tied directly to Lantronix deliverables
- no clean separation between Company and Product records
- no first-class customer segment taxonomy
- no evidence model for claim traceability
- no report templates tied to the three actual deliverables
- no US-first category coverage plan
Current task fit, blunt version:
| Task | Current fit | Recommendation |
|---|---|---|
| JAM-15 | right parent, wrong level of abstraction | keep and repoint to this phase-1 plan |
| JAM-26 | directionally useful but too XPO-centric | keep, rewrite around taxonomy + recast + targeted gap fill |
| JAM-24 | useful only if model quality blocks progress | defer or archive for now |
| JAM-27 | out of phase for US-first work | archive for now |
| JAM-29 | premature until workflow is proven | archive for now |
4. Platform Capabilities
OpenClaw and the current Mission Control setup already support most of what phase 1 needs:
- structured local files for the system of record
- artifact creation and review flow through Mission Control
- task tracking for scoped execution
- scripted transforms and enrichment helpers inside the workspace
- subagent orchestration for batch research and data enrichment
- browser and web tools for source collection when needed
- cron support later if periodic refresh becomes worth automating
What OpenClaw does not require for phase 1:
- a new external-facing application
- user auth for outside stakeholders
- polished multi-user dashboards
- real-time ingestion
- product-grade uptime, API design, or customer support surfaces
That is why OpenClaw and Mission Control are the right substrate for phase 1. The work is still analyst-driven, source-heavy, and evolving.
5. Community Patterns
The proven pattern for early market-intelligence systems is internal-first: structured records, analyst judgment, human-in-the-loop updates, and templated outputs. Teams often start with flexible systems like Airtable, Notion databases, or internal research stacks before they earn the cost and rigidity of a dedicated product. Closed research products like AlphaSense are useful benchmarks for output quality, but they are the wrong build target for phase 1 because the real need here is custom industry structure and consulting leverage, not a general-purpose market-intel product.
Within the OpenClaw world, the closest proven pattern is internal skill-driven workflow plus artifact delivery, not a standalone app. ClawHub and the current workspace setup both point toward narrow internal workflows first.
6. Options
| Option | Description | Complexity | Token Cost | Reliability | Maintenance burden | Verdict |
|---|---|---|---|---|---|---|
| A. Standalone app now | Build a dedicated Lantronix/UAS app with its own data model, UI, and workflow | High | High | Medium | High | Too early |
| B. Internal research workbench in OpenClaw/Mission Control | Use local data files, artifacts, light internal views, and targeted workflow automation | Medium | Medium | High | Medium | Best phase-1 path |
| C. Spreadsheet-only workflow | Keep this as Sheets plus notes with light manual synthesis | Low | Low | Medium | Medium-high human overhead | Fine as fallback, weaker for scale and traceability |
Option A: Standalone app now
Pros:
- clear product surface
- cleaner long-term separation if this later becomes software
Cons:
- forces premature choices on auth, UX, sync, reliability, and architecture
- distracts from taxonomy, evidence, and report quality
- increases build work before Lantronix questions are fully known
Option B: Internal research workbench in OpenClaw/Mission Control
Pros:
- fastest path to useful deliverables
- keeps data, tasks, artifacts, and synthesis in one operating environment
- easier to reshape once kickoff clarifies product plans, customers, and buying context
- supports human judgment and source traceability
Cons:
- less polished than a dedicated app
- some filtering or record views may need light custom work later
Option C: Spreadsheet-only workflow
Pros:
- fast to start
- familiar
Cons:
- weak evidence tracking
- weak report reuse
- product-level positioning will get messy fast
- harder to turn into repeatable consulting workflow
7. Recommendation
Use Option B: an internal research workbench inside OpenClaw and Mission Control.
Key decisions:
- US first. Do not expand to Europe in phase 1.
- Track broadly, report selectively. Keep adjacent or questionable-fit UAS companies in the dataset so Pete can spot-check false negatives, but default Lantronix reports should emphasize the subset marked as Lantronix-relevant.
- Company and Product are both first-class records. Company-only will get sloppy once the work shifts into technical differentiation.
- Customer Segment is a structured taxonomy. Customer profiling must support buyer personas, segmentation frameworks, and jobs-to-be-done, not just loose notes.
- Evidence is first-class. Source quality matters because these reports must hold up in front of leadership.
- NDAA/compliance is a core field. It is especially important for defense-sensitive positioning and supplier credibility.
- Outputs drive schema. If a field does not help the three report types or the kickoff preparation, it is lower priority.
This is the right level of ambition. It gets Pete a useful system fast and leaves room to widen later if the Lantronix engagement proves it deserves more.
8. Security Considerations
- Keep the system internal to Pete's consulting workflow. No client-facing app in phase 1.
- Do not auto-share outputs externally. Pete should review artifacts before anything leaves the workspace.
- Public-source claims should be linked to evidence. Notes from 1:1 industry conversations should be summarized as analyst notes, not dumped as raw transcripts.
- Do not over-collect sensitive defense or contract data beyond what is appropriate from public sources and Pete's own conversations.
- Separate verified facts from inferred positioning. The system should not blur them.
- If enrichment workflows fail or drift, fallback should be manual review, not silent bad data.
9. Implementation Scope
What David should build after approval:
Data model
Create or migrate to a phase-1 data structure with these first-class record types:
- Company
- Product
- Customer Segment
- Evidence / Source
- Report Artifact
Minimum fields
Company
- Name
- Website
- Headquarters / geography
- Segment
- Product types
- Platform domains
- Target customers
- Concerns Lantronix (Boolean flag)
- Key use cases
- Channel model
- Revenue band
- Funding/public status
- NDAA/compliance status
- Strategic relevance to Lantronix
- Evidence confidence
Product
- Company
- Product name
- Product class
- Technical positioning summary
- Compute profile
- Integration profile
- Deployment profile
- Trust/compliance profile
- Commercialization profile
- Strategic notes
Customer Segment
- Segment name
- Vertical
- Buyer persona
- JTBD
- Buying criteria
- Sensitivity to NDAA/supply chain/security
- Strategic fit for Lantronix
Evidence / Source
- URL or note source
- Source type
- Captured date
- Confidence
- Applies to which company/product/segment fields
Workflow scope
- reclassify the existing 125 records against the new taxonomy
- identify category gaps before adding many more companies
- keep broader UAS companies in the dataset even when they miss current Lantronix-fit criteria, then use the simplified relevance flag for default reporting
- add targeted sources to fill missing categories, missing competitors, and missing customer segments
- produce three report templates tied to the engagement
- support lightweight filtering for internal use
- support periodic updates later, but do not build real-time ingestion now
Task restructuring proposal
After Pete reviews this spec:
- Keep JAM-15 as the parent phase-1 task and update it to point here
- Rewrite JAM-26 as phase-1 taxonomy, recast, and targeted gap-fill
- Archive JAM-24 unless model quality becomes a real blocker
- Archive JAM-27 because Europe is out of scope for phase 1
- Archive JAM-29 until the workflow is stable enough to deserve a reusable skill
- create fresh execution tasks only after the taxonomy and report templates are approved
10. Validation Criteria
The build is good enough for phase 1 when these tests pass:
- Recast test: the existing 125-company set can be reclassified into the new taxonomy without major field ambiguity on the important categories.
- Gap test: the system can show which competitor classes, product classes, and customer segment classes are undercovered.
- Filter test: Pete can filter and sort the system by core fields needed for the first three report types, using the simplified relevance flag for default reporting.
- Traceability test: each important positioning claim in a draft report points to at least one evidence item.
- Report test: Pete can generate first-draft versions of the three target report types from the system.
- Kickoff-prep test: the system helps Pete ask better Lantronix questions before it tries to answer everything.
11. Category
Skill
This is a multi-step internal workflow for building, maintaining, and using a structured consulting research system.
12. Context Loading
When this workflow is active, load the following context:
Always load for Lantronix UAS strategy work
/Users/vinny/.openclaw/workspace/artifacts/spec_lantronix_uas_research_workbench_phase1.md/Users/vinny/.openclaw/workspace/mission-control/data/tasks.json/Users/vinny/.openclaw/workspace/mission-control/data/projects.json
Load for current dataset and taxonomy work
/Users/vinny/.openclaw/workspace/data/uas-companies/schema.md/Users/vinny/.openclaw/workspace/data/uas-companies/all_enriched.json- any new phase-1 schema/data files created for the Lantronix workbench
Load when historical framing is useful
/Users/vinny/.openclaw/workspace/artifacts/spec_uas_intelligence_platform.md/Users/vinny/.openclaw/workspace/artifacts/lantronix_strategy_engagement_draft.md
Trigger conditions
- Pete asks for Lantronix research planning
- Pete asks for UAS market structure, competitors, positioning, or customer segmentation
- Pete asks to evolve the UAS dataset, taxonomy, or report workflow
13. Guardrails
- Do not build a standalone app in phase 1.
- Do not expand to Europe or global scope before US category coverage is strong.
- Do not add companies blindly by source list size alone. Expand by missing category, missing competitor class, or missing customer segment.
- Do not drop a company from the dataset just because it misses current Lantronix reporting criteria. Use the relevance flag to exclude it from default reports while keeping it in the tracked universe.
- Do not make company-only the system model. Product records are required for technical positioning.
- Do not treat unverified enrichment output as fact.
- Do not auto-send Lantronix-facing deliverables without Pete review.
- Do not optimize for frequent refresh until the core taxonomy and outputs are stable.
- Do not let this turn into a collector project. Report usefulness beats record count.
14. Handoff
Deliver this plan to Pete as a Mission Control artifact using the Tailscale artifact URL:
http://vinnys-mac-mini.tail31784c.ts.net:3100/artifacts/spec_lantronix_uas_research_workbench_phase1
After Pete reviews the artifact:
- update JAM-15 to link to this artifact as the active spec
- move JAM-15 to
needs-review - keep assignee on Pete
- after approval, rewrite or archive the stale UAS backlog tasks before any build work starts