Language:
PRODUCTS▾
Home Core Serverless Edition Why It’s Different CDS — Constitutional Screening STFL — Sovereign Transaction Finance Layer Defence 🏰 Verify Security All Gates
MORE▾
ASSURANCE
Execution Rights Capabilities Authoritative Sources Evidence Evidence Registry Fortress Baseline Adversarial Verification Machine Law Evolution
SOLUTIONS
Institutions Jurisdictions Due Diligence
RESOURCES
Facts Press Newsroom FAQ Machine Law — The Book Gate SDK Gamechangers The Sound of Machine Law
COMMERCIAL
Pricing Investors
Quantum Security 🔍 Search Request Access →
gateElectionIntegrity — Election Integrity Gate
// IMMO.QUICK · GATEELECTIONINTEGRITY · BWAHLGV · § 25 PARTG · § 108A STGB · DSA ART. 34/35

No certified device, no vote capture.

gateElectionIntegrity forensically seals that an election passes four clusters, voting-machine certification, party-donation transparency, tally integrity, and platform reporting, before a vote is captured, a donation accepted, or a result transmitted. Support for electoral authorities, never a replacement for a regulator's own recognition as evidence.

Request Access → See the architecture
In one sentence: gateElectionIntegrity deterministically checks voting machines, party donations, and tally chains before they take effect, rather than investigating them afterward.
✓ RELEVANT IF...
  • You operate or certify voting software, voting machines, or tallying systems
  • You need to check party donations against the tiered notification and publication duties
✕ NOT RELEVANT IF...
  • You expect the Federal Returning Officer to automatically recognise the result as an official election result
  • No election, party donation, or vote count is involved
// The problem

Elections could previously only be checked after the fact, once the vote was already over.

Voting machines, party donations, and vote counts could previously only be checked after the fact. gateElectionIntegrity turns the protection process ninety degrees and checks all four clusters synchronously before anything happens.

No third option: valid or legally void
A donation that touches a threshold without fulfilling the associated duty is not sanctioned after the fact, it is simply never accepted. The previously customary after-the-fact publication duty disappears, because there is no longer a state in between.
// 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
Voting-Machine Certification
Requires the cryptographic hashes of the BSI certificate and software version against a fixed format specification. A missing certificate, damaged seal, or subsequently altered software version blocks deployment.
bsi_certificate_hash · device_seal_intact · software_version_hash
CLUSTER 2
Party-Donation Transparency
Checks every donation against the four hard-coded thresholds of §25 PartG (€10,000 notification, €35,000 immediate publication, €3,300 cash-payment ban, non-EU origin ban) and blocks acceptance if the associated duty is unmet.
donation_amount_eur · threshold_tier · origin_country · duty_fulfilled
CLUSTER 3
Tally Integrity
Requires an unbroken hash chain of interim results and proof of the four-eyes principle for every capture under §108a StGB and §31g BWahlG. A reported manipulation attempt is not just blocked, it is flagged as a criminal offence.
tally_hash_chain_intact · four_eyes_confirmed · manipulation_flag
CLUSTER 4
Platform Reporting Duty
Compares the detection time of a disinformation or manipulation campaign with the notification time to the Federal Returning Officer. If notification occurs more than 24 hours after detection, the gate blocks.
detection_timestamp · notification_timestamp · hours_elapsed
Fatal test case: tally hash chain broken
A federal constituency reports a broken hash chain of interim results. BLOCK_E3_TALLY_INTEGRITY_BREACH fires before the result is transmitted, the suspected manipulation is additionally flagged as a criminal offence.
// 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
NRW state election, valid BSI certificate, €8,000 donation below reporting threshold, unbroken hash chainPASSPASSPASSPASSELECTION_INTEGRITY_SEALED412ms
Federal constituency, tally hash chain brokenPASSPASSFAILnot evaluatedBLOCK_E3_TALLY_INTEGRITY_BREACH588ms
Cryptographic chain continuation
Every test produces a deterministic receipt_id (VAR-ELEC-{TENANT}-{SEQ}), an input_snapshot_hash, an HMAC-SHA256 signature, and a merkle_link to the previous receipt. Timestamps are supplied exclusively by the caller, never derived from the system clock. Sanctions screening runs live via the OpenSanctions API. Any exception to a block requires six-eyes approval. External trust anchors (TSA timestamp, Shamir quorum signature) are attached asynchronously and carry PENDING status until then.
// Clarification

What gateElectionIntegrity is not.

  • Not automatic recognition by the Federal Returning Officer. The gate delivers a cryptographic proof, not an official election determination.
  • Not an independent voting machine or tallying software. The gate seals the check, it does not replace existing election infrastructure.

For electoral authorities that want to make device, donation, and tally integrity provable.

Request Access → access@immoquick.eu
Request Access →