Protocol Atlas for Hybrid AI Native Systems

Resources

Reference material, glossary seeds, FAQ, and structured notes for understanding the protocol ecosystem around hybrid AI-native systems.

What belongs here

Resources should become the working knowledge base behind the atlas, comparison, gap map, and HAINP drafts — not a generic link dump.

Glossary

Core terms such as execution domain, locality, routing intent, fallback, trust zone, and context portability.

FAQ

Short answers to recurring questions about MCP, A2A, HAINP, protocol layers, and hybrid AI-native execution.

References

External protocol sources, standards bodies, documentation, and implementation references relevant to HAINPRO.

Notes

Editorial notes, comparison observations, and structured ideas that support future drafts and profiles.

Initial glossary seeds

Execution Domain — the environment in which a task runs, such as local, edge, private, or public.
Locality — where data, inference, and context are allowed to remain or move.
Routing Intent — the declared preference or requirement that influences where execution should happen.
Fallback — the governed action taken when preferred execution is not possible.
Trust Zone — a boundary of identity, control, and policy assumptions.
Context Portability — the controlled movement of usable context across domains.

Immediate next additions

Turn “Resources” from a placeholder into a maintained knowledge layer by publishing glossary entries, FAQ answers, and a first curated reference list tied directly to Atlas, Compare, and HAINP.