The Evidence Portal
The enterprise evidence layer for Runtime Authority: every decision, signed, searchable, and exportable.
Knowing a decision happened isn't the same as knowing why
When an agent's action gets escalated, blocked, or produces an unexpected outcome in production, an engineering or platform team needs to understand why just as urgently as an auditor does later, for a different reason: to fix what's live, not to answer for it after the fact. Today, that means going looking: pulling application logs, reconstructing state from memory, and hoping the context that mattered at decision time is still recoverable. The record exists. Nothing surfaces it to the team that needs it first.
Every decision Runtime Authority makes becomes a signed record
Allow, Deny, and Human Review outcomes are not application logs: they're cryptographically signed evidence records, produced at the moment of decision, tied to the exact agent, intent, and policy version involved. The Evidence Portal is where that evidence is investigated, searched, audited, and exported, without requiring anyone to query the underlying runtime directly. For how to verify a record's signature and export it programmatically, see Evidence Verification in the Developers section.
Three evidence layers, one record
A signed outcome by itself only tells you what happened. Every Evidence Portal record is built from three layers of evidence: what was proposed, why it was decided, and, where applicable, what actually happened downstream.
Intent Evidence
What was proposed or observed: the agent's signed intent, and, where a Trusted Adapter is in place, the independently observed enterprise operation it corroborates.
Authority Evidence
Why the decision came out the way it did: the exact policy and Authority Graph version in force at the time, the enterprise facts it relied on and their provenance, and, where one was issued, the Capability Authorization consumed. Consumption shows the capability was used to attempt the action, not that it completed.
Execution Evidence
What happened downstream: when a separately authenticated destination, or a trusted execution adapter acting on its behalf, reports back, PayReality verifies that report's linkage and reconciles it against what was actually authorized.
Authorized and reported execution, reconciled
PayReality records what it authorized. When a separately authenticated destination, or a trusted execution adapter acting on its behalf, supplies an execution receipt, PayReality verifies that receipt's linkage to the original authorization and reconciles the reported execution against the exact action it authorized. Six outcomes are possible.
The reported execution matches what was authorized.
The reported execution differs from what was authorized.
The destination reported that the action did not execute.
The reported execution matches only part of what was authorized.
No execution receipt has been received for this decision yet.
The available evidence isn't sufficient to resolve a match either way.
A cryptographically authenticated receipt proves what the trusted source reported. It does not independently prove that the underlying business system or real-world event was truthful: reconciliation is only as strong as the execution evidence PayReality actually receives.
Built for the people who have to answer for a decision later
Investigation
Trace any decision back to the exact intent, policy version, and Authority Graph state that produced it, not a summary of what happened, the actual evaluation.
Search
Find decisions by agent, outcome, policy, business unit, or time range. Every field that mattered to the decision is a field you can search on.
Audit
Every record carries a cryptographic signature verifiable in the portal, so an auditor can confirm a record hasn't been altered since it was produced.
Compliance
Roll up decisions by policy, outcome, and time period into the shape a compliance review actually needs, without a separate reporting pipeline.
Evidence lifecycle
Every Allow, Deny, and Human Review outcome produces a record the moment it happens, not a log line reconstructed later from application traces.
Reporting
Export the evidence a specific review needs, scoped to exactly what's relevant, rather than granting broad access to the underlying system.
From database records to portable receipts
A signed Authorization Receipt for every decision is already retrievable through the API today. From here, the Evidence Portal's role is evolving further, toward presenting a portable, independently verifiable artifact that doesn't require access to PayReality's systems to confirm. The portal itself isn't going away; what it's a window into is changing.
See the Evidence Portal on a real decision
We'll walk through a signed decision record end to end, from intent to verifiable evidence.