Multi-jurisdiction

Last updated Jun 14, 2026

Day-1 Matter ships US-DE entity formation. The Templates surface was built from M1 to support future jurisdictions as a data add, not a schema migration.

Two primitives carry the jurisdiction story:

jurisdiction_scope.json per template revision

{
  "applies_in": ["US-DE", "US-CA", "US-NY"],
  "required": [],
  "variants": {
    "US-CA": { "jurisdiction_variant_id": "jvr_california_specific" },
    "US-NY": { "jurisdiction_variant_id": "jvr_new_york_specific" }
  }
}

• applies_in: [] — unconstrained; template is renderable in any jurisdiction.
• required: ["US-DE"] — restricted (e.g. DGCL-specific consents). Rendering against US-CA returns 409 jurisdiction_not_supported_by_template.
• variants — IDs of JurisdictionVariant rows that carry jurisdiction-specific overrides.

JurisdictionVariant

Per (template_revision_id, jurisdiction), a structured override payload:

{
  "object": "jurisdiction_variant",
  "id": "jvr_california_specific",
  "template_revision_id": "trv_initial_board_resolution_2026_06_01",
  "jurisdiction": "US-CA",
  "clause_overrides": {
    "annual_meeting_quorum": { "value": "majority_present_in_person" }
  },
  "signer_overrides": {
    "sole_director": { "witnesses_required": { "count": 1, "capacity": "witness" } }
  },
  "legal_basis_overrides": {}
}

The variant applies between the platform body and any org overlay:

Platform body  →  Jurisdiction Variant  →  Org overlay  →  Entity overlay

This ordering matters: an org overlay tuned for US-DE rendering should not have to know about California's witness requirements. The variant applies those automatically when the render targets US-CA.

Regulatory-regime tuples

Signer roles declare allowed regulatory regimes:

{
  "role": "incorporator",
  "legal_bases": [
    { "regulatory_regime": "esign_ueta_us", "legal_basis_within_regime": "ueta_electronic_agent" },
    { "regulatory_regime": "esign_ueta_us", "legal_basis_within_regime": "esra_consent" },
    { "regulatory_regime": "wet_witness",    "legal_basis_within_regime": "wet_signature_witness" }
  ]
}

regulatory_regime reserves slots for eidas_eu and eta_sg ahead of the M6 EU + Singapore rollout. Adding a regime activates new legal_basis values without rebuilding the schema.

Roadmap

The Org.data_residency_region column (added in M0) supports the geographic split: an EU-residency org's renders execute in eu-central-1 workers, and their archive bundles land in eu-central-1 Object Lock with cross-region replication to eu-west-1 for DR.

See also

• MCTF format — the jurisdiction_scope.json file shape.
• Customization — how org / entity overlays compose on top of the variant.