Authority Graph
Your organization's delegated authority, modeled as a structure a runtime can evaluate -- not rebuilt, just made machine-readable.
Authority exists in documents. Runtimes need it in structure.
A Delegation of Authority policy is written for humans to read and interpret. It answers "who can approve what" in prose, cross-referenced against an org chart that lives somewhere else, and an approval matrix that lives somewhere else again. None of that is queryable by a system that needs an answer in milliseconds, for an actor -- an AI agent -- that has no judgment to apply to an ambiguous case.
One graph: principals, delegates, limits, and roles
The Authority Graph ingests your existing governance documents and organizational data and produces a single structure connecting who holds authority, who it's been delegated to, what constraints apply, and where that sits in the org's role hierarchy. Runtime Authority queries this graph on every intent; it is the "who is allowed to delegate what, to whom" half of every decision, alongside the "under what conditions" half supplied by Runtime Policies. For the schema-level detail -- what a delegation record actually contains -- see Authority Graph in the Developers section.
What the graph actually models
Governance ingestion
Existing Delegation of Authority documents, approval matrices, and signing schedules are read directly -- as source documents, not as a template to fill in from scratch.
Delegated authority
Who may act on whose behalf, and how far that delegation extends, is modeled explicitly, including chains of delegation rather than a single flat permission.
Role hierarchy
Reporting lines and organizational structure become part of the graph, so authority evaluation reflects how the organization is actually structured, not a simplified approximation of it.
Approval limits
Monetary thresholds, transaction types, and category-specific limits are captured as constraints on delegation, not as a separate system that has to be kept in sync.
Organizational modeling
Business units, cost centers, and principal-to-agent relationships are represented as first-class entities the runtime can evaluate against.
Machine-readable authority
The output is a graph a deterministic runtime can query in sub-millisecond time -- the same governance structure, in a form software can actually evaluate.
Bring your Delegation of Authority document
We'll show you it modeled as a graph Runtime Authority can evaluate against, in the same session.