Boundary
Graph state may carry Vira runtime identity, not control-plane secrets.
FRAMEWORK
LangGraph
Resolve around graph execution while preserving graph/run correlation and keeping LangGraph as the orchestrator.
EXECUTION BOUNDARY
Vira hooks execute before and after the relevant graph work. Graph topology, node scheduling, memory, and tool orchestration remain native to LangGraph.
IDENTITY PRESERVED
Keep the behavior identity attached to the host framework.
- Behavior Point
- run correlation
- exact behavior revision
- resolve-issued trace context
SUPPORTED OPERATIONS
Use Vira where the control boundary actually belongs.
- 01
resolve before a governed node or graph execution
- 02
store returned Vira context in run state
- 03
pass the context unchanged to after-node tracing
- 04
correlate runtime output with the exact resolve identity
IMPLEMENTATION HOOK
Keep the host runtime native.
This example mirrors the repository documentation. The exact API contract remains in Docs and source.
const hooks = createLangGraphHooks(vira, {
context: { kind:"agent", host:{ name:"langgraph", runtime:"node" }, modelTarget:{ provider:"openai", model:"your-model-id" } },
});
const context = await hooks.beforeNode(resolveRequest);
const output = await graph.invoke(input);
await hooks.afterNode(context, output);SECURITY BOUNDARY
Integration does not equal authority.
Boundary
Higher-authority behavior still resolves in the control plane before projection.
LIMITATIONS
State what the adapter does not control.
- The adapter does not replace graph orchestration.
- A later node must not recompute an earlier revision identity.
- Missing authority cannot be inferred from generic graph telemetry.