Preserve the sequence.
New events add to the history. Corrections leave the original record in place.
Every decision leaves a record.
Know who acted, which rule applied, and what the evidence supported. Keep the history. Give others a way to check it.
The decision is only part of the story.
A useful record connects the action to its authority and evidence. Keep those connections intact so a review can start with the facts already in place.
Follow the reasoning behind each receipt.
Move from the verdict to the policy and supporting record. Each tells you something different about the same event.
Refund request
Start with what happened.
See the request and its verdict together. A hold is recorded as a hold, with its reason and the action waiting for review.
Finance agentDecision record
- Action
- Refund · $612
- Requested by
- Finance agent
- Decision
- Held for approval
- Reason
- Amount exceeds the approval threshold
Connected to the same governed event
History that holds together.
Receipts join an ordered, append-only chain. Each connects to the one before it, making changes to the recorded sequence detectable.
Check a single receipt.
With transparency enabled, inclusion proofs link a receipt to a signed checkpoint without exposing other receipt contents.
Keep both clocks.
Separate when something happened from when it entered the record.
Orcinta Attest
The record, ready for review.
- Scope
- Finance agent
- Period
- September 1–10, 2026
- Included
- Receipts and evidence coverage
Decision historyIntegrity checksControl mappings
Orcinta Attest
Give reviewers a record they can check.
Bring receipts, reconstruction, coverage, and control mappings into a conformance packet. Scope it to the organization or a specific agent and time window.
Export the packet as a branded PDF. Recipients can check its public verification link without signing in.
Explore the control catalogBe clear about what the evidence says.
A verifiable record should make its boundaries visible. Proof preserves the distinction between a checked action and an observed one.
Checked before execution.
Actions routed through the platform’s enforcement path are subject to governance checks. The record shows whether the request was permitted, held, or denied.
Explore agent governanceRecorded after the fact.
Imported activity can establish what was reported. It cannot prove the action passed governance checks before it happened. Gaps in coverage remain visible.
Explore connected sourcesVerification establishes the integrity of the record. It does not establish that a decision was correct or that a policy was sound.
Have questions?
What does a receipt record?
A receipt records a governed event with its subject, decision, applicable rule reference, event details, and audit link. It carries a sequence number and cryptographic links to the preceding receipt. The connected record provides the actor, supporting evidence, and any approval history available for that event.
How is a receipt different from an activity log?
Receipts connect the event to its governance context and an ordered, append-only chain. Verification recomputes the hashes and checks their links to detect changes to the recorded sequence. The record distinguishes when an event happened from when it entered the record.
What does verification prove?
Receipt proofs establish attribution, integrity, and ordering of the recorded evidence. They do not establish that an action was correct, that a policy was sound, or that all activity was captured. Observed activity remains observed even when its proof verifies. A conformance packet provides evidence for review, not regulatory certification.
Can someone verify a packet without an Orcinta account?
Yes. A conformance packet can include a public verification link that a recipient can use without signing in. The public result is limited to the packet’s verification information, rather than opening access to the workspace. Authorized users can revoke a packet; its public link then stops returning a verified result. Revocation does not recall files already downloaded.
Can we prove one receipt without sharing the rest?
Yes, one receipt can be proven on its own without exposing any other receipt. With transparency publication configured, a receipt can carry a Merkle inclusion proof against a signed checkpoint. The proof uses sibling hashes rather than the contents of other receipts. Independent timestamps and witness cosignatures are optional configured additions. These proofs complement the receipt chain; they do not expand what the underlying evidence establishes.
What happens when a policy changes or activity arrives late?
Earlier receipts retain their rule reference, and policy history preserves earlier versions. Event time and recorded time remain distinct, so a later arrival does not silently become evidence available earlier. Corrections add to the history rather than rewriting the original receipt.
Make the next review start with the record.
Connect a decision to the evidence behind it.