Skip to content

A rule written once isn't a rule applied everywhere

One rule reaches every app, team and agent below where it's set, in the path of every call. Lower levels can only tighten it. And you see exactly what applies, and why, before and after you save.

The problem

The organisation decides: no customer data to models outside the EU; the marketing teams may use these three models; nobody calls the expensive model from a test environment. The decision is clear. Whether every app actually follows it is not. Some do. Some did, until a refactor. Some never heard about it. And nobody can answer "what rules apply to this key, right now?" without reading code.

Why it stays unsolved

A rule written in a policy document is applied by each app that reads the document. Each team implements it its own way, in its own code, at its own pace. Exceptions are added in one service and forgotten. A new agent ships without any of it. The rule exists, but where it holds is anyone's guess, and there's no single place to look.

How Vidai handles it

Rules live in one place and are applied by the gateway, on every call, before it reaches a model.

flowchart TB
  org["Organisation: Grachtwerk<br/>approved models · no secrets in prompts"] --> env["Environment: production<br/>its own models and key lifetimes"]
  env --> team["Team: Zuiderhoeve Dairy<br/>EU only · its own models"]
  team --> agent["Agent: zuiderhoeve-social-agent<br/>fewer models still"]
  agent --> key["Its key<br/>everything above, combined"]
  • Set at a level, reaches everything below. A rule on the organisation, an environment, a team, an application or an agent applies to every key beneath it, including keys issued tomorrow.
  • Lower levels only tighten. A team can allow fewer models than the organisation, a smaller budget, a stricter guardrail; never more.
  • Every rule says why it exists: compliance, regulatory, internal policy or budget, so the next person knows what it's protecting.
  • See it before you save it. Changing a team's models previews whose keys gain or lose what, before anything changes.
  • See what applies, any time. What applies here shows, for any key, person or team, every rule that reaches it, the level it came from and why.

Policies › What applies here for one key: every rule that reaches it, where each was set, and its purpose

What changes for you

  • "Does every app follow the rule?" has an answer: yes, by construction. The rule isn't in the apps; it's in the path their calls take.
  • New apps and agents are governed from their first call, with nothing for their developers to remember.
  • Exceptions are visible, approved and dated, not hidden in a branch. See Exceptions, overrides and approvals.
  • Proof: open any refused call in Request logs: it names the rule that decided it and where it was set.

A team's models: the preview of whose keys gain or lose which models, before the change is saved