// IMMO.QUICK · GATEBUNDID · GATE 19 · EIDAS VO 910/2014 · VWVFG

One case file, inseparably bound to one citizen.

gateBundID seals the cryptographically inseparable coupling of a digital administrative act to the eID assertion of the citizen concerned, including Level-of-Assurance checking and authority validity. Support for public authorities, never a replacement for a regulator's own recognition as evidence.

Request Access → See the architecture

In one sentence: gateBundID seals the merge-binding hash, the citizen eID hash, and authority validity into a single receipt, making the merge irrevocable afterward.

✓ RELEVANT IF...

You need to bind digital administrative acts inseparably to an eIDAS eID assertion
You need to forensically prove the Level of Assurance and freshness of an eID assertion

✕ NOT RELEVANT IF...

You expect an authority to automatically recognise the result as evidence
No digital administrative act relating to a citizen is involved

// The problem

A dissolvable coupling would be the antithesis of the certainty requirement.

A digital administrative act concerning a citizen must be cryptographically inseparably coupled to that citizen's eID assertion. If the coupling were dissolvable afterward, a case file could be reassigned to a different citizen without consent, the antithesis of the rule-of-law certainty requirement.

// Architecture

Three sub-gates, inseparably merged.

An expired assertion or a non-competent authority leads to a hard rejection, no exception, no discretion.

SUB-GATE 1

eIDAS eID-Assertion LoA

Checks the eIDAS Level of Assurance (LOW, SUBSTANTIAL, HIGH) and the freshness of the assertion (default freshness window: 5 minutes). A LoA below the required level is rejected.

loa_level · assertion_age_minutes · loa_required

SUB-GATE 2

Administrative Act–eID Merge

Seals the cryptographic merge hash and the citizen eID hash. Together, both form the inseparable binding, a case file can only be read out with exactly this citizen eID.

merge_hash · citizen_eid_hash

SUB-GATE 3

Authority Validity

Confirms that the issuing authority was validly competent at moment T=0. This guards against local and subject-matter incompetence as well as organisational dissolution of the authority.

authority_id · authority_valid_at_t0

// Test results

Six tested scenarios.

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

Scenario	SG1	SG2	SG3	Verdict
Fresh assertion, dispositive	PASS	PASS	PASS	BUNDID_SEALED
Assertion 5 days old	FAIL	not evaluated	not evaluated	BLOCK_BUNDID_ASSERTION_EXPIRED
LoA LOW where SUBSTANTIAL required	FAIL	not evaluated	not evaluated	BLOCK_BUNDID_EID_SUBSTANTIAL_BELOW_REQUIRED
Merge hash missing	PASS	FAIL	not evaluated	NO_DECISION
Authority not competent at T=0	PASS	PASS	FAIL	BLOCK_BUNDID_AUTHORITY_LAPSED
Citizen eID hash missing	PASS	FAIL	not evaluated	NO_DECISION

Test result: after the first, correct rejection, the second run with a fresh assertion reached BUNDID_SEALED in 446 ms. LoA SUBSTANTIAL verified, merge binding and citizen eID sealed, authority BMI_DE valid, material block mode activated.

// Clarification

What gateBundID is not.

Not automatic recognition by an authority. The gate delivers a cryptographic proof, not regulatory admission as evidence.
Not an independent eID provider. The gate checks incoming eIDAS assertions, it does not issue its own eID credentials.

One case file, inseparably bound to one citizen.

A dissolvable coupling would be the antithesis of the certainty requirement.

Three sub-gates, inseparably merged.

Six tested scenarios.

What gateBundID is not.

For public authorities that want to bind digital administrative acts inseparably to citizens.