Lincoln

Lincoln — a governance runtime that lets autonomous weapon systems engage at machine speed while satisfying DoDD 3000.09's requirement for "appropriate levels of human judgment over the use of force." PROBLEM. Drone swarms have crossed the threshold where per-shot human authorization is operationally infeasible (Iran April 2024: $80M attack vs $1B defense; Red Sea: $1B in interceptors against $35K drones). The directive still demands transparent, auditable human judgment, but today's after-action investigations rebuild engagement records by hand over months — Tower 22 took 14 months; the USS Gettysburg blue-on-blue took nearly a year. SOLUTION. Three separately-accountable architectural layers: 1) Interpretation (pre-mission) — the commander's Rules of Engagement are parsed on-device, ambiguities surfaced for explicit resolution, and the compiled mission policy cryptographically signed. 2) Operation (engagement time) — a deterministic policy engine, with no LLM in the decision path, executes routine engagements inside the signed envelope at platform latency; exceptions route to operators. 3) Audit (continuous) — every decision is Ed25519-signed and hash-chained, traceable to the commander's authority, verifiable in ~41ms on commodity hardware without the runtime vendor's cooperation. Human judgment, applied once at compile time, scales to thousands of engagement decisions per mission.

Team

Placement

Participant