Your people stay in charge of every AI action.
One governance layer runs under every Stackmint operating system. A named person approves the exact version, every step is recorded, and any agent can be stopped at once.
What an approval records
market_review · run 0412 · approved- Who
- Account director, namedA named person, never an anonymous reviewer.
- What
- Draft v3, exact textThe client receives the version that was approved.
- Which versions
- agent v12 · playbook v4 · model pinnedEverything that produced the work, pinned.
- When
- 2026-10-08 · 09:22Written to an immutable audit log.
- Context
- Checkpoint contextWhat the approver saw when they decided.
- Seal
- Cryptographic hashThe approved content is hashed and sealed.
Six controls under every operating system.
Every Stackmint operating system inherits the same controls. Your people stay in charge, every run stays within its budget, and you can show exactly how the work was done.
- Approval gates
Approval of the exact version
Nothing reaches a client until a named person approves the exact version. Place checkpoints anywhere in a workflow, or require approval before sensitive actions, external sends and writes to your systems.
- Every step
Immutable audit logs
Every request, decision, change and result is recorded, with the approver’s decision and the context they saw. Answer any client or regulator with evidence.
- Run · workflow · org
Kill switches
Stop any agent or workflow at once. Act on a single run, a whole workflow or your entire organization.
- Credentials server-side
Execution gateway
Specialists can only use the tools and data their workflow gives them. Every action runs through a controlled gateway, with credentials kept server-side.
- Pinned versions
Versioned agents
Each agent, playbook and model version is pinned. No silent changes to how work gets done, and every step records which version did the work.
- Per client, per matter
Client data isolation
Every client and matter has its own context. Documents are treated as content, never as instructions.
How data isolation works
The same controls run under AgencyOS, LegalOS and every Custom OS.
Start with one team, on real work.
- 01
Working session
We map your services and playbooks to an operating system, using your real work.
- 02
Pilot on live work
Start with one team. Your people review every output while the agents learn your standards.
- 03
Roll out across the firm
Add teams, clients and your own agents as the results come in.