Language:
PRODUCTS
MORE
Quantum Security 🔍 Search Request Access →
PUBLIC EVIDENCE RECORD

A superseded authority reached T0.
It did not reach execution.

immo.quick Serverless Edition · Sealed Evidence Receipt · August 2026

Originating challenge: Authority Supersession at T-1 to T0

THE AUTHORITY WAS VALID YESTERDAY. AT T0, IT WAS NOT. THE SYSTEM REFUSED TO EXECUTE.

Don't believe it. Verify it.

THE RESULT

Four outcomes, exactly as they stand in the final evidence receipt.

VERDICT
BLOCK_DERIVATIVE_AUTHORITY_SUPERSEDED
EXECUTION RESULT
ZERO_ACTION_ENFORCED
COMMIT STATE
COMMIT_BLOCKED_NO_STATE_CHANGE
FINAL CLOSURE
No state change. No execution. No downstream cascade. Block is total and deterministic.
IT DID NOT ESCALATE. IT DID NOT WARN. IT DID NOT SCORE THE RISK. IT BLOCKED.
THE CLAIM

A superseded authority cannot authorize execution at T0.

PROVEN
  • Authority supersession flag persisted
  • T0 authority check detected active supersession
  • Gate execution returned deterministic block
  • Commit was prevented
  • Zero-action closure was recorded
NOT PROVEN
  • Real-world FinCEN source freshness
  • A real regulatory revocation
  • Authenticity of a live external authority source
  • Legal validity of the synthetic scenario

NO CLAIM BEYOND THE EVIDENCE.

PROVENANCE OF THE CHALLENGE

TA-14 originated the challenge. immo.quick produced the proof.

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.

ORIGIN OF CHALLENGE
TA-14 admissible-execution work
ARTIFACT PRODUCER
immo.quick Global
EXECUTION ENVIRONMENT
immo.quick Serverless Edition
ARTIFACT STATUS
Publicly verifiable immo.quick Public Evidence Record
TA-14 STATUS
Not TA-14 built, not TA-14 reviewed, not jointly developed and not Exchange-governed.

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.

INSTITUTIONAL COMMUNICATION BOUNDARY

Institutional evidence requires attributable institutional communication.

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.

THE FORENSIC TIMELINE

From sealing to block, every step timestamped.

T-2 - EVIDENCE STATE SEALED
A seed receipt is created and cryptographically sealed. The initial receipt establishes the authority provenance against which the later supersession is evaluated.
CTA-TA14DEMO-1786271739069
T-1 - AUTHORITY SUPERSEDED
The authority attached to the receipt is superseded. The engine creates an AUTHORITY_SUPERSEDED flag and binds the superseded authority provenance to the execution chain.
2026-08-09T10:35:39.640Z
T0 - AUTHORITY STATE RESOLVED
Before execution, the authority chain is evaluated. The engine detects the active supersession and returns BLOCK_DERIVATIVE_AUTHORITY_SUPERSEDED. The authority state is therefore not merely logged after execution. It controls whether execution is permitted to occur at all.
T0 - COMPLIANCE GATE EVALUATED
The underlying gate conditions themselves return PASS. That is precisely why the demonstration matters. The compliance layer can be green while the authority layer is no longer admissible. The engine therefore does not allow the prior PASS to override the superseded authority state.

A compliant transaction with invalid authority is still an invalid execution.

WHY THIS MATTERS

A deterministic system can still be wrong.

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.

THE SURFACE QUESTION
Did the gate execute correctly?
THE DEEPER QUESTION
Was the authority still valid when execution was attempted?
SYNTHETIC INPUTS, REAL EXECUTION PATH

The data is synthetic. The execution path is not.

SYNTHETIC FIXTURES
  • Target entity: TA 14 Demonstration Entity
  • UBO: John Doe - 100%
  • Authority event: synthetic regulatory revocation

No real legal entity, natural person, or regulatory action is represented by those fixtures.

PRODUCTION EXECUTION PATH
  • checkAuthorityChainAtT0 - production T0 validation
  • authorityChainPropagation - production authority propagation
  • gateCTA - production gate logic
  • HMAC-SHA256 sealing, SHA-256 Merkle-chain linking
  • Ed25519 + ML-DSA-65 public signature envelope

The receipt explicitly declares that no mock, stub, or demonstration-specific substitute was used for these listed execution components.

PUBLIC CRYPTOGRAPHIC VERIFICATION

Do not trust this page. Verify the artifact.

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.

SEALED EVIDENCE RECEIPT
EVID-TA14-1786271739069
Download complete JSON

Offline verification available - No account - No API - No shared secret

Download the offline verification script (verify-evidence.mjs)

npm install @noble/curves @noble/post-quantum @noble/hashes
node verify-evidence.mjs EVID-TA14-1786271739069.json
...
Ed25519 - RFC 8032...
ML-DSA-65 - FIPS 204...
Hybrid binding...
Final verdictBLOCK_DERIVATIVE_AUTHORITY_SUPERSEDED
Execution resultZERO_ACTION_ENFORCED

Cryptographic verification establishes integrity and signature validity. It does not expand the declared evidentiary claim boundary.

PUBLIC RECEIPT HASH (PAYLOAD)
4bd89432feb4bee8a66009a6265cb863841ed738e0e9256532ef910947cc5e0b

Download the artifact. Verify the signatures. Compare the hash. Challenge the evidence.

VERIFICATION SPECIFICATION
Signed objectevidence_receipt.payload_hash (hex-encoded)
CanonicalizationNot yet published, see limitation noted below
EncodingLowercase hexadecimal
Payload hashSHA-256
Classical signatureEd25519 · RFC 8032
Post-quantum signatureML-DSA-65 · FIPS 204
ML-DSA contextimmoquick:warranty:v2
Hybrid bindingSHA-256 over the concatenated lowercase hexadecimal representations of the Ed25519 and ML-DSA-65 signatures, encoded exactly as implemented by the verifier.

This table describes only what the published verifier actually does. No RFC 8785 is claimed because none is used.

BUILD PROVENANCE

Version references, not build digests.

EXECUTION RELEASE
SLE-2.0.0-2026-08-09
ARTIFACT VERSION REFERENCE
runSupersessionDemonstration-v2.0.0-2026-08-09
gateCTA - gateCTA-v1.0.0-2026-08-04
authorityChainPropagation - authorityChainPropagation-v1.0.0-2026-08-06
authorityChainGateIntegration - authorityChainGateIntegration-v1.0.0-2026-08-06
genericGateRunner - genericGateRunner-v1.0.0-2026-08-09
forensicCrypto - forensicCrypto-v1.0.0-2026-08-06
hybridSignature - hybridSignature-v2.0.0-2026-08-09
BUILD DIGEST STATUS

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 REVIEW STATUS

The original stays unchanged. External findings sit alongside it.

PUBLIC CRYPTOGRAPHIC VERIFICATION
Available
INDEPENDENT THIRD-PARTY FINDING
Not issued
TA-14 REVIEW
Not performed
TA-14 EXCHANGE GOVERNANCE
Not performed
REGULATORY CERTIFICATION
Not claimed

External findings, if issued in the future, will be published alongside the original artifact without modifying or replacing the original record.

THE EVIDENCE BOUNDARY

One more time, cleanly.

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 RECORD DEMONSTRATES
  • Authority supersession propagation
  • Current authority-state resolution at T0
  • Deterministic execution blocking
  • Commit prevention
  • Zero-action closure
  • Cryptographically sealed evidence
  • Independent public signature verification
THIS RECORD DOES NOT CLAIM
  • A live FinCEN query
  • A real regulatory revocation
  • A real legal entity
  • A legal opinion
  • Regulatory certification
  • Universal proof of all immo.quick capabilities
INDEPENDENT REVIEW

Open for independent review.

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.

A CLAIM CAN BE EDITED. A SEALED EXECUTION CANNOT.

The artifact is public. The signatures are public. The claim boundary is public. The outcome is public.

Download evidence Verify receipt View public evidence records

immo.quick Serverless Edition · Sovereign Compliance Engine

Request Access →