Automated Succession Control Engine — Networked Tactical · Powered by SUCCESS.ION GB2607848.5
ASCENT.
The patrol never loses its medic.
A doctrinal answer to a question the MoD has not formally solved: what happens to medical authority when the medic is the casualty, in a peer adversary contact, where radio silence is non-negotiable and the patrol cannot stop fighting.
The Problem ASCENT Solves
MEDICAL AUTHORITY
CANNOT REACH ZERO.
In conventional operations, when the medic goes down, someone shouts. Someone makes a radio call. Someone decides who takes over. In a peer adversary contact at squad level, none of those options are available. Noise gets people killed. Radio transmissions get people located. The patrol cannot stop fighting to reorganise medical command.
ASCENT — Doctrinal Position
THE PATROL NEVER HAS ZERO MEDICAL AUTHORITY. THE SYSTEM DEGRADES GRACEFULLY THROUGH DEFINED FAILOVER STATES — EACH ONE LOGGED, EACH ONE REPORTED TO LINE 2 AT THE EARLIEST SAFE OPPORTUNITY. NO RADIO CALL. NO AUDIO ALERT. NO PAUSE IN THE FIGHT.
ASCENT is not a procedure that soldiers follow. It is a system state that activates automatically and degrades through defined fallback positions until medical authority is re-established. The soldier who assumes medical authority does not need to announce it, call it in, or explain it. The system logs it, timestamps it, and reports it. The chain of medical authority is unbroken and documented even in the worst case.
The Full Protocol
EIGHT PHASES.
ONE OUTCOME.
From the moment a man down event is detected to the moment medical authority is re-established — across all four systems, in silence, without breaking the patrol's fighting posture.
Man Down Detected
SENTINEL detects the man down event — automatically via biosensor threshold breach (heart rate, movement cessation, impact detection) or manually triggered by the casualty or a buddy. SENTINEL holds the casualty's medical data current to the patrol's blood testing cycle. On detection, that data is burst via Bluetooth to the patrol mesh.
Automatic or manual · Bluetooth data burst to mesh · No radio transmissionSelective Notification
The medic is notified immediately. The patrol is not. This is deliberate — in a contact scenario, pushing a man down alert to every soldier is a distraction that gets people killed. The patrol continues fighting. The medic holds the information and assesses the tactical situation. VANTAGE initiates the MIST report automatically from the SENTINEL data burst.
Medic notified · Patrol not notified · MIST initiated automatically · No audioLine 2 Notification
VANTAGE notifies Line 2 where comms permit. Not broadcast immediately — queued and transmitted at the earliest safe opportunity. The notification includes the MIST report initiated from SENTINEL data. Higher command is informed without the patrol having to break cover or interrupt the engagement.
Queued · Transmitted when safe · MIST attached · No immediate broadcast requiredWBB Protocol — Medic Activated
SDICS has already identified the compatible donor from the patrol's blood type and eligibility data held on the mesh. When the medic deems the tactical situation safe, they activate the WBB protocol via VANTAGE. At that point — and not before — the identified donor is notified by VANTAGE: visual only, screen display, no audio. They are told they are needed and where to go. Terse. Operational. Nothing more.
Medic discretion · SDICS compatibility pre-identified · Visual notification only · No audioCompetency-Aware Failover
If the medic is the man down and cannot initiate — ASCENT activates. SDICS holds medical qualification data for every patrol member: BATLS, Combat First Aid, basic trauma. ASCENT queries that data and identifies the most qualified available patrol member. Qualification data is command-assigned, rank-gated for amendment — a soldier cannot self-promote their own medical qualification. The hierarchy is set by command before the patrol departs.
The selected soldier's VANTAGE switches to Medic role — silently, server-side. Notification is visual only: screen display, no audio, no radio call, no indication to the enemy that command structure has changed. The interface and UX shift immediately to full Medic configuration: MIST, nine-line MEDEVAC, WBB activation — all Medic-role outputs available from the moment of promotion.
Automatic · Competency-aware · Silent · Visual only · Full Medic UX immediately availableManual Self-Designation
If no qualified successor exists in the patrol — every qualified member is a casualty, or qualifications are insufficient — the final failover is manual. Any operator can self-designate as medic within VANTAGE. This is a command decision, not a technical workaround. It is logged with timestamp and operator identity. HEARTBEAT captures the designation event and queues it for transmission to Line 2 at the earliest safe opportunity.
On self-designation, VANTAGE immediately shifts to full Medic UX for that device. The operator is not pretending to be a medic. They are formally assuming medical authority, with a record that goes up the chain. The chain of medical authority is unbroken and documented.
Manual · Any operator · Logged · HEARTBEAT captures · Line 2 notified · Full Medic UX immediatelyComplete Event Record
Every ASCENT event — man down detection, MIST initiation, WBB activation, role transition, self-designation — is logged by HEARTBEAT with timestamp, operator identity, and tactical context. The complete record is transmitted to Line 2 at the earliest safe opportunity. The forward medical facility receives not just the casualty's MIST report but the full chain of medical authority decisions made during the engagement. The record is tamper-evident.
Complete audit trail · Tamper-evident · Transmitted to Line 2 · Forward medical facility recordNine-Line MEDEVAC Output
When the tactical situation permits evacuation, the acting medic — whether the original medic, an ASCENT-promoted successor, or a self-designated operator — initiates nine-line MEDEVAC via VANTAGE. The format is automatic. The casualty data from SENTINEL populates it. The acting medic states what they know; VANTAGE structures it correctly. The MEDEVAC transmission is the final step in an unbroken chain of medical authority that began at the moment of man down detection.
VANTAGE Medic role · Nine-line auto-formatted · SENTINEL data populates · Unbroken chainFailover Architecture
DEFINED STATES.
NO GAPS.
ASCENT degrades through defined system states. Each state has a trigger, a system response, and a logging event. There is no undefined state in which medical authority is absent.
| State | Trigger | System response | Logging |
|---|---|---|---|
| Nominal | Medic operational | Medic VANTAGE active. SENTINEL monitoring. SDICS data current. WBB pre-identified. | HEARTBEAT continuous |
| Man Down — Other | Non-medic casualty detected | Medic notified (visual). Patrol not notified. MIST initiated. WBB compatibility checked. Line 2 queued. | HEARTBEAT logs event + MIST |
| WBB Active | Medic activates WBB protocol | Compatible donor notified (visual, screen only). Donor location available to medic. Protocol logged. | HEARTBEAT logs activation + donor ID |
| ASCENT — Auto | Medic is man down | SDICS queries qualification hierarchy. Most qualified available patrol member promoted. VANTAGE role switches silently. Visual notification only. Full Medic UX immediately. | HEARTBEAT logs promotion + qualification basis + timestamp |
| ASCENT — Final | No qualified successor available | Manual self-designation available to any operator via VANTAGE. On designation: full Medic UX. Decision logged immediately. | HEARTBEAT logs self-designation + operator identity + tactical context. Line 2 notified at earliest opportunity. |
| Recovery | Original medic recovered / evacuation | Medical authority returned to original medic or transferred to receiving facility. All ASCENT events included in handover record. | Complete ASCENT event record transmitted with casualty |
Integrated Systems
FOUR SYSTEMS.
ONE PROTOCOL.
ASCENT is not a single product. It is the protocol that integrates four existing NeuroSync defence capabilities into a coherent medical authority continuity system.
SENTINEL
Detection · Data · MeshMilitary HEARTBEAT. Holds medical and qualification data per patrol member. Detects man down automatically or manually. Bursts casualty data to mesh on event. Maintains blood type, donor eligibility, and medical competency records — updated per patrol cycle, qualification data rank-gated for amendment.
SDICS
Compatibility · Qualification · SuccessionHolds donor compatibility data for WBB activation. Holds medical qualification hierarchy for ASCENT succession. Competency-aware — knows who has BATLS, Combat First Aid, basic trauma. Drives both the WBB compatible donor identification and the ASCENT automatic promotion decision.
VANTAGE
Execution · Interface · NotificationExecutes the role transition. Manages all notifications — visual only, no audio in contact. Provides full Medic UX to promoted or self-designated medic immediately on activation. Nine-line MEDEVAC, MIST, WBB activation — all available from the moment of ASCENT state entry. Self-designation captured and queued for Line 2.
HEARTBEAT
Logging · Transmission · RecordCaptures every ASCENT event with timestamp, operator identity, and tactical context. Queues all transmissions for Line 2 at earliest safe opportunity. Produces the tamper-evident complete record of medical authority decisions that travels with the casualty to the forward medical facility. The unbroken chain of custody for medical authority.
SUCCESS.ION
The Engine · GB2607848.5 · Filed 5 April 2026ASCENT is the military first embodiment of SUCCESS.ION — the patented configurable competency-based role succession and operational continuity engine. The distributed mesh data store, the weighted succession scoring, the rank-gated qualification matrix, the silent notification, the biometric self-designation gateway, the coercion detection layer, and the tamper-evident audit trail are all SUCCESS.ION capabilities deployed in a tactical military context. The same engine is licensable across any hierarchical command structure in any domain.
Tamper-Evident Records
All ASCENT events are logged with cryptographic integrity. A compromised or altered record is detectable. The chain of medical authority cannot be retrospectively modified.
Rank-Gated Amendment
Qualification data — the data that drives ASCENT succession — can only be amended by command rank. A soldier cannot self-promote their own medical qualification in the system. The hierarchy is set by command before deployment.
Zero Audio in Contact
Every ASCENT notification is visual only. No audio alert is ever generated during an active contact scenario. Noise discipline is preserved. The enemy receives no indication that the patrol's medical command structure has changed.
Queue and Send When Safe
No transmission is forced during active contact. Line 2 notifications are queued and sent at the earliest safe opportunity. The system does not compromise patrol security to maintain the reporting chain.
Multimodal Baseline Monitoring
VANTAGE monitors voice pattern, gaze, and interaction cadence against each operator's baseline profile at every authentication event. SENTINEL contributes physiological data. Deviation above threshold triggers a covert alert to Line 2 while the visible succession proceeds normally. A passive duress signal enables silent flagging without alerting the coercing party.
UKDI Submission · 2 June 2026
THE DOCTRINAL
ANSWER.
ASCENT is the answer to a question the MoD has not formally resolved in doctrine. It is not a feature of one product. It is a protocol that integrates four systems into a capability that the British Army does not currently have.
UKDI Innovation Outline · 19 May 2026 · GB2607848.5 Filed · Full Submission · 2 June 2026
PATENT FILED.
GB2607848.5
5 APRIL 2026.
Complete ASCENT protocol documentation, system integration architecture, qualification hierarchy design, data security model, and UKDI submission package available to qualified MoD, UKDI, and NATO procurement contacts under NDA.