Research Foundation
Built on what aviation already learned.
The architectural choices in the iNav4U Platform are not opinions. They are the conclusions of decades of peer-reviewed human factors research, applied to a vessel.
This page explains why the iNav4U Platform is built the way it is — and points to the research that justifies the architecture. Every major design decision in the platform, from the clean OS / data / UI separation to the "suggestions never decisions" principle in the intelligence layer, traces back to specific findings in published aerospace human factors literature.
The core insight: design-induced error
Studies of maritime and aviation accidents consistently report that 60–85% of incidents involve "human error". The number gets cited everywhere, usually as a justification for more automation, more alerts, more safeguards.
The foundational human-factors research tells a different story.
In her landmark work on situation awareness, Mica Endsley showed that the overwhelming majority of "human error" is actually design-induced error — failures caused by systems that fail to present information in a way people can understand and act on under operational load. The human is doing their best. The interface is failing them.
This single insight reframes the entire problem. The fix is not "more automation, more alarms, more displays." The fix is better information design — surfacing the right information, at the right time, in a form that supports the operator's current task.
The aviation parallel
In the 1980s and 1990s, aviation underwent a quiet revolution.
Cockpits had been built for decades around dozens of individual instruments — each one showing one number, each one demanding the pilot's attention, each one adding to cognitive load. The aviation industry replaced this with the Primary Flight Display (PFD) — a single integrated screen showing the same information in a unified, task-aware presentation.
The results were dramatic: safer flying, better pilot performance, fatigue-resistant decision-making, and lower training requirements. The information available to the pilot did not change. The way it was presented did.
Marine electronics never made this transition. Most boats today still operate on a 1980s-style instrument philosophy — a chartplotter here, an engine display there, a battery monitor over there, an AIS panel somewhere else. Each screen shows its own slice of the boat. The skipper is left to assemble the picture mentally, in real time, under stress.
The iNav4U Platform is the marine equivalent of the PFD revolution.
How the iNav4U Platform applies the research
The aviation insight maps directly onto a system architecture, and that architecture is the iNav4U Platform:
The OS handles data
Collecting, validating, and prioritizing every piece of information from every onboard source — across all the protocols a modern boat uses — is the OS's job. The user does not see this work happen. The user does not need to.
The user interface extracts and displays
The user interface is a client of the system, not the system itself. Its job is to take the validated picture the OS produces and present only what the user needs for the task they are doing right now — clearly, calmly, and without noise. See User Interfaces.
Intent-driven presentation
The user declares the current task — passage, anchoring, docking, regatta — and the interface surfaces the relevant subset. This is the marine analog of the aviation PFD's mode-aware display. The information is always there, but the presentation adapts to what the operator is actually doing.
Suggestions, never decisions
The intelligence layer produces suggestions with transparent reasoning, never autonomous decisions. The skipper stays in command. The system explains why it is recommending what it is recommending, and the human chooses.
Traditional fallbacks remain
A vessel running iNav4U OS can still be navigated with paper charts, a magnetic compass, a sextant, and the celestial almanac service — the same way mariners have done it for centuries. The platform's job is to make the modern path safer and easier, not to remove the traditional path.
The references
The research foundation for the iNav4U Platform is grounded in three bodies of work.
Designing for Situation Awareness
Endsley, M. R., & Jones, D. G. (2012). Designing for Situation Awareness: An Approach to User-Centered Design (2nd ed.). CRC Press.
The foundational framework for user-centered design in complex, high-stakes systems. Endsley's work establishes that situation awareness — not raw information — is the metric that matters for operator performance, and that design choices either build it or destroy it. This is the intellectual backbone of the iNav4U / UI separation.
AI in the flight deck — the HABA-MABA-AABA framework
Korentsides, J., et al. (2026). The use of artificial intelligence (AI) in the flight deck: Enhancing human-AI teamwork in aviation. Journal of the Air Transport Research Society, 6, 100099.
Recent peer-reviewed work establishing the HABA-MABA-AABA task allocation framework — Humans Are Better At / Machines Are Better At / Adaptive Allocation Between Both Agents — for human-AI collaboration in aviation. This framework directly informs how the iNav4U intelligence roadmap distributes work between the system and the operator: the machine does what machines are good at, the human does what humans are good at, and the boundary between them is explicit and adjustable.
doi.org/10.1016/j.jatrs.2025.100099 →
DARPA Air Combat Evolution (ACE)
DARPA ACE Program — Air Combat Evolution.
A defense research program developing autonomous systems that maintain human decision authority in extremely high-stakes environments. The principle: even when the machine is faster, the human remains in command, and the machine's role is to support — not replace — human judgment. This principle is non-negotiable in iNav4U, and the ACE program's framing directly informs the "suggestions, never decisions" rule in the intelligence layer.
darpa.mil/program/air-combat-evolution →
Why this matters
A marine operating system that ignores forty years of aerospace human factors research is not engineering. It is a marketing exercise.
The iNav4U Platform is built on the conclusions of that research, not in spite of them. The OS / UI separation, the intent-driven presentation, the explainable rule engine, the careful framing of machine intelligence as suggestion rather than decision — every one of those choices traces back to specific findings, specific frameworks, specific peer-reviewed work.
We do things the way they are meant to be.
That includes basing the architecture on what the field has already learned.