System Architecture & Logic
The operational core of Nav-Fi³ is the Recursive Navigation Engine (RNE), a data processing system synchronized with the TravellerMap Imperial database. Every route stored in the system is not merely a list of coordinates, but a deterministic graph of jump vectors.
The architecture is built upon the concept of Navigational Determinism: once a route is compiled and validated, physical parameters (fuel, time, distance) become immutable until manual recalculation or link termination.
Technical Specs
Data Synchronization Logic
Calculated based on Euclidean distance between hex centers, respecting strict sector boundaries and Imperial parsecs.
Queries the OTU API to extract UWP, Importance, and Hazard Zones (Amber/Red) in real-time. Supports Fuzzy Label Matching for legacy sector data.
Advanced A* algorithm implementation with heuristics based on the asset's specific J-X drive capabilities.
Maintains Imperial Date consistency across different navigation sessions, tracking every week of layover or travel.
Nav-Link Status Lifecycle
The system operates in two mutually exclusive modes tied to the navigation hardware. Understanding the transition between these states is vital for crew safety.
PLANNING_MODE
- Mutable Waypoints
- A* Jump Recalculation
- Manual Cursor Sync
- Fuel Simulation
NAV_SYNC_ACTIVE
- Immutable Vector Graph
- Transit Control HUD
- Seven-Day Temporal Leap
- Bookmark Auto-Update
Operational Protocols
Protocol Delta: Manual Cursor Sync
When the route is inactive, the navigator has exclusive access to the Manual Override. This function instantly synchronizes the virtual position with a waypoint loaded in the table.
Use this function strictly to realign the Nav-Computer in the event of forced jumps, stellar emergencies, or when the vessel is towed off-course.
COMMAND Execute: Set Bookmark on NODE_CURRENT. Success.
Protocol Epsilon: Transit Execution
Executing a jump (Transit) triggers a sequence of atomic operations synchronized with the jump reactor:
- 01. Vector Calculation Matrix
- 02. Fuel Consumption Lock
- 03. Imperial Time-Link Leap (+7D)
- 04. Bookmark State Persistence
Protocol Zeta: Logistics Integration
The navigation system is now bi-directionally linked with the Cargo Hold Management System.
- Automatic Origin Logging (Loot)
- Sector-Aware Liquidation Lookup
- UWP Label Normalization
Every transit waypoint acts as a potential Liquidation Terminal. By selecting the current sector, the navigator can access localized trade data and finalize sales (Income) or register new cargo (Loot) with high-fidelity UWP labels extracted directly from the Imperial Grid.
Advanced Diagnostics
"Interface Integrity Failure: Calculated transit exceed J-X capabilities."
This error state precludes Nav-Link activation. It indicates a physical discrepancy between the navigator's planning and the actual specifications of the jump engine installed on the asset.
Correction Matrix
Engage the RECALCULATE subroutine. The system will query Imperial navigation beacons to automatically inject intermediate refueling nodes into the flight plan.
Analyze stellar cartography via the SAT-LINK interface. Identify a system suitable for the asset's range and manually insert the node waypoint.
// SECURE TERMINAL END // ALL DATA COMPLIANT WITH IMPERIAL NAVAL CODE //