[{"data":1,"prerenderedAt":4},["ShallowReactive",2],{"raw-en-articles\u002Fmaritime-ontology-for-navigation-cargo-port-operations-and-autonomy":3},"---\ntitle: Maritime ontology for navigation, cargo, port operations, and autonomy\ndescription: Structured ontology semantics for navigation, cargo, port operations, and autonomy\nlang: en\nnavigation:\n  enabled: false\n  section: articles\n  order: 30\ntags:\n  - autonomy\n  - maritime\n  - ontology\n  - operations\n---\nPortfolio governance is possible only when teams use identical definitions for risk and control.\n\n## Why this matters\n\nGovernance fails when different parts interpret policy inconsistently.\n\n## What this looks like in practice\n\n- Governance policies translate directly into control code without ambiguous translation.\n- Risk assessments from different teams are comparable using identical definitions.\n- Escalation decisions are consistent because escalation criteria are uniformly defined.\n\n## How teams use it\n\n- implementing portfolio-level policy consistently across autonomous teams\n- comparing risk across domains using identical metrics\n- auditing governance decisions systematically instead of narrative review\n\nEnterprise risk is knowable only when all units assess risk identically.\n",1776235587829]