L19 / Platform / Mission Discovery
MD · 02 · Mission Discovery Engagement 14 days · fixed scope

14 days to a mission you can run.

A technology-driven 2-week sprint that maps your sensors, quantifies your noise, and finds your blind spots — and produces a pilot plan with KPIs ready for execution. Powered by L19 Discovery Intelligence and the same MESH OS models that run live border, perimeter, ISR and counter-UAS operations.

14 days · fixed Sensor & workflow audit Noise quantified Decision-gap analysis Pilot plan + KPIs
Duration
14days
Fixed sprint. Kickoff Monday → read-out Friday wk 2.
Use cases
3–5
Highest-impact mission workflows surfaced and scored.
Output
30–90d
Pilot plan with KPIs, scope, and execution path.
▶ MD · 02 · Outputs

Four artifacts. One execution-ready mission plan.

Every Mission Discovery engagement produces the same four artifacts — quantified, validated, and signed off by both your operators and your sponsor. Not a deck. Not a pitch. A plan you can run.

O · 01 · Sensor & asset map

What you have, where it is, what it sees.

Every sensor, camera, radar, drone, gateway and operator station — geolocated, classified by capability, and assessed for coverage. Gaps and overlaps quantified, not described.

Sensor inventoryCoverage mapsCapability matrix
O · 02 · Noise & decision-gap report

Where alerts go to die — and why.

Operator workflows traced end-to-end. False-positive rate, time-to-decision, and dropped events measured against doctrine. Every bottleneck named, ranked, and tied to a workflow.

Noise %TTD baselineBottleneck index
O · 03 · Mission use-case scoring

3–5 highest-impact opportunities, ranked.

Use cases mapped to MESH OS capability domains (Perception · Command · Agentic · Edge), scored on operational impact, technical readiness and time-to-value. The ones worth running. The ones to defer.

Impact scoreReadiness scoreCapability map
O · 04 · Pilot plan & KPIs

30–90 day execution path with measurable success criteria.

For the top use case: deployment topology, integration list, operator training plan, KPIs, success thresholds and exit criteria. Ready to scope, fund and run.

Pilot scopeKPI frameworkExit criteria
▶ MD · 02 · 14-day program

Three phases. Two weeks. One execution plan.

A repeatable, technology-driven sprint built on validated operational frameworks. The same Discovery Intelligence engine that scopes our live deployments runs yours.

Phase 01
Days 01 → 04 · SENSE

Audit the operational reality.

On-site or remote. Operator interviews, after-action reviews, sensor walk-down, integration probing. We map what's deployed, what's used, and what's ignored.

  • Mission & doctrine kickoff
  • Sensor & asset inventory
  • Operator workflow shadowing
  • Telemetry & noise baseline
Phase 02
Days 05 → 09 · SCORE

Quantify the gaps. Rank the opportunities.

Discovery Intelligence runs the analysis. Decision gaps are quantified, not estimated. Use cases are scored against MESH OS capability domains and operational doctrine.

  • Decision-gap analysis
  • Use-case ideation & scoring
  • Capability mapping (P · C · A · E)
  • Operational sensitivity model
Phase 03
Days 10 → 14 · SHAPE

Build the pilot. Get sign-off.

Top use case becomes a 30–90 day pilot plan. KPIs defined with operators. Success thresholds set. Roadmap presented to sponsor and operations leadership for sign-off.

  • Pilot scope & topology
  • KPI & success framework
  • Sponsor + operator read-out
  • Build-ready handoff package
▶ MD · 02 · Engagement tiers

Scoped to your operational footprint.

Three fixed scopes. Same 14-day cadence. Same artifacts. Different operational complexity.

Tier 01 · Single Site
Site Discovery
One operational site or zone
14 days · fixed
  • One physical site or defined zone (≤5 km²)
  • Up to 25 sensors / assets in scope
  • 3–5 use cases scored
  • 1 pilot plan, 30–90 day horizon
  • Sponsor + operator read-out
Discuss scope
Tier 03 · Enterprise / Force
Force Discovery
National, force-level or programmatic
14 days · phased extensions
  • National-scale or force-wide programmes
  • Multi-domain (border · perimeter · CUAS · ISR)
  • Doctrine alignment workshops
  • Programme-level capability map
  • Multi-pilot roadmap with phasing
  • Sovereign-deploy considerations
Discuss scope
▶ MD · 02 · Mission types

Mission Discovery has been run across six operational classes.

▶ Class 01
Border & coastal

Wide-area surveillance, illicit crossing, smuggling routes, maritime approach.

▶ Class 02
Perimeter & critical infrastructure

Energy, transport, government, industrial. Intrusion, anomaly, asset protection.

▶ Class 03
Counter-UAS

Drone detection, classification, tracking and authorized response.

▶ Class 04
ISR & tactical

Forward-deployed, edge-first ISR. Degraded ops. Sovereign environments.

▶ Class 05
Wildlife & conservation

Anti-poaching, fire detection, wide-area habitat monitoring.

▶ Class 06
Operations & civic

Stadiums, transit, large-event command. Crowd, flow, anomaly.

▶ MD · 02 · Begin discovery

Two weeks. A mission you can run. Then a deployment that ships.

Mission Discovery is built for defense, security, and critical-infrastructure leaders who need to know — before they buy, build, or scale — what AI automation actually does to their operational reality.