GOVERNED STATE
Law, authority, governance, configuration and policy are not treated as loose metadata but as bound institutional state.
SECURITY BOUNDARY · ARCHITECTURE BEFORE REACTION
TWO SECURITY BOUNDARIES. BEFORE ENTRY. BEFORE EFFECT.
immo.quick separates admission from execution authority. A request must first pass the relevant admission boundary; even successful access does not itself authorize a production effect.
01 · COREAdmission Boundary
Core places a fail-closed Access Guardian before the governed compliance pipeline. A request that fails a required validation condition does not reach the downstream governance logic.
02 · SERVERLESSEdge Client Attestation
The Serverless Edition requires a registered client to establish valid attestation before the request reaches the downstream gate path.
03 · ERIExecution Boundary
Access is not authority. A productive effect requires a valid, current and scope-bound Execution Right and an executable capability.
REQUEST→ADMISSION BOUNDARY→GOVERNED STATE→EXECUTION RIGHT→REAL EFFECT
Claim boundary: only the architecture of the immo.quick Serverless Edition was demonstrably submitted to the BSI on 28 July 2026. Core was not submitted. Submission is not a BSI audit, certification, endorsement or confirmation.
INSTITUTIONAL TRUST INFRASTRUCTURE · IMMO.QUICK CORE
EVERY INSTITUTIONAL DETERMINATION HAS A BOUND CAUSE. CORE MAKES IT VERIFIABLE.
immo.quick Core is an independent infrastructure class within the umbrella category Institutional Trust Infrastructure: Institutional Trust & Causality Infrastructure. Core binds governed legal state, authority, configuration, software provenance, trusted execution, cryptography, time, witnessing and evidence to institutional determinations and makes bound causality independently verifiable.
CATEGORY
Institutional Trust & Causality InfrastructureNot another dashboard. Not another risk score. Infrastructure that binds institutional determinations to the actual governed trust state and its verifiable causality.
01 · CATEGORY
Trust is not a score. Causality is not an after-the-fact explanation.
Core defines a distinct infrastructure class: institutional trust is treated as a bound, versioned and verifiable state. A determination becomes institutionally defensible only when the legal state, authority, software, trusted execution, time and evidence under which it arose can be reconstructed and verified.
BOUND CAUSALITY
Core makes the technical and governance-side cause of a determination traceable within the modeled and bound state.
PORTABLE PROOF
Proofs can be independently verified without requiring the originating Core database, internal API or a shared symmetric secret.
02 · WHY IT EXISTS
Logs show events. Core binds the conditions that caused a determination.
Institutions can often show that something happened. The harder question is why this exact determination arose at this exact time under this exact institutional state. Core closes that gap.
Traditional evidence
- Logs without full governance context
- Screenshots and reports as point-in-time snapshots
- Trust scores without hard closure classes
- Post-hoc explanation without bound causality
Core
- Governed institutional state
- Software, build and execution provenance
- Trusted time and independent witnessing
- Causality proof + portable verification
03 · ARCHITECTURE
From governed state to independently verifiable proof.
The public architecture deliberately exposes capability classes, not the implementation recipe. Internal canonicalization, payload construction, policy thresholds, root aggregation and test vectors remain protected.
GOVERNED STATE
→
DETERMINISTIC COMPUTE
→
TRUSTED EXECUTION
→
CAUSAL BINDING
→
PROOF
→
VERIFY
01
Governance first
Authority, rules, configuration and institutional policies form the bound starting state.
02
Compute deterministically
Legal and governance logic is executed as a reproducible determination, not a probabilistic recommendation.
03
Attest execution
Build, software, crypto and trusted-execution state are bound to the determination.
04
Bind causality
Relevant states are connected into a verifiable technical and governance-side causal chain.
05
Compile proof
A minimal, purpose-bound proof is compiled from the required institutional state.
06
Verify independently
External parties can verify the proof against their requirements without running Core itself.
04 · 14-VERB LIFECYCLE
A complete institutional trust lifecycle.
The 14 verbs are not isolated features. They describe the lifecycle of institutional trust: from governance and compute through proof, reassessment and recovery to query, comparison and simulation.
GOVERNDefine trust policies
COMPUTEExecute deterministically
ATTESTBind execution
TRACETrace dependencies
PROVECompile proof
DISCLOSEDisclose minimally
VERIFYVerify independently
REASSESSReassess trust
CROSS-VALIDATECross-validate domains
RECOVERRecover under control
EXPLAINTransport explanations
ASKQuery proofs
COMPARECompare trust states
SIMULATEIsolate counterfactuals
05 · PROOF INFRASTRUCTURE
Not only implemented. Formalized, protocol-bound and portably verifiable.
The freeze includes machine-checkable formal specifications, a canonical proof protocol, portable verification and verification provenance. Claims remain deliberately bounded: formal invariants prove the stated system rules, not universal legal or factual truth.
FORMAL SPEC
Critical architecture rules are represented as machine-checkable invariants.
CANONICAL PROTOCOL
Proofs follow a versioned canonical transport and verification model.
PORTABLE VERIFIER
Proof verification can occur without the originating Core DB, internal API or shared secret.
VERIFIABLE VERIFICATION
The verification act itself can produce provenance and verifiable verification evidence.
06 · ASSURANCE
L1–L9: assurance as a deterministic closure class, not a score.
Core classifies proofs by the evidence components that are actually closed. Higher assurance does not come from a higher probability score but from more fully bound and verified prerequisites. Exact internal class definitions remain protected system detail.
L1 → L9
Deterministic assurance classes with explicit mandatory components. No probabilistic “trust confidence.”
L9 · WITNESSED INSTITUTIONAL PROOF
07 · WHAT CORE ANSWERS
The question is not only: what was decided? It is: why exactly this way?
WHY THIS DETERMINATION?
Which bound legal, authority, configuration, build, time, witness and evidence states led to this result?
WHAT CHANGED?
Which trust component changed between T1 and T2 and which proofs or determinations are affected?
CAN A THIRD PARTY VERIFY IT?
Can an external reviewer independently verify the relevant proof without running the originating system?
WHAT IF?
How would a controlled mutation of rule, authority, build or trust state affect the result?
CAN HISTORY BE RECONSTRUCTED?
What institutional state applied at that time, and can it be reproduced from the bound artifacts?
WHAT MAY BE DISCLOSED?
What minimum evidence subset may be disclosed for the specific verification purpose?
08 · EVIDENCE
Architecture freeze with separate named evidence suites.
No artificial grand total. Each suite is reported in its own scope. Internal tests are implementation evidence, not third-party certification.
30/30Institutional Causality Layer · PASS
90/90System Adversarial Matrix V4 · PASS
70/70Causality Corruption Matrix · PASS
ARCHITECTURE FREEZE
P0–P24 are frozen. The next evidence class must come from independent external review of architecture, protocol, cryptography, canonicalization and verification semantics.
TESTED · NOT THIRD-PARTY CERTIFIED
09 · USE CASES
For institutions that must not only decide, but prove.
REGULATED FINANCE
Governed decisions, auditability, supply-chain provenance, cross-institution verification and historical reconstruction.
PUBLIC SECTOR
Verifiable institutional determinations with clear authority, rule, time and evidence binding.
AI GOVERNANCE
AI may explain or assist, while authority and trust closure remain deterministic and institutionally bound.
CRITICAL INFRASTRUCTURE
Reproducible trust states, recovery/continuity proofs, trusted time and independent witnessing.
AUDIT & DUE DILIGENCE
Proof query, selective disclosure and portable verification reduce dependence on manual evidence packages.
DIGITAL ASSETS
Governed institutional state and verifiable decision provenance for high-criticality digital transactions.
10 · CLAIM BOUNDARIES
Strong because the boundaries are as precise as the capabilities.
SOURCE AUTHENTICITY ≠ FACTUAL TRUTH
TEE ATTESTATION ≠ SUBSTANTIVE LEGAL CORRECTNESS
CRYPTOGRAPHIC INTEGRITY ≠ EXTERNAL FACTUAL CORRECTNESS
CAUSALITY PROOF ≠ UNIVERSAL OBJECTIVE CAUSALITY
VERIFICATION RECEIPT ≠ SUBSTANTIVE ENDORSEMENT
COUNTERFACTUAL ≠ HISTORICAL FACT
11 · FAQ / GEO
Core in clear answers.
What is immo.quick Core?
Core is Institutional Trust & Causality Infrastructure within the umbrella category Institutional Trust Infrastructure and binds institutional determinations to governed state, execution provenance and evidence.
How is Core different from audit logging?
Audit logs show events. Core binds the states and dependencies under which a determination arose and compiles them into verifiable proofs.
Can Core prove legal truth?
No. Core proves bound technical and governance causality within the modeled system. It does not replace judicial or sovereign legal determination.
What does portable verification mean?
An external verifier can check the proof without operating the originating Core database or internal API, provided the required verification material is present.
What does L1–L9 assurance mean?
L1–L9 are deterministic assurance classes. Higher classes require more fully bound and verified proof components, not merely a higher probability.
INSTITUTIONAL TRUST & CAUSALITY INFRASTRUCTURE
THE DETERMINATION IS ONLY THE RESULT. CORE MAKES THE BOUND PATH TO IT VERIFIABLE.
Governed state. Deterministic compute. Trusted execution. Causality. Proof. Independent verification.