Forty-three devices and a brief at 0900
The cage behind the S6 shop holds forty-three devices. Rugged Android tablets from a 2023 unit buy. Two shelves of laptops from two different contracts with two different specs. A stack of phones a company commander expensed after an exercise and never turned in. Some run Windows. Some run Linux because a warrant officer had opinions. Two are still in shrink wrap. The mission brief is tomorrow at 0900 and the tasking says every team leader carries the mission library on a device.
The sergeant running the shop has a spreadsheet. It was accurate in March. It does not say which tablets have the storage for the imagery archive. It does not say which laptops can run analysis without throttling. So the shop does what every shop does the night before a mission. It guesses. It loads everything onto everything and hopes.
This locker is not a failure of discipline. It is what the modern edge looks like. CSIS documented how Ukraine's military went digital on whatever hardware it could field, and an officer writing at the Modern War Institute argued that squads should be free to buy and break their own gear because that is how adaptation actually happens. Bottom-up procurement wins wars. It also fills lockers with hardware nobody has scored.
Enrollment gives every device a score
EdgeLance treats enrollment as an interview. Any device walks in. Windows, Android, macOS, iOS, Linux. The agent fingerprints the operating system and the hardware underneath it. Memory, storage, compute, accelerators, battery, radios. Then it negotiates a capacity profile, which is a signed statement of what this exact device can sustain. Not what the spec sheet promised. What the interview measured.
The profile lands the device in one of three tiers. Scout tier is phone-class. It answers short-context questions, runs alerts, and holds the documents it can actually search. Operator tier is laptop-class. It carries full retrieval and analysis against the whole mission library. Command tier is server-class. It takes the video pipelines and the heavy vision work that would flatten anything smaller. Every node in the fleet wears its tier like a rank.
And this is where mission planning changes. The old question was whether the loadout would run on Guy's phone, asked out loud in the planning bay, answered by the one person who remembered what Guy carries. That question is gone. The system already interviewed Guy's phone. It is a scout node with 41 gigabytes free and it will hold the medical annex and the route imagery for its sector. The planner reads that off a screen instead of asking the room.
Packs sized to the node
A mission pack in EdgeLance is not one artifact copied everywhere. It is a loadout sized per node. The scout-tier phone gets a small model and the document set it can search at speed. The operator-tier laptop gets a larger model and the full mission library. The command-tier server gets the vision models and the video archive. Nobody ships a model to a device that cannot run it, because the sizing happens against the capacity profile before a single byte moves.
Fit gates make that a hard rule instead of a convention. When a planner assigns a loadout to a node, the gate checks the math. Model footprint against memory. Document corpus against storage. Sustained inference against the thermal profile. If the loadout does not fit, the launch blocks and the planner sees exactly which line item broke the budget. The failure happens at a desk during planning. It used to happen on the objective. This is the mission application layer doing what an application layer is for, turning hardware variety into a solved problem instead of a nightly scramble.
A bad device shows up before it breaks the mission
Enrollment is a moment. Readiness is a heartbeat. Every enrolled node reports battery health, free storage, thermal state, software versions, and security posture into a single fleet view. The S6 shop sees the whole locker as a live board instead of a stale spreadsheet.
So the tablet with the degrading battery gets flagged on Tuesday in the motor pool instead of dying Thursday on a hilltop. The laptop that missed a patch cycle shows red before it touches mission data. A device that drifts out of posture drops out of eligibility for the next pack until someone fixes it. The fleet view turns device failure from a mission event into a maintenance event, and maintenance events are cheap.
Delivery works with the network or without it
Sized packs still have to arrive. Connected fleets pull signed packages over the network. Air-gapped fleets get the same packages by USB-C courier, carried on a stick from the build enclave to the device. Either way the package verifies its signature on the device itself, installs against a rollback point, and reports success back into the fleet view when a path home exists. A failed update rolls back to the last good state instead of bricking a node the night before movement.
MDM wraps the whole lifecycle. Duress wipe if a device is taken. STIG posture enforced continuously, not audited annually. We wrote about why MDM has to go beyond Knox for exactly this reason. Fleet management that only locks a device down cannot tell you what the device can carry, and carrying capacity is the number the mission runs on.
Back to the locker. The shop starts enrolling after lunch. Tablets first, then the laptops, then the orphan phones. Each device gets interviewed, scored, tiered, and loaded with the pack that fits it. Three fail their fit gates and go on the bench with a reason attached. By dinner the sergeant is not looking at forty-three devices. She is looking at a board that shows twenty-eight scout nodes, ten operator nodes, two command nodes, and three benched, and the 0900 brief writes itself from that screen.