The question nobody asks at the demo
Every demo of tactical AI shows the same thing: boxes around people and vehicles, drawn in real time. Almost nobody in the room asks what license the detection model ships under. That question tends to come up much later, during accreditation, or when the program wants to share the system with an allied partner, or when a lawyer finally reads the dependency list.
Some of the most popular object detection frameworks are released under the GNU Affero General Public License, or under a commercial license sold as the alternative. The AGPL is a strong copyleft license that extends its obligations to software users interact with over a network. Whether those obligations bite in a given government system is a legal question. The fact that it is a question at all is the problem.
Why it matters more in defense
Defense programs modify software, embed it in larger systems, deploy it to thousands of devices, and share it with partners. Each of those actions is exactly what a copyleft or commercial license constrains. A program that builds around a restricted model can end up unable to release its own modifications to a coalition partner, or paying per-device fees it never budgeted, or rebuilding its detection pipeline late in the schedule.
The DoD CIO's guidance is clear that open source software is welcome and that its license terms still apply. Models are software. Their weights carry license terms just as their code does.
Coalition operations make this sharper. A program that wants to hand its detection pipeline to a partner nation has to be able to redistribute every component in it, including the weights, under terms both governments accept.
What we changed
This week EdgeLance replaced its object detection model across every service with a detector released under the Apache License 2.0. Apache 2.0 permits modification, redistribution, and commercial use, with a patent grant and no copyleft obligations. Every model in EdgeLance's default loadout now carries a permissive license.
The license of each model is recorded in the mission pack that stages it, next to its version and size, and it flows into the software bill of materials for each release. A reviewer can see what license every model on every device carries without opening a single repository.
This fits a position we have held since June, that open weights under permissive licenses are the only foundation a defense program can own outright. The license sits next to the model's provenance in the manifest that stages the mission pack, and both feed the compliance package that builds with every release.
Add one line to the approval checklist
Model approval checklists already ask about accuracy, size, and provenance. Add license terms to that list, and ask it before the model is built into anything. The best detector in the world is a liability if the program cannot ship it to the people who need it.