SAFR — Safeguards for Agentic Finance at Runtime

SAFR — Safeguards for Agentic Finance at Runtime — 93% of in-scope requirements covered.

14 requirements · 14 in scope (12 enforced · 2 designed). The 93% is weighted over the in-scope base.

SAFR: requirement → the KYE™ artefact that enforces it

Demo data

You learn: Which requirements KYE™ enforces at runtime and with which artefact. You can: Walk the requirements.

  1. pre-execution-governance · enforced

    Every agentic financial action is governed at runtime BEFORE execution — not only at pre-deployment…

    Audit events: kye.purpose.request.v1, kye.purpose.admissibility.v1 · Constitution: 12 purpose permission

  2. per-step-independent-authority · enforced

    In multi-step agentic workflows the control flow applies to each action independently — an Auto-Execute or…

    Audit events: kye.purpose.admissibility.v1, kye.evidence.decision_map.v1 · Constitution: 12 purpose permission

  3. agent-identity-verification · enforced

    Every proposed action is bound to a recognised, registered agent whose identity is verified against its…

    Audit events: kye.agent.governance.v1, kye.purpose.request.v1 · Constitution: 52 delegated agent binding, 00 index

  4. controls-repository · enforced

    A configurable controls repository — drawn from organisational policy, regulatory requirements, product…

    Audit events: kye.evidence.decision_map.v1, kye.purpose.admissibility.v1 · Constitution: 12 purpose permission, 29 profiles lite

  5. mandate-capability-authority · enforced

    User-delegated authority is captured as an explicit, machine-readable mandate (permitted action types…

    Audit events: kye.purpose.request.v1, kye.agent.governance.v1 · Constitution: 52 delegated agent binding, 12 purpose permission

  6. deterministic-disposition · enforced

    The Disposition Engine evaluates each in-scope action deterministically against the retrieved controls and…

    Audit events: kye.evidence.decision_map.v1 · Constitution: 12 purpose permission

How this widget is built
Demonstrates
KYE™ Compliance Mapping Rail™
Components
  • Framework requirement (clause)
  • Coverage status
  • KYE™ enforcement artefact (event, decision-record field, Evidence Pack™ entry)
Flow
Clause → status → the KYE™ artefact that enforces it, enforced requirements first. Architecture diagram
Used on

Source: BuildFin.AI — "Safeguards for Agentic Finance at Runtime" white paper, Version 1.0, July 2026. Industry reference framework developed through financial-industry collaboration, with lineage in MAS Project MindForge Phase 2 (Executive Handbook + Operationalisation Handbook, Singapore FinTech Festival 2025) and the BuildFin.AI implementation-resources work stream. SAFR is a reference approach, not regulatory guidance or a managed service. · License: The SAFR white paper is published by BuildFin.AI as an industry reference. The KYE™ registry paraphrases each SAFR requirement's intent and cites the SAFR component / section for crosswalk purposes only; it reproduces no substantial text. Mapping is one-directional (SAFR requirement -> KYE™ artefact) and asserts no endorsement by BuildFin.AI or MAS.

By category

CategoryReqsEnforcedDesignedAdvisoryDeferredCoverage
Runtime governance at the point of action22000100%
Agent identity (SAFR component 1)2110075%
Controls repository & mandate (SAFR component 2)22000100%
Deterministic disposition (SAFR component 3)3210083%
Governance envelope (authenticated evidence)11000100%
Immutable audit log (SAFR component 4)11000100%
Substantive human escalation11000100%
Deployment patterns & scope boundary22000100%

Every requirement → the KYE™ artefact that enforces it

IDTitleStatusKYE™ enforcement
safr.pre-execution-governanceEvery agentic financial action is governed at runtime BEFORE execution — not only at pre-deployment validation and not only in a retrospective auditenforcedaudit_events: kye.purpose.request.v1, kye.purpose.admissibility.v1
engines: internal, internal, internal
constitution_refs: constitution/12-PURPOSE-PERMISSION.md
safr.per-step-independent-authorityIn multi-step agentic workflows the control flow applies to each action independently — an Auto-Execute or Observe outcome at one step carries no authority into the nextenforcedaudit_events: kye.purpose.admissibility.v1, kye.evidence.decision_map.v1
engines: internal, internal
constitution_refs: constitution/12-PURPOSE-PERMISSION.md
safr.agent-identity-verificationEvery proposed action is bound to a recognised, registered agent whose identity is verified against its registry entry before any other evaluation proceedsenforcedaudit_events: kye.agent.governance.v1, kye.purpose.request.v1
engines: internal, internal
constitution_refs: constitution/52-DELEGATED-AGENT-BINDING.md, constitution/00-INDEX.md
safr.authoritative-registry-resolutionIn open networks the Agent Identity component resolves which registry is authoritative for the action context and retrieves the appropriate identifier accordinglydesignedaudit_events: kye.agent.governance.v1
engines: internal, internal
constitution_refs: constitution/52-DELEGATED-AGENT-BINDING.md
safr.controls-repositoryA configurable controls repository — drawn from organisational policy, regulatory requirements, product rules, and user-provided authority — is the rulebook every proposed action is checked againstenforcedaudit_events: kye.evidence.decision_map.v1, kye.purpose.admissibility.v1
engines: internal, internal
constitution_refs: constitution/12-PURPOSE-PERMISSION.md, constitution/29-PROFILES-LITE.md
safr.mandate-capability-authorityUser-delegated authority is captured as an explicit, machine-readable mandate (permitted action types, decision logic, escalation conditions, validity period, principal authority); the agent cannot extend the scope of a mandate through its own reasoningenforcedaudit_events: kye.purpose.request.v1, kye.agent.governance.v1
engines: internal
constitution_refs: constitution/52-DELEGATED-AGENT-BINDING.md, constitution/12-PURPOSE-PERMISSION.md
safr.deterministic-dispositionThe Disposition Engine evaluates each in-scope action deterministically against the retrieved controls and produces a bounded outcome calibrated to the risk the action presentsenforcedaudit_events: kye.evidence.decision_map.v1
engines: internal, internal
constitution_refs: constitution/12-PURPOSE-PERMISSION.md
safr.four-outcome-dispositionEvery proposed action resolves to exactly one of four outcomes — Deny, Escalate, Auto-Execute, or Observeenforcedaudit_events: kye.evidence.decision_map.v1, kye.purpose.admissibility.v1
engines: internal
constitution_refs: constitution/12-PURPOSE-PERMISSION.md
safr.risk-calibrated-outcomeOutcome assignment is calibrated to the risk profile of the action using factors such as reversibility, financial materiality, customer impact severity, regulatory sensitivity, and novelty/anomalydesignedaudit_events: kye.evidence.decision_map.v1
engines: internal, internal
constitution_refs: constitution/12-PURPOSE-PERMISSION.md, constitution/25-EDGE-GOVERNANCE.md
safr.governance-envelope-authenticatedEach action is packaged in a governance envelope (action + reasoning/action-trace + context metadata) before assessment, and the envelope is authenticated against its origin — not merely treated as a record of what the agent reportedenforcedaudit_events: kye.evidence.tool_call.v1, kye.evidence.pack.v1, kye.replay.context_seal.v1
engines: internal, internal
constitution_refs: constitution/13-RESILIENCE-LOOP.md, constitution/52-DELEGATED-AGENT-BINDING.md
safr.immutable-audit-logEvery governance decision produces an entry in an immutable, tamper-evident, append-only audit log that captures the complete history of every action and every decision, reconstructable without relying on the agent's own accountenforcedaudit_events: kye.evidence.pack.v1, kye.replay.proof.v1
engines: internal, internal, internal
constitution_refs: constitution/30-AUDIT-WORM-RETENTION.md, constitution/13-RESILIENCE-LOOP.md
safr.substantive-human-escalationEscalation to a human reviewer is substantive rather than nominal — bounded escalation volume, a timeout window that defaults to block or senior escalation on no decision, and reviewers with authority equal to the original agent decisionenforcedaudit_events: kye.purpose.admissibility.v1, kye.compliance.attestation.v1
engines: internal, internal
constitution_refs: constitution/36-GOVERNEDUI.md, constitution/21-DELEGATED-AUDITABILITY.md
safr.native-and-gateway-integrationThe governance layer supports both native instrumentation (the agent emits a governance envelope before each action) and gateway interception (a gateway wraps outbound API calls) without requiring changes to agent codeenforcedaudit_events: kye.evidence.tool_call.v1, kye.purpose.request.v1
engines: internal, internal
constitution_refs: constitution/16-EDGE-RUNTIME.md, constitution/52-DELEGATED-AGENT-BINDING.md
safr.decision-not-settlement-boundaryThe governance layer governs the DECISION to act — distinct from settlement rails (which move value) and LLM guardrails (which shape model output); these layers are complementary, not interchangeable, and the decision layer operates after content filtering and before executionenforcedaudit_events: kye.evidence.decision_map.v1
engines: internal
constitution_refs: constitution/00-INDEX.md, constitution/12-PURPOSE-PERMISSION.md

Canonical KYE™ surfaces referenced on this page: KYE Protocol™.