Studio · Jurisdiction Tag Router Live demo

Try live

Tag a resource with jurisdictions, match against a policy ruleset, and resolve an effect (allow/deny/escalate). Not legal advice, not geo-blocking, not sanctions screening.

Not legal advice, not geo-blocking, not sanctions screening. The demo host runs in isolation — nothing is stored.

Demo host: isolated demo host set by your deployment

Jurisdiction Tag Router · Agents & policy

Set policy → tag → route

Checking host…

Define policy rules (jurisdictions + allow/deny/escalate), tag a resource with jurisdictions, then resolve an effect by tag ID or live jurisdictions.

Not legal advice, not geo-blocking, not sanctions screening. The demo host runs in isolation — nothing is stored.

Policy

Rules JSON *

Tag a resource

Resource type (optional) Resource ID (optional) Jurisdictions * Payload ref hash (optional)

Resolve route

Route by the last tag ID (auto-filled) or by entering jurisdictions directly for an immediate, stateless resolution.

Tag ID Jurisdictions (alt)

Operator and workspace consoles are separate applications (pilot).

Policy

Tag a resource

Resolve route

Result