Product · SimThink Abyss · Governance
Set the rules of agent work for your field, before it runs
Before, the rules of the work lived in documents, in people’s heads or inside program code, and staff who know the business could not read or change them. With SimThink Abyss, the people who know the business set the rules down as data that AI agents must follow, and a rule change needs no code release. Every approval stays with a person.
Abyss is a design tool for fields with special rules, such as manufacturing or safety inspection. It sets the names, the order of work and the checks that agents follow in that field. A requirement that cannot be checked is refused before anything runs.
What we guarantee
What SimThink Abyss guarantees for your organization
Declare your work in plain terms
You state what each thing is called, how things relate, the order of work, what must stop the work, and who exchanges what with whom and in which format.
Rules are data
A rule change means a change to data, with no new program code and no code release.
What you draw is what runs
The design is saved exactly as drawn. What is saved is exactly what runs and what is checked.
Unchecked demands are refused first
A requirement that cannot be checked is refused before anything runs. The refusal names the checkpoint that stopped it. A combination that is not allowed cannot be chosen, and the check says why.
AI cannot approve
Only a person can approve, and each approval is kept in a fixed form. If an AI claims to approve something, that claim is not saved.
Evidence before decisions
A claim with no evidence behind it is not used to make a decision.
No lock-in
The design is a file. If you edit it in a text editor, it goes through the same check. When you work with another company, the same rules carry over. Where its rules differ, you add one set for that company.
How it works
Setting up the frame of your work
Name the terms
Agree on what each thing in your work is called and how things relate. In manufacturing, this can mean products, recipes and defect types.
You get: Term definitions
Draw the flow
Set the order of work, the information each step needs, and where a person must approve.
You get: Input forms and approval rules
Set the checks
Decide what AI output is checked against, and what must stop the work. In safety inspection, this can mean what an inspection sheet needs before it becomes the report required by law.
You get: Check criteria for AI output
Hand it over
Write the rules down so that another person can take over the work later.
You get: A handover document
The SimThink family
Where it sits in the SimThink family
SimThink Abyss sets the rules for the work that runs in SimThink OS, ES and Surf. You do not need Abyss to start with SimThink Build. You need it when the work passes to the next department, when the result must meet a law, a contract or a public submission, when people must watch the judgments an AI makes, or when several agents must use the same words for the same things. A simple test tells you: when someone else takes over this work later, can one rules document explain it?
Operating system
Learn moreSimThink OS
The agentic operating system for a company. It runs planning, work, approval and review on one set of rules.
Execution system
Learn moreSimThink ES
Manages AI agent work the way a plant manages work orders. Only work that a person accepts counts as output.
Work system
Learn moreSimThink Surf
The agent window next to your work screen. People and the agent work side by side.
Governance
This page
SimThink Abyss
A design tool that sets up the frame of agent work for a specific field. Rules are kept as data, so a rule change needs no code release.
Sets the rules for work in OS, ES and Surf
Start by setting up the frame of one piece of work.
We build the frame of your work with you. You keep the term definitions, the input forms, the approval rules, the check criteria for AI output and a handover document.
Details are shared during adoption talks.
Talk to us about adoption