One Ledger for Every Consequential Decision
Finance and security decisions run through the same request shape - actor, action, target, context - and land in the same append-only ledger, each with a verdict, a trust score, and a sha256 proof. Many engines, one ledger.
Illustrative product view
Why one ledger matters
Most stacks decide actions in a dozen disconnected places - a payment approval here, an IAM check there - each with its own vocabulary and its own log. When an auditor or an incident asks “who decided this, on what basis, and can you prove it wasn’t changed after the fact?”, the answer is scattered. The Decision Ledger unifies it: every consequential action, whatever engine decided it, is written to one append-only, tenant-scoped table in one canonical shape.
What a ledger row proves
- Who acted - human, service account, or AI agent - resolved to one identity
- What was attempted, on what target, and its blast radius
- The canonical verdict: allow, step-up, hold, or block
- A 0–100 Action Trust Score and its band
- A sha256 seal over the decision, so any later edit is detectable
- The tenant it belongs to - every read is org-scoped
From decision to audit evidence
Because every row is canonical and sealed, a governed decision can become compliance evidence automatically - mapped to the controls it satisfies - instead of being reconstructed by hand before an audit. The ledger is the spine the Trust Center, assurance receipts, and the governed-action evidence loop all read from.
Frequently asked questions
What is the Decision Ledger?
It is a single, append-only, tenant-scoped record of every consequential decision Fintra makes - across finance and security - each written in one canonical shape with a verdict, a trust score, and a tamper-evident sha256 seal.
What does “many engines, one ledger” mean?
Different domains have different decision engines - a finance engine, a security policy decision point - but they all emit the same DecisionRequest/DecisionResponse shape and write to the same ledger, so the audit trail is uniform no matter who decided.
How is a row protected from tampering?
Each decision is sealed with a canonical sha256 hash computed over its contents. Any later change to the stored record breaks the seal, so silent edits are detectable.
Is it multi-tenant safe?
Yes. Every decision is stamped with its organization and every read is scoped to that tenant, enforced at the database with row-level security.
Stay in the loop
One practical finance briefing a week - new guides, checklists, and benchmarks.
Put a decision - with proof - in front of every action
See how Fintra decides allow / step-up / hold / block per action and writes each verdict to a tamper-evident ledger.
Talk to us