SALT19 is opening conversations with qualified operators, enterprises, public-sector teams and strategic partners that can evaluate defined workflows under explicit success criteria. A pilot is not a logo exercise. It should answer whether a system saves time, improves evidence quality, integrates cleanly, earns repeat use and fits a real buying process.
SALT19 does not present every system as production-ready. Pilot scope should match what the current software can actually support.
UAS flight intelligence, mission context, weather/GNSS/space-weather signals, cooperative traffic awareness, planning and FAA SWIM integration.
Machine-discoverable technical utilities, MCP access, x402 payment gating, fresh-state primitives, structured outputs and verification-oriented receipts.
Local-first photogrammetry and geospatial production aimed at generating operational mapping deliverables without requiring customer imagery to leave the workstation.
Android edge-C2, local perception, persistent visual tracking, resilient localization, governed control paths, federation and companion telemetry.
Governed cognitive architecture for persistent reasoning, memory, planning, capability composition, execution authority, verification and experience retention.
Local AI-assisted software engineering with workspace authority levels, reviewable changes and explicit control boundaries.
Can the system close a real job-to-be-done without forcing the operator into artificial demo behavior?
Measure operator time, workflow steps, manual interventions and integration burden against the current baseline.
Track failure modes, retries, evidence completeness, result quality and where human review remains essential.
Determine whether qualified users return, would deploy again, and can identify a plausible budget owner and procurement path.
SALT19 will prioritize pilot conversations where success criteria, technical access, operational constraints and the path from evaluation to adoption can be made explicit.