New: Governed AI for Critical Systems, on the controls regulators will ask for.New: Governed AI for Critical Systems. Read the post

Skip to main content

Governed AI for Critical Systems

Blog

Nina Foster - Business Development Strategist at Thread AI

October 28, 2026

AI is rapidly entering the systems that matter most: government networks, critical infrastructure, and platforms that process personal data. In these environments, an AI agent that exceeds its authority, takes an unapproved action, or leaves no clear record of its reasoning creates security, safety, and privacy risks. That’s why state and federal lawmakers are weighing how to regulate AI.

The rules are coming, even if no one knows their final shape

Across nearly every proposal, regulators keep asking for the same things: clear limits on what AI systems are allowed to do, meaningful human oversight of consequential decisions, protection for sensitive data, and a record that shows what happened and why.

Organizations that wait for the final rulebook will be stuck retrofitting controls onto systems that were never built for them. Knowing what AI is allowed to do, and tracking what it actually did, is good business practice with or without a regulator. It protects data, customers, and operations, and it makes compliance straightforward once regulations materialize.

Limiting who uses AI doesn’t control what AI does

Most organizations start AI governance with access: which teams can use which tools, which models are approved, and which data each user can see. While these controls are necessary, they only govern who uses AI and what it can see. They don’t govern what it can do.

That gap is where the risk lies. Once an agent can call tools, query databases, and trigger actions in other systems, its decisions have real consequences. The question then becomes what stands between an AI’s decision and the action it takes.

If the answer is “nothing,” then the only safeguard is the model’s own judgement. Rules written into a prompt can be ignored, misread, or overridden by a cleverly worded input. That isn’t a foundation that regulators, auditors, or the public will accept for systems that hold PII or keep the lights on.

Control has to live outside the model.

LLM on its own

No orchestration layer

The model decides what to do and how - without boundaries.

No Control

Third-party orchestration

Rules in prompts and wrappers

The model chooses its own actions and can drift. There is only partial control.

Partial control

Lemma + LLM

Governed control layer

The model can only take actions it has been granted. Anything else is blocked or paused for a person.

Governed

What Lemma is

Thread AI’s orchestration platform, Lemma, is the regulation layer above the model: AI proposes, Lemma – and ultimately the customer – decides what’s allowed to happen.

Lemma sits between AI models and the systems they touch, connecting data, models, tools, humans, and actions inside one governed environment. Its model-agnostic nature allows organizations to use the LLMs they’ve already implemented, and when the market changes, replace them without having to rebuild their controls each time.

The principle behind Lemma is governance by default. Every agent runs inside explicit boundaries, with a human in the loop wherever it matters.

The model can reason, but it shouldn’t act on its own authority. Lemma ensures this.

How Lemma governs AI

Lemma gives operators control over how agents run. Actions are explicitly authorized, workflows stay within defined limits, and anything out of the ordinary goes to a human before it is executed. The result: AI that compliance teams can sign off on, and auditors can trace.

Here’s what that looks like in Lemma:

  • Permissioned actions

    Tool calls are authorized by Lemma, not the prompt, so an agent can’t take an action it hasn’t been granted or talk its way past the rules.

  • Bounded by default

    Every workflow is built within set parameters. Agents operate inside a defined scope, and can’t wander outside systems or data they aren’t approved to touch. Customers define the boundaries, and Lemma enforces them.

  • Database guardrails

    Admins set scoped permissions for every database Lemma touches, so it can only read or write what you allow. Systems of record and sensitive data stay protected from accidental or malicious changes.

  • Prompt-injection defenses

    Teams can build checks into workflows that catch instructions hidden in documents, emails, or web content before they can redirect an agent.

  • Human in the loop where it matters

    Any action flagged as high-risk, or any unusual agent behavior, pauses until a person approves it. Operators decide where those checkpoints sit.

  • Drift monitoring and correction

    Agent behavior is tracked over time, so it stays consistent with how the workflow was designed.

  • Full traceability

    Every step is logged with a chain of custody: which model proposed what, which policies were applied, who approved it, and what resulted. That’s the evidence auditors and compliance teams need.

In practice

From the moment a workflow is built, agents only have the access you grant them. An agent cleared to read a record has no ability to change it, and it can’t reach systems it wasn’t granted.

The authority was never there to begin with, and every step is logged for review.

Agent permissions

  • Read a customer recordGranted
  • Change that recordNo authority
  • Reach other systemsNo authority
  • Log every stepRecorded

Already at work in regulated industries

Organizations across insurance, financial services, and supply chain management are already running and building governed AI workflows on Lemma, including the two examples below. In each case, the same pattern repeats: AI does the heavy lifting, deterministic code checks the math, and a human signs off before any consequential decision is made.

What this means for government and critical infrastructure

The foundations of AI trust are consistent across domains, whether protecting financial ledgers, handling sensitive benefits data, or supporting critical grid operations.

For federal agencies, Lemma’s logs and approvals become the evidence behind ATO packages, test-and-evaluation, and inspector general reviews. For states and utilities, Lemma enforces boundaries and human checkpoints for systems where an error can affect public safety or service reliability. For anyone holding PII, it keeps agents to the data and actions they’ve been cleared for.

Governance also makes AI easier to scale. Lemma plugs into the systems a team already uses, so agents can work across departments and data sources rather than staying stuck in one pilot. New use cases run under the same controls, so security doesn’t start from scratch each time. When rules change, teams update policy in one place instead of rebuilding every workflow.

Trust in AI won’t come from better models alone. It will come from being able to show, at every step, what an AI system was allowed to do, what it actually did, and who signed off. That’s what Lemma is built to provide.

If you’re working on deploying AI safely in the public sector, energy, or another regulated industry, we’d like to hear from you. Get in touch with Thread AI.