For the people who
show up after.
USAR teams in a collapsed parking deck. SAR pulling a kid off a mountain at dusk. Swiftwater anchoring in flash flood. We’re building a machine that gets to the void first — so a human doesn’t have to.
Rescue concept of operations
You’re trained to enter the void. Most of the world isn’t.
The rescue technician we’re designing for is the one rigging a high-angle anchor over a mineshaft, breaching a wall with a chipping hammer, or wading into a river that just took out a bridge upstream. Hours into an op. Equipment heavy. Margin thin.
Your team has the rigging, the medical, the structural. The cost is your body — in the rubble pile, on the rope, in the water. Every void you enter is a coin flip with secondary collapse, hypothermia, anchor failure.
Vertex is building for the moment your team needs eyes and hands in a place a human shouldn’t have to go first.
- Secondary collapse during void search. A wall pancakes onto the rescuer who’s twelve feet in. Standard mitigations are training and luck.
- Patient location ambiguity. A “trapped child” report turns into eighteen hours of breaching the wrong wall.
- Cold-water immersion. Body temperature drops in minutes. Decision-making degrades faster than you notice.
- Wilderness search grid drift. The grid you laid at first light is wrong by sunset. Wind, exhaustion, terrain.
- Confined-space atmospheric monitoring. Oxygen, CO, H₂S, LEL. Four-gas meter is on your harness. You’re reading it less than you should.
- Rope-team cognitive load. Twenty feet of rope, four anchors, two patients. The rigger is also doing the math on the descent.
Vertex is designing toward a rescue policy for confined-space, vertical, and aquatic environments. The target system would enter first, build the map, and either hold the void or support extraction under doctrine and authority set at the command post.
rescue_first vs tag_and_hold selectable.Every action the policy takes on a rescue scene cites real, published standards — same framework as our reconnaissance and ICU scenarios in Colosseum.
This is the trace schema we are designing toward—not a deployment record or live-model trajectory. Values below illustrate how sensor state, proposed action, and doctrine citation would remain together.
We intend to build with rescue teams through approved rubble-pile training, structural-collapse drills, and rope-rigging review. Those activities are a proposed co-design program, not a current deployment claim.
If your team trains regularly and wants to host a Vertex field day, tell us.
Build it with us.
Rubble-pile drills, confined-space integration, swiftwater training co-design, and long-term model-card collaboration on rescue decisions.