MASTER STUDY GUIDE
A comprehensive reference for AERO, SPECTRUM, and TACTICAL — explained in both military doctrine and plain English, with competitive positioning and objection handling.
The mathematical core that powers all three defense branches. It is NOT cybersecurity. It is NOT a rules engine. It is a physics engine that treats any operational signal — a drone's flight path, a radio frequency, a unit's movement pattern — as a physical object with mass, velocity, and trajectory.
⚔ Military Doctrine
The kernel is analogous to a battle management system (BMS) that applies kinematic physics to operational signals instead of relying on signature-based threat databases. It baselines the electromagnetic and operational signature of a mission — approved devices, flight paths, radio frequencies, unit movement — and flags any signal that deviates from the mission plan.
The advantage over traditional C2 systems is that it does not need to know what the threat is. It detects that something is moving wrong. This makes it effective against zero-day attack vectors — GPS spoofing, novel jamming patterns, unauthorized devices — that signature-based systems would miss because they have no fingerprint on file.
Plain English
Imagine you're watching a highway. Normal traffic flows at 65 mph in a predictable pattern. A crash doesn't happen instantly — cars start braking, swerving, and slowing down beforethe collision. The kernel watches for those early braking and swerving patterns, not just the crash itself.
It does this for anything — a drone's position, a radio signal's strength, a soldier's movement. It learns what “normal” looks like, then alerts you the moment something starts accelerating away from normal. The key insight: things go wrong gradually before they go wrong catastrophically. The kernel catches the gradual part.
Engine Version
v1.0.0
Production-stable
Computational Loops
5
D to M to KI to Kin to Class
Classification Rules
5 (R1 to R5)
First match wins
Directive Keys
3
Stable, Observe, Rapid Response
Every signal reading runs through five sequential computations. These loops are the same across all three branches — only the input data and directive labels change.
Measures the percentage gap between the current reading and the mission baseline.
⚔ Military Doctrine
Measures the percentage by which the current signal reading deviates from the mission baseline. This is the first indicator of operational drift — a drone 12% off its planned flight path, a radio transmitting at 130% of expected power, a unit moving 20% faster than mission cadence. The baseline is the mission plan; deviation is the degree to which reality has departed from the plan.
Plain English
“How far off is this from what we expected?” If the drone should be at position 100 and it's at 135, that's a 35% deviation. The baseline is just “what normal looks like.” Deviation is “how weird is this right now?”
Encodes the magnitude of the raw signal value into a single-digit structural weight.
⚔ Military Doctrine
Encodes the magnitude of the raw signal value into a structural mass. This is the kernel's way of encoding how heavy the reading is — not how far it deviated, but how big the signal itself is. This creates a second dimension of analysis that prevents the kernel from being fooled by small deviations on large signals (which can be noise) or large deviations on small signals (which can be critical).
Plain English
Think of this as the “weight” of the reading. Every signal value gets a “weight” from 1 to 9 based on its magnitude. It's a second way of looking at the data — not “how far off is it?” but“how big is the thing we're looking at?” Two readings with the same deviation but different masses tell different stories.
Combines structural mass with deviation to produce the kernel's primary threat-score.
⚔ Military Doctrine
The Kinetic Index is the kernel's primary threat-score. It combines the structural mass with the deviation rate so that KI amplifies when a high-mass signal shows even moderate deviation — because a heavy reading that's drifting is more dangerous than a light one. Conversely, KI stays low when deviation is small relative to mass. This is the expression of the doctrine: the bigger the asset and the more it drifts, the faster you need to act.
Plain English
This is the “danger score.” It combines the weight of the reading (Mass) with how far off it is (Deviation). If you have a heavy reading that's also drifting, that's more dangerous than a light reading drifting the same amount. Think of it like this: a cargo truck swerving is more dangerous than a bicycle swerving, even at the same angle.
Tracks the rate of change of the signal — velocity, acceleration, and rapidity.
⚔ Military Doctrine
The kinematic loop is what separates SENTATRON from every threshold-based defense system on the market. It tracks the rate of change of the signal — not just where it is, but where it's going and how fast it's getting there.
Velocity measures how fast the signal is changing per second. Acceleration measures how fast the velocity itself is changing (the second derivative). Rapidity Index normalizes the velocity against the baseline — a rapidity of 1.0 means the signal is changing at a rate equal to the entire baseline per time unit. That is a near-vertical trajectory.
This is how the kernel detects an attack before it completes. A GPS spoofing attack doesn't instantly jump the drone's position — it drifts it, accelerating over time. The rapidity index catches that acceleration pattern before the drone reaches a critical state.
Plain English
This is the “speed and direction” check. Not just “is the drone off course?” but “is it getting more off course?” and “is it getting more off course faster?”
The Rapidity Index is the most important number here. If it hits 1.0, it means the signal is changing so fast that it's headed straight toward a critical event — like a car that's not just braking, but braking harder every second. That's when you need to act now, not in five minutes.
The final loop applies a deterministic, first-match-wins rule set to classify the reading into one of three directive keys. See the Classification Rules section below for the full breakdown.
The kernel evaluates five rules in order. The first rule that matches wins. This is deterministic — the same input always produces the same directive. No black boxes, no machine-learning drift, no “the AI decided.”
Fires when the deviation rate is at or below the volatility floor (default 0.50%).
⚔ Military Doctrine
The signal is within normal operational noise. No action required. The mission is proceeding within parameters. This is the green state — the kernel confirms the baseline is holding.
Plain English
“Everything's fine.” The reading is so close to normal that it's just background noise. No action needed.
Fires when the rapidity index crosses the branch's vertical-trajectory threshold (AERO: 0.8, SPECTRUM: 0.85, TACTICAL: 0.85).
⚔ Military Doctrine
This is the early attack detection rule. It fires when the signal's rate of change is accelerating fast enough to project a near-vertical trajectory toward a critical event — even if the current deviation hasn't reached the magnitude threshold yet. This is how the kernel catches a GPS spoofing attack, a jamming escalation, or a unit cohesion breakdown beforethe asset is lost. The rapidity threshold is set lower than the magnitude threshold specifically to provide early warning.
Plain English
“It's not bad yet, but it's getting worse fast.” This rule fires when the signal is changing so quickly that it's clearly heading toward a problem. Think of it like seeing a car start to swerve — it hasn't crashed yet, but the swerving tells you it's about to. This is the kernel's most valuable rule because it gives you time to act before the worst happens.
Drones, Aviation, Flight-Path Management
AERO monitors the kinetic trajectory of aerial assets — drone swarms, individual UAVs, and aviation platforms. It baselines each asset's flight path, vibrational signature, and signal integrity, then detects drift, spoofing, and compromise before the mission degrades.
⚔ Military Doctrine
AERO functions as a kinematic air defense layer. Rather than relying on ADS-B transponder data alone (which can be spoofed), AERO baselines the physics of each aerial asset's trajectory — its expected position, velocity, and vibrational profile — and monitors for deviation from that baseline.
The key doctrinal advantage: AERO detects GPS spoofing and command-link hijacking by watching for acceleration patterns in the flight path that are inconsistent with the mission plan. A drone being spoofed doesn't instantly jump to a wrong position — its reported position starts drifting at an accelerating rate. AERO's R2 (Vertical Trajectory) rule catches this before the drone reaches a critical state.
Primary signal types: flight_path_deviation, swarm_cohesion, vibrational_mass, signal_integrity.
Plain English
Think of AERO as a smart watchdog for anything that flies. It learns where each drone is supposed to be and how it's supposed to move. Then it watches for two things:
The acceleration check is the magic. Nobody else catches GPS spoofing this early because they're looking at “is the drone in the wrong place?” AERO looks at “is the drone heading toward the wrong place?”
Primary Signal
flight_path_deviation
Position delta from mission plan
Observe Threshold
15% deviation
R4 fires
Rapid Response (Magnitude)
45% deviation
R3 fires
Rapid Response (Trajectory)
0.8 rapidity
R2 fires — earliest detection
Early Attack Detection — How AERO Catches Drone Compromise
GPS Spoofing: The attacker sends false position data to the drone. The drone's reported position starts drifting from the mission plan at an accelerating rate. AERO's R2 rule fires when rapidity reaches 0.8 — before the drone reaches a critical deviation.
Command-Link Hijacking: Unauthorized control inputs cause trajectory deviation spikes. The velocity and acceleration metrics spike before the drone's overall position is critically off.
Physical Interference: A strike or collision causes an abrupt kinematic shift. R3 (Magnitude Critical) fires immediately on the deviation spike.
Competitive Comparison — AERO vs. Other Drone Defense Systems
Telecommunications, Signal Security, EM Perimeter
SPECTRUM baselines the electromagnetic signature of an operational area. Any unauthorized transmission — a forgotten phone, a foreign beacon, an exfiltration burst — triggers a kinetic anomaly directive.
⚔ Military Doctrine
SPECTRUM functions as a dynamic EM perimeter management system. Unlike traditional spectrum monitoring (which scans for known threat frequencies), SPECTRUM baselines the entireelectromagnetic environment of the mission area — every approved device, every authorized frequency, every expected transmission pattern.
Any deviation from that baseline is flagged. This catches:
The kinematic advantage: SPECTRUM tracks the velocity of EM changes. A gradual increase in background EM noise might be environmental. A rapid spike — rapidity above 0.85 — is an active event: jamming, exfiltration, or intrusion.
Primary signal types: em_signature, transmission_burst, device_registry, bandwidth_velocity.
Plain English
Imagine a quiet room where you know exactly what sounds belong — the hum of the AC, the tick of a clock, the shuffle of papers. If someone whispers, you notice — not because the whisper is loud, but because it doesn't belong.
SPECTRUM does this with radio waves. It learns the “sound” of your mission area — every radio, every phone, every device that's supposed to be there. Then it listens for anything that doesn't belong:
The key is it watches how fast things change. A slow drift in background noise might be nothing. A sudden spike means something just happened — and you need to know about it.
Primary Signal
em_signature
EM field strength reading
Observe Threshold
18% deviation
R4 fires
Rapid Response (Magnitude)
50% deviation
R3 fires
Rapid Response (Trajectory)
0.85 rapidity
R2 fires — active event
Competitive Comparison — SPECTRUM vs. Other Signal Security Systems
Ground Units, Perimeter, Kinetic Footprint
TACTICAL reads the kinetic footprint of ground operations — movement patterns, device density, mission cadence. It flags anomalies in the unit's electromagnetic and operational radius.
⚔ Military Doctrine
TACTICAL functions as a unit cohesion and perimeter integrity monitor. It baselines the movement patterns, communication cadence, and device density of ground units — then flags when the unit's kinetic footprint deviates from the mission plan.
This catches:
The kinematic layer detects when unit cohesion is degrading — the spacing between units increasing at an accelerating rate, the movement speed diverging from plan. R2 (Vertical Trajectory) fires before the unit is fully dispersed, giving the commander time to order a regroup.
Primary signal types: unit_cohesion, area_density, mission_cadence, device_anomaly.
Plain English
Think of TACTICAL as a team coach who knows exactly how the team should move together. Every player has a position, a speed, and a rhythm. If one player starts drifting away from the group, or the whole team starts moving faster than the play calls for, the coach notices immediately.
TACTICAL watches for:
The acceleration check is critical here too. If unit spacing is getting worse faster, that's different from slow drift. It might mean the unit is being pushed apart by an external force — and the commander needs to order a regroup before they're fully dispersed.
Primary Signal
unit_cohesion
Inter-unit spacing / coordination score
Observe Threshold
18% deviation
R4 fires
Rapid Response (Magnitude)
50% deviation
R3 fires
Rapid Response (Trajectory)
0.85 rapidity
R2 fires — cohesion collapsing
Competitive Comparison — TACTICAL vs. Other Ground Awareness Systems
Every directive requires human oversight. Three modes control how much the engine does automatically versus how much waits for a commander.
ADVISORY
Every directive requires human review before action. The engine projects the trajectory; the commander decides. Default for all defense branches.
ASSISTED
The engine pre-drafts response directives for one-click commander confirmation. Reduces cognitive load during multi-domain operations.
AUTONOMOUS
The engine auto-executes non-lethal directives and auto-notifies field teams. One-click override always available.
Fail-Safe: Lethal kinetic directives are permanently locked to Advisory mode. The engine can project, recommend, and pre-draft — but a human commander must authorize every lethal action. This constraint is architectural, not configurable. No admin, no setting, no override can change this.
⚔ Military Doctrine
The approval architecture maps to standard rules of engagement (ROE) escalation. Advisory is WATCHCON equivalent — full human control. Assisted is like having a staff officer pre-drafting courses of action for the commander to approve. Autonomous is for non-lethal directives only — frequency shifts, observation deployments, perimeter alerts — where the cost of delay exceeds the risk of auto-execution. The lethal lock is the doctrinal safeguard: no AI system should make kill decisions without human authority.
Plain English
Think of it like a self-driving car with different levels of autonomy. In Advisory mode, the car tells you “I think you should brake” and waits for you to do it. In Assisted mode, it pre-loads the brake and you just tap to confirm. In Autonomous mode, it brakes automatically for non-dangerous situations (like slowing for traffic) but always hands back to you for dangerous ones (like swerving into oncoming traffic). The lethal lock means the car will never swerve into traffic on its own — that decision is always yours.
Every directive emits an immutable audit receipt. Defense regulators can replay any decision without trusting a black box.
⚔ Military Doctrine
Every reading that passes through the kernel generates an audit receipt containing: the input hash (deterministic hash of all input signals), the full kinematic snapshot (signal value, baseline, deviation rate, structural mass, kinetic index, rapidity index), the classification rule that fired (R1 to R5), the engine version, and a timestamp. This receipt is immutable — it cannot be altered after the fact. A defense inspector can take any historical directive, replay the same input through the same engine version, and verify the output matches. This is the compliance foundation for defense procurement and legal review.
Plain English
Every time the system makes a decision, it saves a receipt showing exactly what information it had, what math it did, and what rule it used to decide. Think of it like a bodycam for the AI — you can go back and check exactly why it fired an alert, what numbers it was looking at, and whether it made the right call. No “the computer said so” — you can verify everything.
What's in the Audit Receipt
SENTATRON Defense is not cybersecurity. It is not a drone detector. It is not a spectrum analyzer. It is a physics-based mission integrity engine that detects operational compromise by watching how signals change over time.
The Core Differentiator
Every competing system asks: “Is this bad?” — comparing signals against a database of known threats. SENTATRON asks: “Is this changing wrong?” — comparing signals against the mission's own baseline and watching their trajectory.
This means SENTATRON catches zero-day threats — novel attack vectors that aren't in any database — because it doesn't need to know what the threat is. It just needs to see that the operational physics are deviating from the plan.
Signature-Based Systems
Databases of known threats. Miss anything they haven't seen before.
SENTATRON: Detects novel threats by trajectory, not signature.
Threshold-Based Systems
Alert when a value crosses a fixed line. Don't catch gradual drift or acceleration.
SENTATRON: Catches acceleration before the threshold is crossed.
ML/AI Black Boxes
Machine learning models that flag anomalies but can't explain why. Unreliable for defense compliance.
SENTATRON: Deterministic rules. Every decision is replayable and auditable.
Single-Domain Systems
Drone defense OR spectrum monitoring OR ground tracking. No cross-domain sync.
SENTATRON: One kernel, three branches, cross-branch directive sync.
Common questions and objections you'll face — and how to counter them.
Objection: “We already have spectrum monitoring.”
Response: “Your spectrum monitoring is reactive — it logs events and searches for known signatures after the fact. SENTATRON is kinematic — it watches the trajectory of your EM environment in real time and catches novel threats that aren't in any database. It doesn't replace your SIEM; it adds a physics layer that catches what your SIEM misses.”
Key phrase: “Your SIEM tells you what happened. SENTATRON tells you what's about to happen.”
Push real readings through the kernel and see the directives in action.