Jurisdiction Tag Router
A jurisdiction-aware routing gate that tags resources and matches them against a policy to determine allow, deny, or escalate — with content-hash integrity.
The problem
/ 01When a resource crosses jurisdictional boundaries, you need a ruleset that tags it with the relevant jurisdictions, hashes the payload for integrity, and deterministically resolves an effect (allow/deny/escalate) with a matched rule and escalation reason where applicable.
What it does
/ 05Sets a policy as an array of rules: jurisdictions[], effect (allow|deny|escalate), optional destination, optional priority.
Returns a policyHash (SHA-256 of the ruleset) and ruleCount.
Tags a resource with optional resourceType/resourceId, required jurisdictions[], optional payloadRefHash — returns tagId and contentHash.
Routes by tagId or jurisdictions: returns matched effect, destination, matched rule, and escalated reason if applicable.
Inspects full policy and a tagged record by ID.
Who it’s for
/ 03- Compliance engineers mapping data residency rules
- Product teams routing cross-border resources
- Security operators auditing jurisdictional policy decisions
In context
/ 01Complements Consent Receipt Registry (consent integrity), Escape Hatch Notarization (exceptions), and the Dual Control Timer (approval gating).