The 7 Signals
USV Autonomy &
Human-in-the-Loop
Operations
Master Framework — Robotic Warfare Specialist Interface Design
We design for cognitive restraint, operational clarity under fatigue, and surviving reality. No skeuomorphism. No arcade effects. No "AI magic." Dark graphite grids. Muted navy. High legibility at a distance.
Dark graphite grids. Muted navy. High legibility at a distance.
Amber = Warning. Red = Operator Decision Required.
Animations must communicate state, risk, and intent surgically.
Motion as Telemetry
Motion is not decorative; it is a vital operational signal. If an animation does not actively reduce cognitive friction or improve decision-making under stress, remove it.
1. System Boot Mission Start
power2.inOut / 0.85s per module, staggered 0.15s.
2. Autonomy Handoff Mode Switch
easeInOutSine / 3.0s continuous "breathing" loop.
3. Sensor Confidence Degradation
rough ease / Variable based on telemetry.4. Fault Diagnosis Intervention
power1.out / 1.2s total sequence drawing.
5. Post-Mission Debrief AAR Timeline
none (Linear) for playback, power3.out for annotations.USV-7: 0300 HRS Collision Analysis
Operator intervened 4 seconds too late. Two failures identified. Both were design failures.
Post-Incident Review
Scenario: USV-7 collided with a drifting semi-submersible hazard at 0300 HRS under low-light supervision. Operator intervened 4 seconds too late.
-
Failure 1 — Alarm Fatigue: When bow radar degraded due to heavy spray,
the previous UI flashed a bright amber border. The operator classified this as "routine
environmental noise" and ignored it.
Redesign applied: The UI now blurs and jitters slightly, communicating ambiguity without triggering an ignored, boy-who-cried-wolf flashing alarm. -
Failure 2 — Handoff Ambiguity: The autonomy algorithm snapped control back
to the operator in 0.1 seconds. The operator, experiencing microsleep, missed the instant
visual change.
Redesign applied: Autonomy transitions now require a 2-second visual build-up and a physical hardware confirmation before snapping off. Red is exclusively reserved for this state.
The Seven Signals of Operational Design
Seven governing truths for how systems build behavior under pressure. Less motivational language. More operational reality.
Design the inputs or accept the outcome.
Every hesitation, shortcut, or procedural collapse under pressure can be traced upstream to an environment that built it or failed to replace it.
The system learns through repetition.
Exposure is not capability. Capability is deposited through repetition across time, variation, and honest conditions. If you did not count the reps, you did not design them.
You default to training, not intention.
Under cognitive load, aspiration shuts down and subroutine runs. The operator becomes who the system rehearsed.
Friction is not a problem. It is the mechanism.
Comfort in training does not transfer. Friction exposes weak defaults, encodes memory, and separates borrowed performance from built capability.
What you rehearse becomes what you execute.
Every scenario teaches more than the visible procedure. It teaches pacing, posture, cross-checking, and refusal.
Under pressure, the system reveals its true configuration.
Pressure is an X-ray. It exposes what was built and what was borrowed, what is load-bearing and what was merely decorative.
The Whole Doctrine
Not content delivery. Not completion metrics. Not certification theater. Not the performance of readiness.
The work is to build an operator under conditions honest enough, repeated enough, measured enough, and difficult enough that the right response survives the moment when intention no longer matters.