NORNR
Official day-1 embeds for agent runtimes that already matter.
NORNR / Framework embeds
Day-1 supportWe are intentionally narrowing the official embed story to OpenAI Agents SDK and LangGraph first. One runtime lane and one orchestration lane are enough to prove that NORNR can sit above agent execution without becoming a framework zoo.
The point of a framework embed is not to recreate the runtime. It is to make policy decision, review path and defended record feel default before a consequential action becomes routine.
Official embeds
The question stays the same in both: should this action run under the active owner mandate?
Best first fit when a tool call inside the runtime can become paid usage or a vendor-side action and the team needs a decision before it executes.
Best first fit when the team already models state transitions and needs NORNR to decide which edges can reach consequential actions.
CrewAI, AutoGen and the broader long tail still matter, but widening too early weakens the product story. The day-1 embed surface should stay narrow until buyers already understand the control model.
The winning integration is the one that leaves policy reason, approval state, receipt trail and audit export on the same governed path, not the one with the most adapters.
What the embed proves
These embeds only matter if they leave a better decision and proof trail than the runtime could on its own.
NORNR should answer the mandate question before the tool call, graph edge or consequential action touches settlement or a vendor workflow.
The runtime stays intact. NORNR only adds a bounded review path when the active mandate is no longer enough.
If the embed cannot carry the path into receipt trail, audit export and finance handoff, it is not yet a first-class NORNR surface.