01
Implemented
The product path exists in the current software and can be inspected in an EdgeLance-controlled environment.
Evidence ledger
Proof without implication.
EdgeLance names the environment, data, demonstrated behavior, and boundary behind every public proof. Software evidence does not silently become hardware, field, accreditation, or customer evidence.
Evidence vocabulary
A claim advances only when its evidence does.
02
Software tested
Automated or repeatable local tests exercise the claimed behavior and its failure boundaries.
03
Simulator demonstrated
The current interface or contract has been exercised in a named simulator with synthetic demonstration data.
04
Hardware verified
The path has retained evidence from the named physical device, sensor, radio, or compute target.
05
Field exercised
The capability has retained evidence from an operationally representative field event. This is not implied by software or simulator proof.
Public product records
What the current captures actually establish.
Each record states the proof and the line it does not cross.
Software tested
Collaborative mission planning
- Environment
- Local web application
- Data
- Synthetic Operation Northstar
- Establishes
- Planning room, reusable mission objects, source status, staff workflow, map, COA comparison, order, execution, sync, and review surfaces.
- Does not establish
- The capture does not imply government acceptance, classified-data approval, or operational deployment.
Simulator demonstrated
Native mission and readiness
- Environment
- iOS 26.2 / Release / iPhone 17 Pro simulator
- Data
- Synthetic Relay operator
- Establishes
- Native operator readiness, private local signals, explicit check-in, medic contact, mission surface, link state, and common operating picture.
- Does not establish
- Simulator evidence is not physical-device acceptance, HealthKit clinical validation, or field exercise evidence.
Recorded demonstration
Vision mission record
- Environment
- Packaged local replay
- Data
- Recorded Cologne demonstration footage
- Establishes
- Person detection, persistent track IDs, re-identification, OCR, multilingual audio, timestamped events, and mission-record binding.
- Does not establish
- A packaged replay demonstrates the product workflow; it is not a live deployed camera system or an independent accuracy benchmark.
Implemented
Mission playback and review
- Environment
- Local mission workspace
- Data
- Synthetic Warhacker mission
- Establishes
- Decision timeline, linked evidence, event sources, playback controls, after-action workflow, and review context.
- Does not establish
- The product capture does not establish customer acceptance or accreditation of the complete deployment environment.
Integration maturity
Connect upward. Never hide the dependency.
A software seam is not described as a validated partner endpoint, and protocol simulation is not described as physical hardware acceptance.
TAK ecosystem
Software adapter
CoT projection and package paths
PEAT
Software verified
Governed peer-to-peer replication
MISB ST 0601
Codec verified
ISR metadata and evidence binding
GeoPackage / KML
Software verified
Governed disconnected map exchange
USB-C courier
Software verified
Signed and sealed disconnected delivery
Lattice
Endpoint pending
Entity and task exchange seam
Palantir
Endpoint pending
Ontology and evidence export seam
MAVLink 2
Hardware pending
Signed read-only UxV telemetry
MANET / Starlink
Hardware pending
Bearer telemetry and route awareness
Bring the acceptance standard.
We will map the mission thread, evidence already available, hardware and partner dependencies, and the work required to reach the next state.
Request evidence review