Proof of Record
A structured record of how an execution unfolded: lifecycle states, provider interactions, wallet balance transitions, ledger entries and timestamped execution context.
Trust · Auditability
When an outcome is questioned by a customer, an operator or an auditor, the answer should already exist. Orangepill links the steps of each financial operation into one reviewable record instead of leaving them across logs, provider portals and spreadsheets.
Problem
A typical investigation means pulling the request from one system, the provider response from another, and the balance change from a third, then hoping the timestamps line up. Nothing connects the authority that allowed an action to the effect it had.
What is recorded
A structured record of how an execution unfolded: lifecycle states, provider interactions, wallet balance transitions, ledger entries and timestamped execution context.
The path from the original intent through each attempt to the resulting ledger effect, so an outcome can be followed back to the request that caused it.
What each provider reported, kept as observations. Provider responses inform the record; they are not silently treated as established fact.
Which policy and authority permitted an action. For software agents, the scope and limits they acted within are part of what explains the outcome.
When a case escalates to a person, Resolve is designed to keep the decision, the disposition and the authority behind it with the case, separate from the remediation the owning system executes.
Traceability
Proof of Record explains how an outcome was produced. It does not replace the ledger: the ledger remains the authoritative financial state, and the record is the evidence of how that state came to be.
We will show what its record would contain if it had run through the runtime.