For the people who go
down range.
Reconnaissance squads, line medics, EOD, route-clearance teams. We’re building a machine that reads doctrine, takes the riskiest part of the task, and stays under soldier supervision — auditable to the rule.
You don’t need a slide deck. You need a robot that can cite the manual.
The soldier we’re designing for is the squad leader on a recon patrol, the line medic running TCCC under fire, the route-clearance team rolling at 4 km/h hoping the next culvert isn’t the one. You’re trained against doctrine that fills hundreds of pages of ATP. You execute it. You teach it.
The cost is your team’s body. Every danger area you cross, every kill zone you skirt, every casualty you load. The doctrine exists because the cost is high.
Vertex builds for the moment a machine can take the entry, the route check, or the casualty drag — cite the rule it followed, and leave the lethal authority with you.
- Kill-zone entries on covered routes. Doctrine is clear. Terrain doesn’t always agree. Crossing the wrong wadi costs the team.
- IED-rich routes. The pattern is statistical; the death isn’t. A robot that can lead the column at 4 km/h does math humans shouldn’t.
- CASEVAC time-to-surgery. Golden window vs ground-evac reality. Distance is fixed; load time isn’t.
- Civilian-presumption failures. The default-civilian rule under uncertainty. ROE-graded. Doctrine-required. Hard.
- Recon footprint discipline. Detection windows on observation posts — the team that’s observed is the team that’s no longer reconnoitering.
- Doctrine drift under fatigue. The 16th hour of a patrol. The 4am QRF tasking. Training holds. Up to a point.
Vertex’s tactical policy is the original domain in Colosseum. The v0.0.4 library now carries 16 reconnaissance rules and a larger scenario set; the published model study uses the original six recon scenarios. Every scored action remains linked to the authority it cited.
Every action the policy takes cites published US Army or DoD authority. The same provenance system is used by Colosseum: rules are GROUNDED or APPLIED_BY_ANALOGY. The schema supports NOT_GROUNDED, but v0.0.4 ships none.
This is what the mission log actually looks like — sensor values, the action, and the cited doctrine line under every step. From the live demo, verbatim:
We don’t build for soldiers. We build with soldiers. Field days, exercise integration, doctrine review sessions with serving and retired NCOs. Every claim our model makes about its training is one we can show evidence for, on request.
If your unit, program office, or training command wants a longer conversation about doctrine-grounded autonomy, tell us.
Doctrine-grounded autonomy.
Training-center integration, exercise support, model-card collaboration, and program-office briefings. Every claim cited. Every action auditable.