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 →
gateWhistleblowerProtection — Whistleblower Protection Gate
// IMMO.QUICK · GATEWHISTLEBLOWERPROTECTION · HINSCHG · EU-RL 2019/1937

A leaked identity halts admissibility.

gateWhistleblowerProtection forensically seals that a reporting channel passes four clusters, channel integrity, deadline compliance, retaliation protection, and confidentiality, turning legal duties into cryptographic prerequisites. Support for companies and authorities, never a replacement for a regulator's own recognition as evidence.

Request Access → See the architecture
In one sentence: gateWhistleblowerProtection technically enforces what the law only demands legally, an anonymous channel, respected deadlines, sealed retaliation correlation, protected identity.
✓ RELEVANT IF...
  • You operate an internal reporting channel under whistleblower protection law
  • You need to forensically document retaliation against whistleblowers
✕ NOT RELEVANT IF...
  • You expect a supervisory authority to automatically recognise the result as legal compliance
  • No internal reporting channel or whistleblower report is involved
// The problem

A technically weak reporting channel is legally worthless.

Whistleblower protection law demands anonymous channels, fixed deadlines, and retaliation protection on paper. gateWhistleblowerProtection turns these duties into cryptographic prerequisites, technically enforced rather than merely legally expected.

The evidence is presented to the employer, not just the burden of proof
The law reverses the burden of proof in retaliation cases. The gate goes further: it automatically detects the temporal correlation between a report and a subsequent measure and seals it as forensic evidence, the employer is not just under the burden of proof, the evidence already exists.
// 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
Channel Integrity
Checks three conditions: cryptographic anonymisation, encryption, complete access log. If any condition is missing, the gate blocks the channel.
anonymization_verified · encryption_verified · access_log_complete
CLUSTER 2
Deadline Compliance
Deterministically monitors the seven-day deadline for acknowledgement of receipt and the three-month deadline for substantive feedback under §17 HinSchG.
acknowledgment_days · feedback_months
CLUSTER 3
Retaliation Protection
Detects temporal correlations between a report and subsequent employment actions (dismissal, transfer, pay cut) and seals this correlation as forensic evidence supporting the statutory reversal of the burden of proof.
report_timestamp · adverse_action_timestamp · correlation_flag
CLUSTER 4
Confidentiality
Ensures the whistleblower's identity is disclosed only to authorised persons. A breach triggers immediate blocking plus alerting, the party responsible is forensically identified.
identity_disclosure_authorized · breach_detected
Fatal test case: dismissal four days after report
A dismissal occurs four days after a report. BLOCK_W3_RETALIATION_CORRELATION_DETECTED seals the temporal correlation as forensic evidence, before the dismissal could become legally usable.
// 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
Report received, deadline met, no retaliation detectedPASSPASSPASSPASSWHISTLEBLOWER_PROTECTION_SEALED367ms
Dismissal four days after reportPASSPASSFAILnot evaluatedBLOCK_W3_RETALIATION_CORRELATION_DETECTED410ms
Cryptographic chain continuation
Every test produces a deterministic receipt_id (VAR-WHIS-{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 gateWhistleblowerProtection is not.

  • Not automatic recognition by a supervisory or labour authority. The gate delivers a cryptographic proof, not regulatory confirmation of legal compliance.
  • Not an independent whistleblower system. The gate seals the channel and deadline check, it does not replace an existing reporting-channel provider.

For companies and authorities that want to make whistleblower protection provable technically, not just legally.

Request Access → access@immoquick.eu
Request Access →