One force.
One chain of custody.
Every link signed.
Officers verified before the first shift, weapons accountable from issue to return, vehicles tracked to the fix, patrols that never settle into a pattern. One command picture carries the whole chain — erasable on demand, audit-logged by design.
ORBAT WATCH
MEDEVAC
Officers, armoury, patrols and fleet — one register.
A verified person, an accountable weapon, a tracked vehicle, and a patrol that never settles into a pattern — Force holds them as one register, not four. Every state transition is a recorded, attributable fact, so the officer on shift, the weapon in their hands, the vehicle under them and the route they run all resolve to the same command picture. The four surfaces below are entry points into that single record.
VERIFIED PERSON
VETTED
Officers
Verified before the first shift.
IDENTITY
national register · livenessPSIRA
grade + status · verified-atCOMPETENCY
per weapon type · to expiry/force/officers
→ACCOUNTABLE WEAPON
CUSTODY CLEAN
Armoury
Issue it, configure it, account for it.
CUSTODY
issue → return · signedWEAPON
base + kit · one state eachHORIZONS
FCA licence · SANS storage/force/armoury
→UNPREDICTABLE PATROL
RUNS ACTIVE
Patrols
Plan against readiness, patrol without a pattern.
ROUTE
fresh variant · no repeatCORRIDOR
geofence · edge-triggeredCHECKPOINT
dwell + check-in/force/patrols
→TRACKED VEHICLE
REPORTING
Fleet
Every vehicle registered, fitted, reporting.
REGISTER
VIN · plate · verifiedTELEMETRY
OBD2 · CAN · position + healthREADINESS
GSORTS · operator-set/force/fleet
→One console, four registers.
Officers, armoury, fleet and patrols are separate pages here because each deserves the depth — but an operator runs them from one console. Switching tabs below is what switching capability actually looks like: the officer roster and custody ledger read as registers, the fleet and patrol tabs carry the same live map each deep page runs.
Units carry affiliation and echelon as first-class symbology.
Every organisational asset is a Unit: a tracker-bearing entity that owns its credential, positions and telemetry. On creation it carries a 2525D affiliation — friend by default for blue force — and an optional APP-6(D) echelon, so a roster reads as a real order of battle rather than a flat device list. Persons belong to a home unit and surface on the picture only as its crew.
- 01
2525D affiliation — Friend / Assumed Friend / Suspect / Hostile / Unknown / Neutral — rendered as the map frame plus a paired word.
- 02
APP-6(D) echelon is optional and can be updated on its own, without disturbing anything else about the unit.
- 03
Each unit holds its own protected credential; a tracker authenticates as exactly one unit and locates only that unit.
- 04
Affiliation firewall: a unit holding crewed persons can never be flipped away from friendly — the change is refused outright, not flagged after the fact.
2525D AFFILIATION · FRAME + PAIRED WORD
APP-6(D) ECHELON · TEAM → COMPANY
FIREWALL
A unit crewing persons refuses any non-friendly change outright — enforced up front, never as a late check.
ACTIVE UNITS
ECHELON DEPTH
FRIENDLY AFFILIATION
CALLSIGN COLLISIONS
Liveness is derived; readiness is commanded.
The platform keeps two semantic axes on two distinct visual channels per unit row and refuses to fold them. Liveness is a status dot driven by derived state over the tracker telemetry; readiness is a separate badge carrying the operator-set GSORTS vocabulary. A jammed live signal is not a partial-mission-capable assessment, and a low-battery tracker never silently maps to a degraded combat platform. This is the state model every Force entity hangs on — officer, weapon, vehicle, patrol and unit all carry the same two axes.
BLUE-FORCE · 7/7 LIVE
FIX AGE 0:08
- 01
A clear liveness picture that escalates from nominal through stale, offline and low-battery to jammed, man-down and panic.
- 02
GSORTS readiness in doctrinal terms — fully, partially and non-mission-capable, with maintenance and supply called out separately.
- 03
Telemetry chips — battery, backhaul and jam — sit on the liveness channel, colouring the row the moment a degraded report lands.
- 04
Readiness is operator-set with telemetry as a suggestion only; the two constructs stay distinct.
POSITION FRESHNESS
READINESS
TELEMETRY
MAN-DOWN / PANIC
Each echelon level emits its own live signal.
Force Management is not a static org chart; every level carries a datastream. A unit emits a position trail and a parallel, tamper-evident device-event record — acknowledgeable by the operator and drawn from a fixed set of nine kinds. Man-down and panic events surface against the covering patrol run and escalate even a collapsed section header to red.
ECHELON CADENCE STACK
MAN-DOWN @ LEAF · CHAIN ESCALATED
DEVICE-EVENT TAXONOMY
9 KINDS · FIXED SET
Every event a friendly unit raises lands on one tamper-evident record and drives the liveness picture. The kind set is fixed and catalogued, so liveness, alarms and patrol review all read from the same vocabulary.
- 01
Each position report can carry telemetry — battery, backhaul, ignition and jam — while coordinate-only reports stay first-class.
- 02
Each unit keeps a short trail of its recent movement, showing where it has been without retaining a long-term track.
- 03
Operator acknowledgement clears an alarm from the picture — and the acknowledgement itself lands on the same tamper-evident record.
- 04
Liveness, readiness, telemetry chips and last-fix mono age compose each TRACK-mode unit row.
POSITION INGEST
POSITION TRAIL
LAST-FIX FRESHNESS
DEVICE-EVENT KINDS
Know your own force the way you know the threat.
Every unit, officer and platform accounted for, governed and live. Talk to our team about a Force Management walkthrough, an evaluation over your order of battle, or an integration into your mounted operating picture.