Genuine receipts generated by the immo.quick system and publicly accessible evidence. Explore their underlying determinations, results and available verification paths.
Treasury factoring and constitutional screening with clearly stated verification limits.
A documented financial assessment and capability-issuance record. Its actual execution timestamp is null: issuance is not evidence that the factoring action took place.
TREASURY-FACTOR-RECEIVABLE-9d852bbe369130d1
Treasury receipt · open public JSON extract ↗Open verification portal ↗A rule-based screening of a legislative text using catalog GG-GATE0-FORENSIC-v7.0. Three potential constitutional collision areas were flagged. This is a screening result, not a court ruling.
GG0-MT5UWWTC-IZ0SH
Open original receipt (JSON) ↗Open verification portal ↗This Evidence Library presents genuine system-generated immo.quick receipts. The Treasury original exists as a system receipt; the linked public JSON case extract contains selected fields from it. The Constitutional JSON is the published original record of the documented screening. Inspect the available artifacts and their verification data through the public evidence and verification paths. Each receipt establishes its specific recorded event: a determination, capability issuance and actual execution are distinct states.
Gate PASS is not execution permission. Capability issuance is not actual execution.
The treasury original remains outside this public site package; only an explicitly labeled case summary is published. Back to the public evidence registry ↗
A receipt records a specific state or event. Assessment therefore depends on more than verifiable integrity: it requires identifying the event that is bound and the sources, rules and execution data available.
A gate establishes whether its formally defined conditions are satisfied. A PASS does not grant an execution right on its own.
Authority, rule state, jurisdiction, time and mandatory dependencies must align for the specific action.
A narrowly bound technical permission may follow from a valid execution right. Issuance does not prove that execution occurred.
Only evidence of the completed action establishes execution. Integrity alone guarantees neither source truth nor legal recognition.
A receipt binds its stated event to particular inputs, rules and states. Its fields show whether it records a domain review, capability issuance or execution.
No. A gate result establishes its defined domain conditions. A valid execution right requires the complete applicable authority and condition resolution.
This depends on the method and published verification data. Public signatures can be checked with available keys; HMAC requires the relevant secret key or an appropriate verification service.
Each artifact now has its own public evidence page. State, verdict, time, execution boundary, cryptographic binding and claim boundary are explained in readable form while the unchanged original JSON remains directly accessible.
immo.quick separates domain determination, institutional reliance, execution rights, technical capability, actual execution and resulting evidence. This prevents a positive check from becoming execution permission by implication and prevents an earlier valid state from being carried forward without revalidation. Each stage answers a different institutional question and has its own evidentiary boundary.
A regulatory, technical or domain-specific condition is deterministically established.
PASS ≠ EXECUTION PERMISSIONThe receiving institution decides whether an existing artifact may be relied upon for its specific purpose.
EVIDENCE ≠ RELIANCEAuthority, Rule, Jurisdiction, Time and material Dependencies must close for the exact consequence under the current state.
RELIANCE ≠ EXECUTION RIGHTOnly a valid Execution Right may produce a narrowly scoped, bound and, where applicable, single-use Capability.
RIGHT ≠ EXECUTED ACTIONThe authoritative state is revalidated immediately before effect. Material changes before the Execution Cut can prevent execution.
CONTINUING AUTHORITYThe governing state, permitted or refused effect and resulting proof chain are preserved as distinct evidence.
PROOF ≠ SOURCE OF LEGITIMACYA banking domain receipt records a sealed domain state while explicitly stating that no execution permission is created.
View artifactBANKING_SEALED · execution_permission=falseA subsequent receipt records a sanctions match. The earlier positive state remains historical evidence but cannot be carried forward as standing permission.
Open BLOCK receiptBLOCK_SANCTIONS_MATCH · chain_integrity=VALIDA separate Reliance Decision Record shows that an existing proof does not automatically become institutionally usable.
View Reliance artifactdecision=REFUSE · reliance_granted=false