gateAMLARegulation
gateAMLARegulation determines encoded AMLA/AML regulatory conditions, scope, subject state and applicable rule dependencies. The gate contributes a bound regulatory determination state; it creates neither regulatory authority nor Execution Permission.
AMLA RULE STATE IS NOT SUPERVISORY AUTHORITY.
CAN
- deterministically evaluate encoded regulatory conditions
- bind determinations to source, scope, time and input state
- surface missing, expired or conflicting regulatory dependencies
- produce attributable evidence for the concrete determination
CANNOT
- replace a regulator, supervisor, court or competent institution
- create legal or regulatory authority through score, consensus, AI or administration
- turn a gate PASS into an Execution Right on its own
- mint an ExecutionCapabilityToken on its own
Regulatory determination is evidence. Not regulatory authority.
Authoritative source
The relevant rule must originate outside the system from a legitimate normative or institutional source.
Defined matter
The determination is limited to the encoded subject, entity, transaction or operation under review.
Point-in-time state
Effective dates, transition periods, expiry and version state remain explicit.
Canonical input
A reproducible determination requires a defined canonical input state.
Dependencies
Missing or contradictory dependencies remain visible rather than being converted into invented permission.
Bound evidence
The resulting state can be bound to source, input, scope and time for later verification.
Regulatory domains compose. They do not confer authority on one another.
Only scope-relevant determinations become dependencies in Execution Rights resolution. The links shown are not a universally mandatory sequence.
Five dimensions. Regulatory state can inform them; no gate replaces them.
A regulatory PASS is a determination. Never a permission by itself.
AUTHORITY → DETERMINATION → EXECUTION RIGHTS → CAPABILITY OR NONE → EXECUTION OR NONE → EVIDENCE