Language:
PRODUCTS▾
Home Core Serverless EditionHealthcare Why It’s DifferentExecution RightsGlobal Requirements CDS — Constitutional Screening STFL — Sovereign Transaction Finance Layer Verify Security All Gates
SECTORS▾
All SectorsHealthcareDefenceAviationHeavy IndustryFinancial MarketsAsset Management & Securities FinancingPharma & Clinical TrialsLogisticsSport & MotorsportMusic & Digital MarketsEnergy & ESGPublic SectorSociety & AdministrationAI · Data · Cyber · TelecomReal Estate & TransactionsAgriFood & Food Safety
MORE▾
ASSURANCE
Authority Surface Execution RightsOverride Accountability Capabilities Authoritative Sources Evidence Evidence Registry Fortress Baseline Adversarial Verification Machine Law Evolution
SOLUTIONS
Institutions Regulators Governments Investors · PE Jurisdictions Due Diligence
RESOURCES
Facts Press Newsroom FAQ Machine Law Gate SDK Public Documentation The Sound of Machine Law
COMMERCIAL
Pricing
Quantum Security 🔍 Search Request Access →
gateBaselLiquidity, Prudential Banking Domain
// The problem

A breached capital buffer is the death of a bank.

If a bank's liquidity ratio or hard core capital falls below the regulatory threshold, immediate intervention by the European Central Bank looms. gateBaselLiquidity does not monitor capital buffers after the fact, it deterministically locks the outflow at T=0 if the transaction would breach the buffer.

No capital call, no ECB intervention, no bank failure
Because the triggering transaction is physically blocked before the capital buffer is breached, no capital call and no immediate supervisory intervention arises. The T=0 lock prevents the harm, rather than reporting it after the fact.
// Architecture

Four clusters, checked sequentially.

Every cluster is dispositive (material_block_mode: true), a hit blocks bindingly, not merely for documentation. That is the default at this systemic bottleneck.

CLUSTER 1
LCR/NSFR Projection
Calculates the Liquidity Coverage Ratio and Net Stable Funding Ratio after the transaction and compares against the 100% minimum quota.
lcr_projected_pct · nsfr_projected_pct
CLUSTER 2
CET1 Buffer
Compares the CET1 ratio after the transaction against the SREP requirement plus the combined buffer requirement under CRD VI.
cet1_ratio_projected · srep_plus_buffer_requirement
CLUSTER 3
Large Exposure Limit
Checks the single-name exposure after the transaction against the 25%-of-tier-1-capital limit under CRR III Art. 395.
single_name_exposure_pct
CLUSTER 4
SSM Early Warning & BRRD
Checks early-warning indicators, recovery-plan trigger thresholds, and MREL compliance under the SSM Regulation and the BRRD.
early_warning_triggered · mrel_compliant
Fatal test case: LCR slips below 100 percent
A payout of €2.5bn would push the LCR down to 85%, triggering BLOCK_L1_LCR_BELOW_100_PCT. The T=0 outflow lock physically blocks the payment before the capital buffer is breached.
// Test results

Two tested scenarios.

All values on this page are fictional test data and serve only to illustrate the gate logic.

Scenario C1C2C3C4 Verdict Latency
LBBW €1.5bn payout, LCR 142%→118%, CET1 12.5%→10.8%, exposure 22%PASSPASSPASSPASSBASEL_LIQUIDITY_SEALED653ms
Commerzbank €2.5bn, LCR→85%, CET1→7.4%, exposure 38%FAILnot evaluatednot evaluatednot evaluatedBLOCK_L1_LCR_BELOW_100_PCT352ms
Cryptographic chain continuation
Every test produces a deterministic receipt_id (VAR-BASL-{TENANT}-{SEQ}), an input_snapshot_hash, an HMAC-SHA256 signature, and a merkle_link to the previous receipt. Persistence occurs in the BaselLiquidityReceipt entity with a 10-year retention period.
// Clarification

What gateBaselLiquidity is not.

  • Not automatic recognition by the ECB, EBA, or BaFin. The gate delivers a cryptographic proof, not supervisory approval.
  • Not an independent treasury or regulatory-reporting system. The gate seals the pre-check, it does not replace existing regulatory reporting.

For banks and regulators that want to make capital-buffer impacts provable before execution.

Request Access → access@immoquick.eu
// SEVEN SUB-GATES

From a narrower liquidity domain to a substantially broader Prudential Banking Domain.

C1
Own Funds / Capital Requirements
C2
Liquidity Requirements
C3
Leverage Ratio
C4
Large Exposures
C5
Prudential Reporting / Disclosure
C6
Supervisory / Governance State
C7
Trade Finance Off-Balance-Sheet Positions
INSTRUMENT NAME DOES NOT DETERMINE PRUDENTIAL TREATMENT.
INSTRUMENT → ECONOMIC / LEGAL CHARACTER → ANNEX I BUCKET → ART. 111 CCF → REGULATORY EXPOSURE VALUE → LARGE EXPOSURE DETERMINATION
GATE CATALOG · REGULATORY DETERMINATION DOMAIN

gateBaselLiquidity

gateBaselLiquidity determines encoded capital, liquidity, exposure and prudential conditions for a defined financial action. The gate contributes a bound regulatory determination state; it creates neither regulatory authority nor Execution Permission.

DOMAIN_DETERMINATION_ONLY = true · EXECUTION_AUTHORITY = false · EXECUTION_PERMISSION = false
Explore Gate Catalog →Execution Rights →
gateBaselLiquidity regulatory determination domain
AUTHORITY BOUNDARY

PRUDENTIAL STATE IS NOT SUPERVISORY AUTHORITY.

CAN

  • deterministically evaluate encoded regulatory conditions
  • bind determinations to source, scope, time and input state
  • surface missing, expired or conflicting regulatory dependencies
  • produce attributable evidence for the concrete determination

CANNOT

  • replace a regulator, supervisor, court or competent institution
  • create legal or regulatory authority through score, consensus, AI or administration
  • turn a gate PASS into an Execution Right on its own
  • mint an ExecutionCapabilityToken on its own
REGULATORY STATE

Regulatory determination is evidence. Not regulatory authority.

SOURCE

Authoritative source

The relevant rule must originate outside the system from a legitimate normative or institutional source.

SCOPE

Defined matter

The determination is limited to the encoded subject, entity, transaction or operation under review.

TIME

Point-in-time state

Effective dates, transition periods, expiry and version state remain explicit.

INPUT

Canonical input

A reproducible determination requires a defined canonical input state.

DEPENDENCY

Dependencies

Missing or contradictory dependencies remain visible rather than being converted into invented permission.

EVIDENCE

Bound evidence

The resulting state can be bound to source, input, scope and time for later verification.

RELATED DETERMINATION DOMAINS

Regulatory domains compose. They do not confer authority on one another.

gateCentralBankReservegateBRRDgateBankingCompliancegateEUFinance

Only scope-relevant determinations become dependencies in Execution Rights resolution. The links shown are not a universally mandatory sequence.

EXECUTION RIGHTS

Five dimensions. Regulatory state can inform them; no gate replaces them.

AAUTHORITY
RRULE
JJURISDICTION
TTIME
DDEPENDENCY
ALL FIVE REQUIRED DIMENSIONS VALID → VALID EXECUTION RIGHT · ANY REQUIRED DIMENSION ABSENT → NO VALID EXECUTION RIGHT → NO CAPABILITY → NO EXECUTION
INVARIANT

A regulatory PASS is a determination. Never a permission by itself.

AUTHORITY → DETERMINATION → EXECUTION RIGHTS → CAPABILITY OR NONE → EXECUTION OR NONE → EVIDENCE

Request Access →