Module · Policy

Compliance, residency, approvals · by rule, not by exception.

Policy is the rule-set of the TokenOne® scheme. It governs the compute decision: which providers, regions, brands (including TokenOne AI), models and aggregators a workload can use. Where Guardrails screen the content of a call, Policy gates which calls happen at all. Use them together.

What it covers

Eleven routing-level controls, configurable per scope.

Policy rules cascade global → tenant → team → project → workflow → model → provider. Lower scope wins. Every decision logged.

Jurisdiction restriction

Restrict workloads to specific countries or regions for regulatory compliance.

Residency requirement

Inference must run in approved regions; logs must land in approved regions.

Provider restriction

Allow- or deny-list providers per workload, project or tenant.

Open-source-only / self-host-only

For sovereign deployments · never route to a closed-weight or hosted model.

Spend caps

Per-request, per-user, per-team, per-workflow caps. Hard or soft, time-windowed.

Approval required

Route into the approval queue before execution. Approver and reason captured.

Reroute

When a rule denies the most efficient path, route to the next available compliant route · never just block.

Restricted task class

Disallow specific task families (e.g. code generation, vision) per scope.

Policy + Guardrails together

Routing-level + content-level. The full picture.

Policy module

Routing-level controls

Decides whether the call can be made at all, and which providers / regions / models are eligible. Runs before the model sees the prompt.

Guardrails module

Content-level controls

Screens the content of the prompt and the response. Catches PII, secrets, injection, leakage, toxicity, hallucination. Runs at the request boundary.

What’s included

Policy capabilities.

  • Declarative rules in JSON or YAML · versioned, replayable, scope-cascaded.
  • Self-serve compliance posture page for tenants · region, retention, providers, model origin, aggregator.
  • Approval queue with full context · who, what, when, why.
  • Audit replay · run a historic decision against a new policy version.
  • Compliance bundles for SOC2, ISO 27001, GDPR, HIPAA-aligned workloads.
  • Drift detection on policy decisions · catch regressions before they hit production.

Compliance, by rule. Not by exception.