OpenChainGraph Suite · CONTRACT A3 · arch #5

SCA, Consent, and FAPI Compliance

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.

Map SCA exemptions, build consent scope, validate FAPI security profile, and generate consent receipts.

OpenChainGraph · 4 Steps compliance mandate Hash-Anchored §4 chain_depth:4 Client-Side · Zero PII
Chain Topology — Sca Exemption Mapper → Consent Dashboard Builder → Fapi Security Validator → Consent Receipt Generator
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Live Execution

This page is the chain definition (plan). To run the chain step by step in your browser, with each step's kernel executing in-page and a composite hash over the outputs, open the live runner:

▶ Run this chain in your browser
Chain Stages · 4 Steps
1 ROOT · D0 catalog
Sca Exemption Mapper 92-sca-exemption-mapper
exemption_map and risk_scores feed T91 consent scope builder
↓
2 D2 catalog
Consent Dashboard Builder 91-consent-dashboard-builder
consent_scope and framework_flags feed T97 FAPI validation
↓
3 D3 catalog
Fapi Security Validator 97-fapi-security-validator
fapi_profile and security_gaps feed T96 consent receipt generation
↓
4 TERMINAL · D4 catalog
Consent Receipt Generator 96-consent-receipt-generator
Exports SCA/consent/FAPI Policy Mandate, final stage
▶ Run this chain (live) browser · real execution · composite §4 hash
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition — no new hash is minted. Available after hash computation.