SOLAR
Modeled energy input while surfaced. The digital twin identifies the conceptual solar-capable upper area.
Future physical platform
Pelagio Defense’s physical platform is a software-defined concept: a future maritime node with energy, sensing, communications, onboard autonomy, station keeping, and a modular payload bay.
The present product validates data contracts, operator interfaces, and deterministic software behavior. It does not validate physical dimensions, endurance, range, cost, depth, speed, weight, or manufacturability.
View readiness evidenceDigital twin
The interactive model explains intended systems and software states. Its geometry is illustrative and does not represent deployed or field-validated hardware.
SYSTEMS
Modeled energy input while surfaced. The digital twin identifies the conceptual solar-capable upper area.
Canonical simulation nodes track battery percent, energy kWh, storage capacity, solar input, and charging state.
PodAgent evaluates only PodState and a local SensorPicture. It cannot access hidden world truth.
Local sensing produces contact ID, estimated class, confidence, range, bearing, last-seen tick, and source.
The model represents local or remote runtime, communications health, degraded state, and offline state.
A visual abstraction of low-speed local position maintenance. No propulsion specifications are claimed.
A stateful conceptual bay supports interchangeable simulated reconnaissance, relay, environment, and abstract response modules.
ENERGY
Each node tracks battery percent, kWh, capacity, solar kW, daylight generation, and state-dependent consumption. Low energy changes eligibility and can move a node into charging.
SENSING
A SensorPicture contains only contacts within local modeled range. Every record carries observed class, confidence, range, bearing, source, and last-seen tick.
COMMUNICATIONS
Communications health participates in mission scoring. An offline node produces an empty local picture; local deterministic autonomy remains the fallback runtime.
AUTONOMY
PodAgent returns a typed decision from PodState and SensorPicture. RuntimeManager validates the decision and isolates optional remote failure before applying it.
PAYLOAD BAY
The canonical lifecycle drives CLOSED, OPENING, OPEN, and CLOSING bay states plus reconnaissance deployment, transit, observation, return, and recovery.
LIMITATIONS
No real hardware is controlled. No real deployment, navigation, targeting, weapon, guidance, or engagement capability exists. Geometry is illustrative and carries no validated specification.
Simulated mission states
The simulation workspace, mission record, and 3D twin consume the same canonical state. No state controls real hardware.