--- title: "Trust, and Verified." canonical_url: https://auteurintelligence.com/trust/ description: "How Auteur keeps agents aligned: deterministic guardrails, allowlists, spending limits, sandboxed workspaces, human gates and cross-company AI oversight." --- # Trust, and Verified. Trust here is not a promise about how the machinery works inside, those mechanisms are in patent review. It is a set of outcomes you can check. This page lists them. --- **Looking for the operational side?** [Security for the agent era](https://auteurintelligence.com/security/) details the screening, sweeps, gates, and cross-model checks underneath these commitments. ## The rogue-agent problem, answered with engineering The industry's own published safety evaluations describe models that deceived their evaluators, slipped their test environments, or went far beyond their assigned task. Enterprises are right to take that seriously: an agent you cannot read is a liability, however capable it is. We not only let you monitor and verify; we record behavior over time and evaluate those results as a whole, so across long-form jobs you always know where things went right, where they went wrong, and what the thought processes were behind the work at each step. Our answer is not another model promising to behave. It is old-fashioned, deterministic software engineering wrapped around every seat: allowlists instead of trust, spending limits enforced before dispatch, private, sandboxed workspaces, and human gates on anything that spends money, changes canon, or publishes. On top of that sits oversight by AI from more than one company: work from one model family is verified by a different one, so no model grades its own homework. The economics follow the honesty. When something goes wrong you know at the first failed check, not after the damage: in building this very site, sixteen failed attempts were caught by verification and receipted, and none of them reached the page you are reading. --- ## Proposals are not approvals Approved production truth is human-reviewed and versioned, and approved canon stays separate from automated suggestions: a suggestion cannot quietly become canon. Complex goals move through a durable, reviewable workflow, so there is always a line between a draft and a decision. --- ## Approved work stays versioned Once something is approved, it does not silently change underneath you. Reviewed production truth is held as a versioned graph of scenes, entities, review states, source evidence, and handoffs. Visual production keeps immutable render versions and their dependencies, so a project can move from source material through scenes, shots, generation, and assembly without a later step rewriting an earlier approval. Department packets are revision-pinned and carry checksums. --- ## Receipts and readback, independent of self-report Auteur verifies what changed and what passed instead of accepting an agent's claim that the work is complete. It derives Git ancestry, commits, changed paths, diff validity, tests, and mismatches independently of what the executor reports, the receipt is built from the work, not from the claim about the work. "Done" means the evidence agrees. --- ## Isolation before integration Agent work stays isolated from your primary checkout and is verified before it is integrated. Non-protected branches and private, sandboxed workspaces restrict where an agent can write and what it can run, and changed paths are observed independently, so autonomous work is contained and auditable rather than trusted on faith. --- ## Failure is stopped, and work recovers Failed branches and repeated dead ends are stopped before they consume the rest of the budget. Hard iteration, token, time, and spending limits, no-write watchdogs, and deterministic failure signatures bound the damage, and bounded remediation and recovery bring work back rather than abandoning it. The system is built to stop wasted effort, not to run unattended. --- ## Authority is checked at call time Connecting an AI interface does not grant wildcard authority over files, spending, publication, or application changes. Authority is recomputed on every call, so a tool visible in a stale client list still cannot act outside what is currently authorized. Covered services refuse autonomous work when their running revision is stale. --- ## Status is labeled candidly The site shows two independent things about every product: how finished the software is, and how you can get it today. We keep them separate on purpose, because a product can be genuinely capable and deliberately limited at the same time. Our editorial rule is simple: we publish only what we can back with evidence you can check, and we weaken a sentence rather than state something we cannot show.