Protocol Atlas for Hybrid AI Native Systems

Profiles

Profiles adapt HAINP core semantics to specific industries, environments, and operational constraints.

What a profile does

Defines domain-specific constraints and assumptions
Maps HAINP semantics to real operating environments
Identifies locality, routing, trust, fallback, and observability requirements
Provides concrete scenarios for validation and future implementation

Current profile families

HAINAUTO

Automotive, mobility, V2X, and vehicle-edge-cloud coordination. This is the first proving ground for hybrid execution semantics.

Vertical Profile

HAINIOT

Industrial IoT, distributed edge environments, low-connectivity operations, and device-to-edge coordination.

Vertical Profile

HAINBOT

Robotics, embodied AI, and physical-agent execution across sensors, actuators, local runtime layers, and remote coordination systems.

Vertical Profile

HAINDATA

Data governance, locality, context portability, residency rules, auditability, and controlled cross-domain movement.

Capability Track

HAINCLOUD

Cloud collaboration, workload placement, cloud fallback, hybrid inference routing, and policy-aware execution beyond local boundaries.

Capability Track

HAINMOD

Modal and multimodal execution, including text, voice, vision, sensor inputs, and cross-modal context transfer.

Capability Track

Priority path

HAINAUTO should remain the first profile because it combines strong locality constraints, multi-domain execution, safety-sensitive fallback logic, and a clear vehicle-road-edge-cloud topology.