Machine Law did not emerge in a single release. It evolved through a documented sequence of increasingly strict architectural boundaries between analysis, authority, execution and evidence.
This record traces that development from November 2025 through the public disclosure and formal documentation of the Execution Rights Graph in August 2026. The chronology combines permanently archived technical publications, dated public architecture disclosures and independently inspectable evidence surfaces.
This lineage spans two fully independent systems sharing one architectural thought: hardware-backed immo.quick Core as the origin, and immo.quick Serverless Edition as a provider-neutral, hardware-independent architecture designed for maximum scale. Their functional Machine Law models remained closely aligned through June 2026 before Serverless began to diverge more decisively from July onward.
The purpose is not to claim ownership of generic standards, cryptographic primitives or common industry terminology. It is to preserve the documented evolution of the specific immo.quick architecture.
The documented Machine Law lineage begins on 17 November 2025. From this point onward, immo.quick increasingly moved regulatory and institutional conditions out of descriptive workflows and into technically enforced system state.
The architectural question changed:
The first decisive architectural break was the move from observation to enforcement. Non-conforming state was no longer something merely detected and reported. It became something the infrastructure was designed to prevent from progressing.
By February 2026, enforcement had become a broader governance architecture. Terminal Refusal expressed a fundamental idea: certain impermissible states should not merely trigger warnings. They should become structurally non-executable.
At the same time, proof began separating from provider trust.
In March 2026, the earlier enforcement doctrine became a formal architectural category. Machine Law distinguished itself from systems that merely observe, score or retrospectively explain.
Enforcement alone was no longer enough. The system now had to preserve independently verifiable evidence of both positive and negative paths.
By June 2026, immo.quick Core and immo.quick Serverless Edition represented two fully independent technical systems built around the same underlying Machine Law principle. Core was the hardware-backed origin: deterministic institutional infrastructure built around TEEs, enclaves and hardware-supported assurance. Serverless followed a fundamentally different architecture, designed without dependence on that hardware model and optimized for provider neutrality and maximum horizontal scalability.
At this point, their functional governance and proof models remained closely aligned. Both systems produced cryptographically bound evidence and receipts. The distinction was therefore not yet primarily what they enforced, but how the underlying infrastructure was constructed.
From July 2026 onward, Serverless increasingly expands the authorization architecture already present from inception. SCP-1.0, STFL and CDS strengthen proof, provenance and authority resolution around that existing execution-right foundation. In August, this architecture becomes publicly named, machine-verifiable and formally documented.
This finally changes the architectural question. No longer: did the checks pass? Instead:
The Execution Rights architecture was not published immediately after its initial implementation. Over several months, the underlying authorization model was expanded and subjected to adversarial Red-Team testing, boundary-condition testing and extreme stress testing before public disclosure. Execution Rights Manipulation is today one of the publicly named attack families of the ongoing Adversarial Verification suite.
View Adversarial Verification →
The architectural trajectory is consistent: each stage removes another source of unproven discretion between authoritative state and institutional consequence.
HOW THE TWO SYSTEMS DEVELOPED IN RELATION TO EACH OTHER
Core established the original deterministic institutional architecture around formal governance models, consequence boundaries, cryptographic evidence, bi-temporal state, institutional verification and hardware-supported assurance through TEEs and enclaves.
Serverless does not depend on Core's hardware-based trust architecture. Execution Rights were part of the Serverless authorization foundation from inception. SCP-1.0, STFL, CDS, public verification and Authority Supersession progressively hardened, expanded and exposed that architecture before its formal public disclosure in August 2026.
Core and Serverless are not versions of the same system. They are fully independent architectures that share the same underlying Machine Law thought. Core was the origin, the hardware-backed foundation on which the earliest deterministic governance and proof concepts were established. Serverless pursued the same fundamental objective through a different architectural model, designed from the outset for provider neutrality and maximum horizontal scalability.
Until June 2026, both systems remained closely aligned in their functional governance, enforcement and proof logic. From July 2026 onward, Serverless began to diverge more decisively, developing its own proof standards, public verification surfaces and ultimately the Execution Rights authorization model.
| Date | Disclosure | System | Type | Permanent Record |
|---|---|---|---|---|
| 17 Nov 2025 | Genesis of deterministic governance lineage | immo.quick | Architecture | Internal/Public Record |
| 17 Dec 2025 | Active Defense | immo.quick | Architecture | Documented |
| 18 Dec 2025 | Deterministic Enforcement over Stochastic Prediction | immo.quick | Architecture | Documented |
| 29 Mar 2026 | Machine Law v1.0 | Core | DOI | 19301212 |
| 30 Mar 2026 | Machine Law v1.1 | Core | DOI | 19328229 |
| 1 Apr 2026 | v1.2 | Core | DOI | 19361101 |
| 4 Apr 2026 | v1.3 | Core | DOI | 19420763 |
| 7 Apr 2026 | v1.4 | Core | DOI | 19457223 |
| APR–JUN 2026 · TWO SYSTEMS. ONE THOUGHT · Architecture Lineage | ||||
| 8 Apr 2026 | Serverless v1 | Serverless | DOI | 19462893 |
| 14 Apr 2026 | Regulatory Specification | Core | DOI | 19565734 |
| 17 Apr 2026 | State 1 | Core | DOI | 19634279 |
| 26 Apr 2026 | Core 2.0 | Core | DOI | 19799660 |
| 2 May 2026 | Core 2.1 | Core | DOI | 19969948 |
| 8 May 2026 | Core 2.2 | Core | DOI | 20078326 |
| 23 May 2026 | Core 2.3 | Core | DOI | 20355497 |
| 25 May 2026 | SEF | Core | DOI | 20386349 |
| 5 Jun 2026 | Core 2.4 | Core | DOI | 20562464 |
| 5 Jun 2026 | Serverless 1.1 | Serverless | DOI | 20562673 |
| 17 Jun 2026 | Serverless 2.0 | Serverless | DOI | 20736877 |
| 22 Jun 2026 | The Layer No One Is Talking About | Serverless | Protocol Article | |
| 26 Jun 2026 | STFL Article | Serverless | Protocol Article | |
| FROM JUL 2026 · SERVERLESS ARCHITECTURAL DIVERGENCE · Architecture Lineage | ||||
| 1 Jul 2026 | SCP-1.0 | Serverless | DOI | 21112798 |
| 1 Jul 2026 | STFL | Serverless | DOI | 21113308 |
| 3 Jul 2026 | CDS | Serverless | DOI | 21153394 |
| 29 Jul 2026 | Executive Liability article | Machine Law | Protocol Article | |
| 4 Aug 2026 | The Scaling Machine | Serverless | Protocol Article | |
| 7/8 Aug 2026 | Capability Manifest | Serverless | Public Evidence | Manifest |
| 9 Aug 2026 | TA-14 | Serverless | Public Evidence | Evidence Record |
| 10 Aug 2026 | From Proof to Execution Rights | Serverless | Protocol Article | |
| 11 Aug 2026 | Execution Rights Architecture Reference | Serverless | Architecture Reference | Public |
This chronology documents the development and public disclosure of the immo.quick architecture. It does not assert proprietary ownership over generic cryptographic primitives, open standards, standard URI conventions, common software-engineering practices or abstract concepts independently developed elsewhere.
References to architectural priority concern the specific documented immo.quick formulations, system structures, named architectural objects and their dated public disclosure.