Fintra Feature
One decision contract for the whole enterprise
Decision Fabric
Example figures- REQUEST
- actor, then action, then target
- + context
- ENGINES
- finance · security
- HR next
- RESPONSE
- verdict + trust + proof
- one shape
- Normalize every native verdict
- allow · step_up · hold · block
- Unknown verdict
- fails safe to HOLD
- No engine owns the action
- never a silent allow
- Route by domain
- finance | security | …
The seam that makes a platform a platform
Fintra already decided actions in several places, each with its own verdict words: one engine said “deny recommended,” another “require approval,” a third “step up.” The decision fabric collapses those into one canonical vocabulary and one request/response shape, so a governed action looks the same whether a finance engine or a security policy decision point answered it.
| Native (engine) | Canonical |
|---|---|
| deny_recommended (security PDP) | block |
| require_approval (finance signals) | hold |
| challenge / step_up | step-up |
| allow / allow_with_logging | allow |
| anything unrecognized | hold (fail-safe) |
Fail-closed by construction
- An unknown verdict maps to HOLD: never a silent allow on a consequential action
- If no registered engine owns the request, the fabric refuses rather than defaults open
- A misbehaving engine is skipped by the router, not fatal to the decision path
- Every response is sealed and routed to the one Decision Ledger
Questions people ask
What is the unified decision fabric?
It is a single canonical decision contract (actor, action, target, and context in; a verdict, trust score, and tamper-evident proof out) shared by every domain engine, so consequential actions are decided the same way no matter which engine owns them.
How does it unify different engines’ verdicts?
A normalizer maps each engine’s native verdict (for example deny_recommended, require_approval, challenge) onto one canonical vocabulary: allow, step-up, hold, block. Unknown verdicts fail safe to hold.
What happens if no engine handles an action?
The fabric raises rather than defaulting open. It fails closed: no engine, no silent allow.
Which engines are live?
Two today, the finance decision engine and the Aegis security policy decision point, writing to one Decision Ledger, with additional domains able to register against the same contract.
Keep reading
Calculators
One finance briefing a week
New guides, checklists and benchmarks, by email. Unsubscribe from any issue.
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.