Open infrastructure for Decision Graphs
Reasoning Layer infrastructure for enterprise AI agents needs a shared substrate - an agreed-on shape for what a decision is, how decisions reference each other, and how an agent queries the chain. Uvi is publishing that substrate, open and free, under Apache 2.0.
Two artifacts, one principle. An open schema specification anyone can implement against, and a reference MCP server that plugs straight into Claude Desktop, Cursor, and any MCP-compatible agent runtime. Build your own backend, fork the reference, or run Uvi as the managed implementation - the choice stays yours.
What’s shipping
decision-graph-spec
The open schema. Node types, edge types, attributes, state machine, GraphQL SDL, MCP protocol contract, worked examples. Implementations welcome. Apache 2.0.
github.com/nabooai/decision-graph-spec@naboo/mcp-server
A working MCP server that exposes the spec’s tools (list_decisions, get_blockers, trace_decision_chain). Plugs into Claude Desktop, Cursor, and any MCP-compatible agent. Apache 2.0.
npx @naboo/mcp-servergithub.com/nabooai/mcp-server Why this is open
Uvi’s reasoning is simple. The category needs a shared shape before any single vendor can win it - otherwise every agent runtime ends up integrated against a different proprietary surface, and the whole stack rots into glue code.
We have a strong opinion on what that shape should be, because we’ve been deploying Decision Graphs inside large organizations (Global-E, Melio) for a while. So we’re publishing the shape as a spec, and a reference implementation that works today, and inviting the rest of the ecosystem to ship alternatives.
The schema is the contract. The reference is the proof. The hosted Uvi product - the Forward Deployed Agent who sits with your team and encodes your organization’s decisions into the graph - is the thing we sell. Those are two cleanly separable layers. We’re betting the category is bigger than any one vendor.
How to get involved
Read the spec
Start with spec/0001-introduction.md in the repo.
Run the MCP server
Five-minute install. Comes with an Acme Co sandbox backend you can query immediately.
Comment on RFCs
All schema discussions live in GitHub Discussions. Issues are for bugs only.
Governance
v0.x is BDFL-governed by Uvi while the shape settles. From v1.0 onward, schema changes require an RFC and rough consensus from active implementers. We’ll publish the process in CONTRIBUTING.md alongside the spec.
Two ways to engage Uvi
The schema and the reference MCP server are yours to fork, extend, and ship against. Or talk to us about the hosted Reasoning Layer infrastructure - a Forward Deployed Agent who encodes your organization’s Decision Graph alongside your team.