In one sentence: Core is the instance that runs in your own infrastructure (TEE, your cloud, air-gapped) and runs every decision through 9 deterministic gates before it counts.
✓ THIS IS FOR YOU IF...
The instance needs to run in your own TEE/cloud (AWS Nitro, Azure Confidential Computing) — not with a third party
'Probably correct' isn't enough — you need a formally proven 0% false-approval rate
An auditor or regulator must still be able to reconstruct what happened on day X, even 5 years later
× NOT FOR YOU IF...
You just want to test an API quickly without setting up your own servers → look at Serverless Edition instead
You don't need post-quantum-secure, court-admissible proof
DEPE_PROOF.json
{
"artifact_id": "ART-2026-84291"
"verdict": "PASS"
"gates_passed": 9
"crypto": "ML-DSA-65"
"pq_safe": true
"bi_temporal": true
"latency_ms": 53
"frameworks": 23
"jurisdictions": 53
"worm_block": #84291
"merkle_root": "a3f7c9d2..."
}
<43ms
0
7
53
Left: overview and status. Right: the technical flow of the T=0 execution lock.
⚠ BILL — NOT YET IN FORCE
§30(2a) OWiG (new) is part of the government bill BT-Drs. 21/6133 implementing EU Directive 2024/1203 (cabinet approval 29 April 2026, first Bundestag reading 11 June 2026, currently with the committees, the Bundesrat's 12 June 2026 statement in BT-Drs. 21/6668 not yet finally addressed). No entry-into-force date is confirmed, and the wording may still change during the further legislative process. The SLE attestation described here prepares companies for the foreseeable legal position, it does not replace current legal advice and does not establish an already-existing legal entitlement.
✗Corporate fine up to €40M under §30 OWiG — full amount, no proof of effective prevention
✗Compliance manual documents intent — not the moment of actual prevention
✗EU Directive 2024/1203: once an environmental offence is physically executed, fine reduction is barely enforceable after the fact
✓ WITH SLE ATTESTATION
✓compliance_attestation.sle_eligible = true — cryptographically sealed before physical batch release
✓proof_standard = DETERMINISTIC_T0_EXECUTION_LOCK — prevention at T=0, not asserted retroactively
✓legal_benefit field in the audit trail: fine reduction or case dismissal, documented per incident
✓EU Directive 2024/1203 as an algorithm-bound norm — rule-version-hash-bound in the algoSig
✓
gateHeavyIndustry carries SUB-GATE 5 as the direct hit, but EU Directive 2024/1203 and §30(2a) OWiG (new) are additionally anchored as an algorithm-bound normative reference in gateAgriFood, gateEsgSocial and gateProcurement, rule-version-hash-bound in the algoSig and in the applied_norms field of every audit trail. Four new verdicts are live: BLOCK_H5_ENVIRONMENTAL_CRIME_PERMIT_INVALID, _PERMIT_EXPIRED, _NO_PRENOTIFICATION, _ECOSYSTEM_PERMIT_MISSING.
--d --h --m --s
01.01.2027 · 00:00:00 UTC
✓You receive your personal receipt as primary evidence — HMAC-SHA256, expires_never: true
✓No hardware setup on our part — Core is hardware-bound, provided by the acquirer
✓Exclusively under NDA · Bilateral · By invitation
VORHER — KLASSISCHE COMPLIANCE
The institution bears the burden of proof
PDF reports · Manually created logs No cryptographic binding Contestable · Backdatable · Manipulable Months · €500k–2M · No certainty
One layer above: Gate 0.The nine gates above check secondary law, AML, sanctions, DORA, NIS2, GDPR. Gate 0 sits one level higher and answers a single binary question in advance: does a documented fundamental rights collision exist for this jurisdiction and transaction combination? Optionally activated at tenant level, not a replacement for Gates 1 through 9, but their constitutional foundation.
