Governance

An agent that acts only on what your team approved.

Most agents are models wired to tools: they do what they infer, and say “done” when the call returns. conxtagents acts only on approved playbooks, waits for approval on anything consequential until you let that action run on its own, checks the real system after every change, and records every decision.

Two ways to run an agent

The difference is a line, and who draws it.

Ungoverned agents

A model plugged into your tools.

  • Acts on whatever it infers, with no approved source of truth
  • Takes consequential actions without a person in the loop
  • Learns silently, so bad patterns become behaviour
  • Says “done” without checking the change took
  • Hard to say what it did, or why
conxtagents

An agent inside a governed brain.

  • Acts only on playbooks a person approved
  • Consequential actions wait for approval, until you let one run on its own
  • Even what it learns is reviewed before it governs
  • Reads the system back after every change, and only then says done
  • Every decision and side effect is attributed and on the record
The governed learning loop

Memory governs only after a person approves it.

The agent proposes what it learns from real work. Nothing crosses into the memory the agent acts on until you approve it, and rejected memory never governs anything.

governed brain · example agentlearning
Approved by a person
Proposed by the agent · outside
waits
Give new hires the Business Essentials licence
drafted from request #1852
rejected
Make every new hire a local admin
declined · never governs
Approved · inside · governs actions
governs
Verify identity before any account change
approved by a person
governs
Match every invoice to a purchase order
approved by a person
Three lanes of action

The agent knows what it may do, and what it must never do alone.

On its own

Reads, and earned actions

Reads you marked as read-only run by themselves, and what they return is shown to the approver. An action can join them once the owner allows it and its record stays clean.

e.g. look up a user, review a client’s bills
Waits for a person

Consequential

Anything that creates or blocks an account, changes a licence or touches a client’s books waits for your yes, with a signed, one-time approval.

e.g. onboard a new hire: account and licence
Never alone

Handed to a person

Security-sensitive or novel cases go to a human. The agent stops instead of guessing.

e.g. a request to make someone Global Administrator
How every action stays safe

Guarantees, enforced by design.

Approved playbooks only

A playbook waiting for review cannot drive an action. Only playbooks a person approved do.

Scoped execution tokens

Each approval issues a one-time token bound to a single user, team, playbook and action.

Checked, then recorded

After every change the agent reads the system back. The receipt says what was approved, who or what approved it, and what the system showed afterwards.

Rejected means never

Memory you decline is not just unused: it can never govern an action.

Agents that do the work. And prove it.