gateDefence
gateDefence determines encoded Defence & Security conditions for a defined action. It is a Determination Domain — not a licensing authority, not a permit issuer and not Execution Permission.
The gate does not decide whether execution is allowed.
CAN
- determine applicable encoded sector conditions
- compose relevant specialised gate determinations as dependencies
- surface missing authority, licence, role, time or jurisdiction evidence
- produce a GateProofBundle as evidence input
CANNOT
- create governmental authority
- issue an export or procurement permit
- mint an ExecutionCapabilityToken on its own
- govern the Execution Plane or reinterpret law
Sector state is bound to the concrete action.
Action & purpose
Which technical, contractual or operational action is proposed and what defined purpose does it serve?
Parties & roles
Identities, roles, recipients, suppliers, controlling entities and relevant authority credentials.
Items, technology & data
Classification and scope of affected items, technology, software or controlled data.
Jurisdictions
Relevant legal territories, transit locations, domicile states, destination states and other territorial bindings.
Permits & sources
Existing permits, contractual authority and provable normative sources. The gate does not create them.
Time & dependencies
Validity windows, versions, prerequisites and outputs of specialised Determination Domains.
Specialised gates remain specialised.
gateDefence does not replace these domains. It binds the determinations relevant to the concrete scope into a sector determination state that may then become evidence input to Execution Rights resolution.
Five dimensions. Complete closure required.
Four hard separations before effect.
gateDefence remains a Determination Domain. Authorization for a concrete consequence-bearing defence action is resolved only at the separate Execution Rights boundary and only when all required Authority, Rule, Jurisdiction, Time and Dependency states are closed.