NewEvery agent tool call now routes through the governed MCP gateway — policy check, audit log, then dispatch.Read the changelogarrow_forward
XOOZLYAI Orchestrator
routeHow it workssmart_toyAgent fleetshieldGovernance & trustsellPricingmenu_bookDocsarticleBloghistoryChangelog
Log inStart free
grid_viewProductsrouteHow it workssmart_toyAgent fleetshieldGovernance & trustsellPricingmenu_bookDocsarticleBloghistoryChangelogHelp centreLog in
Start free
  1. XOOZLY
  2. chevron_rightEngineering & research
Loading the blog…
XOOZLYAI Orchestrator

Ready to orchestrate your AI fleet with total confidence?

Start a project, set a cost cap, and watch the loop run with every tool call policy-checked and logged before it leaves the platform.

Start freearrow_forwardSee what shipped
  • check_circleNo credit card required
  • check_circleYour keys, your model spend
  • check_circleEvery tool call audited

Platform

  • All productsarrow_forward
  • Orchestration looparrow_forward
  • Agent fleetarrow_forward
  • Governed control planearrow_forward
  • Pricingarrow_forward

Trust & legal

  • Trust centrearrow_forward
  • Security & compliancearrow_forward
  • AI use policyarrow_forward
  • Report a vulnerabilityarrow_forward
  • Data subject requestsarrow_forward

Resources

  • Documentation & guidesarrow_forward
  • Engineering & research blogarrow_forward
  • Changelogarrow_forward
  • Uptime & reliabilityarrow_forward

Browse by domain

  • Strategy & Researcharrow_forward
  • Developmentarrow_forward
  • QAarrow_forward
  • Governance & Orchestrationarrow_forward
  • All 10 domainsarrow_forward
XOOZLY
© 2026 XOOZLY · 61 agents · 10 domains · 8 SDLC stationsAI use policyarrow_forwardLog inarrow_forward99.9% uptime SLAarrow_forward
  1. XOOZLY
  2. chevron_rightEngineering & research
  3. chevron_rightDispatch
Loading this dispatch…
  1. XOOZLY
  2. chevron_rightEngineering & research
  3. chevron_rightDeterministic guardrails vs. probabilistic LLM evaluators
Engineering

Deterministic guardrails vs. probabilistic LLM evaluators

Hard execution bounds and fuzzy evaluation loops answer different questions. Mixing them produces a system where the safety property is a sample from a distribution.

RTRuntime TeamverifiedOrchestrator & station graph·Jul 28, 2026·11 min read
𝕏in
On this page
  1. 01Two different jobs, two different mechanisms
  2. 02Where the fuzzy layer still belongs
At a glance
61/61Agents governed
0Bypass paths
6Steps per station
Architectural questions?

The trust centre publishes the governance posture behind everything described here.

Open the trust centrearrow_forward
01

Two different jobs, two different mechanisms

An evaluator written as a prompt is useful for judging whether an answer reads well. It is the wrong tool for deciding whether an agent may write to a repository, because its answer is a sample rather than a decision, and samples vary.

So the bounds are not prompts. A station's tool loop stops after a fixed number of steps. An observation is truncated to a fixed length before it re-enters context. A tool call either matches a policy grant or it does not. None of those outcomes depends on how a model felt about the request.

02

Where the fuzzy layer still belongs

Inside the bounds. Planning, drafting and evaluation are exactly the work a model should do, and the loop gives them room — it just does not let them decide where the edge of the sandbox is.

RTWritten by the Runtime TeamOrchestrator & station graph. Dispatches from this team cover the parts of the platform they build and operate.

Related in the product

  • arrow_forwardThe orchestration loop
  • arrow_forwardThe governed control plane
Governed by default

Ready to govern your autonomous fleet?

Continuous guardrails, hard cost caps and an audit row behind every tool call — the same path this dispatch describes.

Start freearrow_forwardRead the trust centre
Suggested reading

More from the engineering blog

Explore all dispatchesarrow_forward
  • GovernanceAug 10, 2026

    Why we built a central MCP gateway instead of trusting agents directly

    Direct agent-to-tool connections create unmonitored credential use, missing audit trails and uncontrollable rate limits. Here is how one centralized proxy enforces policy, writes the audit row and dispatches — in that order — before a request reaches a third-party server.

    verified_userONE PATH PER TOOL CALLPolicy check → audit log → connector dispatchNo domain may bypass it
    8 min readRead article: Why we built a central MCP gateway instead of trusting agents directlyarrow_forward
  • AI OpsAug 03, 2026

    Inside the Rule Optimizer: proposals a human still has to approve

    How detected failure patterns in autonomous runs become proposed rule edits a human approves — and why approval writes a new version instead of editing one in place.

    Proposals auto-applied without review0%
    Input: run historyOutput: proposed version
    6 min readRead article: Inside the Rule Optimizer: proposals a human still has to approvearrow_forward
  • FinOpsJul 19, 2026

    Eliminating runaway inference costs with hard project-level caps

    Inside the per-project spending limit that is read before a run starts rather than reconciled after it finishes, and the auto-pause that follows a breach.

    Worked example — one project's monthAuto-pause threshold 80%
    Spent to date · 78%Hard ceiling · 100%
    5 min readRead article: Eliminating runaway inference costs with hard project-level capsarrow_forward