01 · OBSERVATION
What happened?Logs, reports and telemetry can make activity visible. Visibility is valuable, but it does not itself create or withdraw execution permission.
MACHINE LAW™ · EXECUTION RIGHTS™ INFRASTRUCTURE
The control boundary between capability and execution rights™.
An Execution Right answers a specific question: may this actor perform this action on this target under the conditions that apply now? The Serverless Edition™ resolves the required authority, rules and dependencies into a bound execution state. An individual successful check cannot substitute for that complete evaluation.
02 · PREDICTION
What may happen?Models can estimate risk, drift or consequence. Probability can inform a determination, but probability is not institutional authority.
03 · INTERVENTION
Can trajectory be changed?Escalation, pause and override can preserve governability. An intervention right is still not the same thing as the right behind the original execution.
04 · AUTHORIZATION
May this action exist?Machine Law™ closes the relevant authority state for the exact action. If required closure is absent, no valid bounded capability should follow in the governed execution path.
EXECUTION RIGHTS™ INFRASTRUCTURE · FROZEN ARCHITECTURE
ARCHITECTURE FREEZE = TRUE
The Execution Rights™ architecture is formalized, hardened and frozen. Rights closure, bounded capabilities, registered execution surfaces, current-right revalidation, replay protection, reassessment and portable verification form one fail-closed control chain.
REQUEST → DETERMINATIONS → RIGHTS CLOSURE → EXECUTION RIGHT → BOUNDED CAPABILITY → ENFORCEMENT → EXECUTION → EVIDENCE
NO VALID EXECUTION RIGHT → NO CAPABILITY → NO EXECUTIONInternal architecture freeze of a tested implementation. Not third-party certification.
HARDENING CLOSURE · 11 SEPTEMBER 2026
The enforcement boundary is closed — within the currently executed test scope.
The previously open nonce-reuse vector was closed in the central production enforcement path. Replay validation, nonce consumption, corruption verification, global conformance and the freeze decision now use bound fail-closed states rather than independent green indicators.
14 / 14CORRUPTION VECTORS BLOCKED
0 failed · nonce_reuse → EXECUTION_DENIED.
191GLOBAL ENFORCEMENT V3
Applicable variants across 10 registered production execution surfaces.
9 / 9CONFORMANCE V2
Suites passed · overall_pass = true.
TRUEARCHITECTURE_FREEZE
Only when control conditions and binding global conformance both pass.
Persistent single-use nonce authority. consumeExecutionNonce is the single source-of-truth for capability status, the persistent nonce store and atomic claim-and-consume. A previously consumed nonce returns NONCE_ALREADY_CONSUMED and cannot authorize productive effect again.
CONFORMANCE_FAILURE ⇒ ARCHITECTURE_FREEZE = FALSE · ALL_REQUIRED_CONTROLS_PASS ∧ GLOBAL_CONFORMANCE_PASS ⇒ ARCHITECTURE_FREEZE = TRUE
Internal technical verification of the current implemented state. Not third-party certification, not a claim of universal invulnerability, and not a statement about unmodeled attack vectors.
GLOBAL EXECUTION REQUIREMENTS
Regulation is moving toward execution.
FINMA, BaFin, NIST, NSA, EU and U.S. government strategies are converging on continuous authorization, Zero Trust, resilience, evidence and enforceable boundaries. See how immo.quick already operationalizes these control properties at the Execution Rights™ layer.
THE ARCHITECTURAL DIFFERENCE
Governability is not authorization.
An enterprise can remain observable, manageable and even interruptible while the authorization question is still unresolved. immo.quick separates those layers instead of treating them as one.
AUTHORITATIVE SOURCE→RULE STATE→JURISDICTION→TIME→DEPENDENCIES→DETERMINATION→EXECUTION-RIGHTS CLOSURE→CAPABILITY / NONE→EVIDENCE
WHAT THE MACHINE MAY DO
Determine, bind, constrain and evidence.The architecture can process encoded rules and authoritative states, resolve required conditions, bind a capability to the supported authorization state and preserve evidence within explicit claim boundaries.
WHAT THE MACHINE MAY NOT INVENT
Authority, legal sovereignty or substantive truth.Institutional authority originates outside the machine. A Gate Judgment is not an Execution Right. Cryptographic integrity is not a legal judgment.
Intervention can stop execution. Execution Rights™ determine whether a valid capability may exist in the first place.
WHY THIS MATTERS NOW
Autonomous software compresses the distance between decision and consequence.
As agents and automated systems touch payments, regulated workflows, clinical processes, critical infrastructure and public-sector execution, a retrospective explanation becomes less valuable than a provable boundary before action. The institutional problem is no longer only whether software can act. It is whether software can demonstrate the authority under which that action became executable.
BOARD / CRO
Control exposure before consequence.Separate responsibility on paper from the technical conditions that create an executable capability.
REGULATOR / AUDITOR
Inspect the authorization path.Trace authority, rule state, dependencies and evidence without asking a model to become the sovereign decision-maker.
CFO / INVESTOR / PE
Look below compliance software.Execution failures can become remediation, legal, operational and balance-sheet exposure. The diligence question is whether the control layer is structural, inspectable and difficult to substitute.
INSTITUTIONAL ENTRY POINTS
One architecture. Different institutional questions.
InstitutionsExecution authorization, bounded capability and evidence.RegulatorsInspectable authority and claim boundaries.GovernmentsLegislative assurance with sovereign human judgment preserved.Investors & PEInfrastructure position, defensibility and institutional demand drivers.VerifyPublic proof surfaces and independent evidence checks.
immo.quick does not claim that software creates legal or sovereign authority. The architecture binds execution to externally legitimate authority and publishes the boundary of what its evidence can establish.
CURRENT ERI AUDIT · ADVERSARIAL + GLOBAL ENFORCEMENT
FORGE THE CAPABILITY. BYPASS THE CLOSURE. RACE THE STATE. REPLAY THE CAPABILITY.
The Execution Rights™ Infrastructure was tested beyond the happy path. The audit deliberately attacks capability bindings, closure, state transitions, dependency graphs and runtime invariants. The objective is not probabilistic robustness, but deterministic fail-closed behavior.
191GLOBAL ENFORCEMENT V3 APPLICABLE VARIANTS · 10 SURFACES
Global Enforcement
39/39 tests passed. 0 bypass paths detected in tested scope. A non-Spine capability is blocked with SPINE_ISSUANCE_REQUIRED.
Capability Forgery
Manipulating action, subject, executor, validity, state references, scope, max_uses, environment or determination hash → INVALID_CAPABILITY_BINDING.
Closure Bypass
Four of five closed dimensions are not sufficient. Authority, Rule, Jurisdiction, Time and Dependencies must all close. For physical dependencies, a present measurement or valid signature is also insufficient by itself: ERI-INV-017 and ERI-INV-018 require closed reality-consistency and verified-provenance conditions. Unresolved divergence or provenance that is not explicitly verified blocks fail-closed.
Revocation Race
If authority or dependency state changes between revalidation and execution, the Atomic Execution Check blocks.
Replay Attack · Capability Replay
Re-use of an already consumed capability is deterministically detected and blocked.
Graph Poisoning
Orphan nodes, missing edges, circular dependencies and stale nodes invalidate the dependency graph.
Manifest / Runtime Conformance
Published architecture claims are checked against actual runtime enforcement.
“Replay Attack” explicitly means a cryptographic/technical replay attack here.
An already validly consumed capability is presented again for execution. This is not probabilistic repetition and not an AI re-run. The same capability + same idempotency key returns the already known result; a new execution attempt with a different key after consumption is blocked as REPLAY_DETECTED.
Technical conformance evidence for the tested system state. Not third-party certification and not a claim of absolute invulnerability.
INSTITUTIONAL PROOF PATH
The book about the moment before effect
The Moment Before · Rami Cherri
Machine Law™, AI governance and execution rights™ explained clearly. The English edition has 348 pages. Hardcover, paperback and e-book formats have separate ISBNs and direct links to tredition, Amazon and buecher.de on the book page.
See editions, ISBNs and retailersUnderstand it through a story
In “The Moment Before”, Rami Cherri explains compliance, governance and execution rights™ through a fictional bank story and documented real-world cases.
Explore the book about compliance and governance