Mission Intelligence Ontology Layer
A governed semantic foundation enabling products, systems, people, AI models, and partner organizations to interpret mission information consistently.
Systems cannot collaborate reliably without a common mission language.
Different systems may describe the same reality as a track, asset, object, vehicle, unit, platform, contact, or node while disagreeing about identity, time, location, confidence, status, ownership, classification, authority, role, relationship, and significance. MIOL establishes governed semantic contracts so exchanged information retains consistent and computable meaning.
- Missions and objectives
- Actors and organizations
- People and roles
- Assets and capabilities
- Observations and sources
- Events and activities
- Locations and operating areas
- Decisions and recommendations
- Plans and tasks
- Policies and authorities
- Constraints and risks
- Actions and outcomes
- Evidence and provenance
- Models and simulations
- Knowledge and lessons
Meaning becomes a governed interface.
Concept and Identity
Defines the represented concept, attributes, relationships, identity rules, and validation expectations.
Time, Location, and Confidence
Preserves how mission information is situated, measured, qualified, and interpreted.
Provenance and Markings
Maintains source, transformation history, classification, ownership, and known semantic limitations.
Compatibility
Controls extensions, versions, deprecation, migration, and change-impact analysis.
Product Conformance
Ensures seven mission products interpret shared concepts without semantic forks.
Partner Views
Supports sovereign terminology and policy while preserving shared mission meaning.
Each product adds responsibility without redefining the mission.
Fusion™
Creates and updates trusted observations and mission objects.
Command™
Relates objectives, tasks, resources, and dependencies.
Decision™
Connects options to evidence, assumptions, risks, and outcomes.
Sim™
Represents possible states, events, and alternative futures.
Govern™
Evaluates identity, policy, authority, purpose, and constraints.
Coalition™
Applies releasability and partner-specific representation.
Autonomy™
Relates authorized assets, tasks, operating envelopes, and execution.
The mission language must evolve without breaking the mission.
MIOL governance includes versioned contracts, architecture review, compatibility rules, change-impact analysis, deprecation, migration planning, validation suites, stewardship, extensions, and evidence. Phoenix governs review, testing, approval, publication, and adoption.