The jurisdictions are part of the risk envelope, and each one derives its own control set from the same corpus. One specification produces different safeguards in different regions.
Akka Verify derives the obligation set per jurisdiction from a corpus of 190 AI regulations and 1,230 controls. A platform team in Singapore and an actuarial team in Italy receive different controls with the same mechanism vocabulary, on one platform.
The matrix derives differently for the EU AI Act, the China Generative AI Interim Measures, Italian AI Law Article 4, the Colorado AI Act, Texas TRAIGA, India DPDP, the Korea AI Act, California SB-53, NY RAISE, GDPR Chapter V and DORA.
Function, data, decision authority and consequence narrow the list further, so two systems running in one country can carry different obligations. Region decides which rows of the corpus are reachable at all.
The specification, the component model and the evidence record are identical in every region. A team changes the jurisdictions in the risk envelope and inherits the rest of the specification unchanged.
Full-parity sovereign deployment keeps traffic and data in-region while preserving HA and DR, across China, Hong Kong, Singapore, North America, Canada and the EU. Manulife rolled Akka out to 2,000 developers across 6 countries under central risk control.
Each jurisdiction contributes its rows to the same matrix. The runtime enforces the union of those rows, and the evidence record shows which authority each control answers to.
A regional team edits the risk envelope and keeps the rest of the specification. The controls that apply in Singapore and the controls that apply in Ontario compile from one specification into different runtime safeguards.
Industry presets shorten the derivation to about half a day. A preset carries the frameworks that dominate a sector in that jurisdiction.
The runtime reconstructs an Eval Matrix from the controls the deployed code enforces and compares it against the signed matrix, reporting missing rows, orphan rows and drift on demand.
The monthly corpus watch detects the change and scopes the review to the rows it affects in that jurisdiction. Regions the change does not reach carry on unaltered.