AI-BOUNDARY-2.0 · 2026-11-02
The immo.quick Serverless Edition checks the protected execution path immediately before the called function runs its first instruction. This boundary applies to human calls as well as calls from functions and workflows. It does not grant an AI agent an execution right. The publisher reported the following internally tested state on 2 November 2026.
The overview reads its state from runtime checks: integrity seal and audit chain, cryptographic schemes, permitted connection destinations, logins and sessions, key provenance without key values, runtime permissions and the AI boundary. A snapshot can be captured with a receipt.
Each handling step is recorded with a receipt. The system calculates configured reporting deadlines and records the authority and case reference. A human submits the notification. An incident can only be closed once all required notifications are recorded. The statutory timing anchors and scope limits are explained below the cards.
An administrator can end all sessions of an account together. Only the owner can end the owner’s sessions. Session revocation remains a separate access control.
Every use of AI must be registered. Unregistered use is rejected. Verdicts and approvals are removed from AI responses. An AI response establishes neither a domain approval nor an execution right.
AI never holds an execution right in this system. There is therefore no AI kill switch as a system feature. Immediately before a protected execution function runs its first instruction, the runtime checks the input. A call by an AI agent, or AI-origin input without human confirmation for that exact function, is rejected. The rejected operation is not executed. Its rejection receives a receipt recording BLOCK, the function reference and “nothing executed”. Human confirmation does not replace other authority or execution checks.
An AI agent’s proposals have no direct effect. The agent cannot call an execution function, cause a data change or grant approval. It never becomes an administrator. Only the owner may designate an account as an AI agent.
The reported software bill of materials contains 746 components, each with a pinned version and checksum. This inventory is version-specific and is not an external security certification.
The publisher reports a fully passing internal test suite and 46 AI guardrail checks, including adversarial tests. Rejection tests observed no database writes by the rejected execution path. The rejection receipt documents this boundary; it is not execution permission. An external penetration test has not yet been performed. Internal tests replace neither that assessment nor certification.
Login: the second factor is disabled in the reported state by the owner’s decision. This is a documented operating setting, not a statement that institutional authentication requirements have been met.
For significant incidents, the general sequence is an early warning within 24 hours and an incident notification within 72 hours of awareness. The final report is due within one month after the incident notification. Ongoing incidents and trust services have specific rules; applicable national implementation governs.
EUR-Lex · NIS2 · Article 23Initial notification as early as possible, within four hours of classification as a major ICT-related incident and generally within 24 hours of awareness. If classification occurs after those 24 hours, the four-hour period runs from classification. Statutory follow-up reporting deadlines must be considered separately.
EUR-Lex · DORA · Delegated Regulation (EU) 2025/301, Article 5A notifiable personal data breach must be reported without undue delay and, where feasible, within 72 hours of awareness. The exception for breaches unlikely to pose a risk, and the requirement to explain a late notification, remain applicable.
EUR-Lex · GDPR · Article 33Cybersecurity · Serverless Edition™
Whoever connects the Serverless Edition through its own API gets the protection automatically. No add-on module, no security tier at extra cost. Every request passes the same protective layers, every check ends in a signed receipt, and every error is reported visibly instead of being swallowed.
IN OPERATION
The institutional API is a separate machine protocol. Machine access is never treated as an administrator session. Refused requests are logged, repeated failures per sender are throttled.
IN OPERATION
Every request has a fixed size limit, institutional requests at most 16 KB. Transfers that are too slow are aborted. This protects against overload by oversized or deliberately delayed requests.
IN OPERATION
The System connects only to destinations listed in the sealed code or the configuration. Internal and private networks are blocked, every redirect is checked on its own, every block is logged. This prevents attacks that try to use the System as a stepping stone (SSRF).
IN OPERATION
At start-up the System checks every program file against a sealed manifest. In enforcement mode it refuses to start on any deviation instead of running with altered code.
IN OPERATION
Where no rule exists, only an administrator has access. The rule registers themselves are locked against direct changes, even for administrators. Changes only go through three approvals by different people.
IN OPERATION
Failed login attempts are counted and limited. Sessions expire after a fixed time.
IN OPERATION
Security-relevant events go into an audit log that can only be appended to and is linked as a hash chain. Any later change is detected.
IN OPERATION
Every check ends in a receipt with Ed25519 and ML-DSA-87, chained with SHA-384. The daily root additionally carries SLH-DSA-SHA2-256s. A receipt is valid only if both signatures verify.
IN OPERATION
If a scheme is marked as compromised, the System immediately stops issuing with it. Instead there is a technical abort with a failure record and an alarm.
IN OPERATION
Keys are exchanged with X25519 and ML-KEM-1024 (FIPS 203), against today’s and future attacks.
IN OPERATION
Every night the System checks its evidence chains. If a chain breaks, a critical alarm is raised for each affected record before retention deadlines apply.
IN OPERATION
Signing keys are generated locally, never displayed and never transmitted. Without them the System issues no receipt.
IN OPERATION: runs in the current System state. BUILT IN · ACTIVE AFTER SETUP: present and tested, becomes active with your configuration.
IN OPERATION
A security incident is captured with a forensic receipt and reported internally to the security team. The official report to the BSI is made through its reporting form; the receipt is the evidence for it.
IN OPERATION
The System prepares reports under DORA (initial report within 4 hours) and NIS2 (within 24 hours). Every field comes from signed System data. What is not yet established is shown as “not yet determined”, never estimated.
IN OPERATION
If the Cyber Resilience Act check warns or blocks, the System automatically creates the draft report through a specifically authorised service identity, exactly once per incident.
BUILT IN · ACTIVE AFTER SETUP
Security events go to your SIEM in Common Event Format (CEF) as soon as its address is configured.
IN OPERATION
External vulnerability reports are accepted through a fixed channel and confirmed with a receipt.
The same API also checks your obligations. Every check ends in its own receipt.
gateNIS2
gateDORA
gateCRA
gateCER
gateTechStandards
gateAIHighRiskConformity
gateDataAct
gateEUDPF