Skip to main content
Use a native integration only when portable lifecycle hooks cannot express the required behavior.

Ownership

Native factories are selected only for the active framework. Keep the portable portion in ordinary lifecycle hooks and isolate the native portion.

Migration effect

Advanced applications already own their native runtime. Harnest validates and packages the target but does not compose managed capability folders into it.

Invocation hooks

Keep cross-framework policy portable.

ADK and LangGraph

Review the full portability boundary.