immo.quick Serverless Edition · Sealed Evidence Receipt · August 2026
Originating challenge: Authority Supersession at T-1 to T0
Don't believe it. Verify it.
NO CLAIM BEYOND THE EVIDENCE.
This demonstration was initiated in response to an authority-supersession question raised by Greggory Don Butler through TA-14's admissible-execution work. The governance question was specific: deterministic execution can still become inadmissible if the authority supporting execution has been superseded before consequence attaches.
immo.quick independently implemented, executed, sealed and published the resulting demonstration on the immo.quick Serverless Edition.
The artifact should therefore be understood as an immo.quick evidence record produced in response to a TA-14 governance challenge, not as a TA-14 finding, certification, registration or Exchange-governed institutional record. Had the demonstration been developed through the TA-14 AI Governance Exchange, its institutional provenance and review record would be different.
Evidence should preserve origin as carefully as it preserves outcome.
Provenance note based on the public exchange between Greggory Don Butler, Founder of TA-14, and Rami Cherri, Founder & CEO of immo.quick Global, August 2026.
immo.quick does not process system registrations, sealed evidence submissions, cryptographic material or architecture-related transfers through consumer email accounts. For interactions involving immo.quick execution infrastructure, evidence artifacts, registration data or cryptographic material, immo.quick requires an email identity attributable to an institutional domain.
This requirement is part of the immo.quick security and provenance model. It is designed to preserve attributable institutional identity not only inside the evidence artifact, but also across the communication channel through which evidence and system-related material is exchanged.
For this demonstration, no institutionally attributable TA-14 email domain was provided for artifact transfer. immo.quick therefore did not transmit the sealed evidence artifact through the proposed consumer email channel. The demonstration was executed on the immo.quick Serverless Edition and the resulting artifact was instead published as a Public Evidence Record for independent verification.
This boundary does not constitute a judgement on TA-14 or on any specific email provider. It reflects an internal immo.quick security principle governing evidence, registration and architecture-related communications.
INSTITUTIONAL EVIDENCE REQUIRES ATTRIBUTABLE INSTITUTIONAL COMMUNICATION.
AUTHORITY_SUPERSEDED flag and binds the superseded authority provenance to the execution chain.BLOCK_DERIVATIVE_AUTHORITY_SUPERSEDED. The authority state is therefore not merely logged after execution. It controls whether execution is permitted to occur at all.A compliant transaction with invalid authority is still an invalid execution.
If it deterministically executes an obsolete rule, a stale approval, a revoked authority, or an invalid provenance chain. That is why immo.quick separates the causal execution chain from the authority legitimacy chain.
No real legal entity, natural person, or regulatory action is represented by those fixtures.
checkAuthorityChainAtT0 - production T0 validationauthorityChainPropagation - production authority propagationgateCTA - production gate logicThe receipt explicitly declares that no mock, stub, or demonstration-specific substitute was used for these listed execution components.
The final Sealed Evidence Receipt contains a hybrid public signature envelope designed for independent verification without access to the internal HMAC secret. Classical signature: Ed25519 (RFC 8032). Post-quantum signature: ML-DSA-65 (FIPS 204). Hybrid binding: SHA-256 over the concatenated lowercase hexadecimal signature representations.
Offline verification available - No account - No API - No shared secret
Download the offline verification script (verify-evidence.mjs)
Cryptographic verification establishes integrity and signature validity. It does not expand the declared evidentiary claim boundary.
Download the artifact. Verify the signatures. Compare the hash. Challenge the evidence.
This table describes only what the published verifier actually does. No RFC 8785 is claimed because none is used.
CI/CD build digests were not computed for this demonstration. The published identifiers are version references, not SHA-256 build digests.
WE DO NOT LABEL VERSION REFERENCES AS CRYPTOGRAPHIC DIGESTS.
External findings, if issued in the future, will be published alongside the original artifact without modifying or replacing the original record.
WHAT THIS RECORD ESTABLISHES: This record establishes only the bounded claim declared within the artifact. Cryptographic verification establishes integrity, signature validity and consistency with the declared evidence package. It does not constitute legal, regulatory, judicial or third-party certification.
This artifact is publicly available for independent cryptographic and evidentiary examination. Any qualified reviewer may verify the receipt, challenge the declared claim boundary, inspect the causal timeline and test the public signature envelope. External findings will be published alongside the original artifact without replacing or modifying the original record.
The artifact is public. The signatures are public. The claim boundary is public. The outcome is public.
immo.quick Serverless Edition · Sovereign Compliance Engine