Connect tools and documents
Connectors read the decisions your team already made in Slack, GitHub, Google Drive, Notion and Linear, or in their exports; documents (a policy, SOP or runbook) are drafted into rules sentence by sentence. Each suggested rule names an owner: who decided it, or the role the document names. Or add a rule in one sentence on Home, or (optionally) record rules by voice over your own screen.
The owner confirms
Mined and drafted rules apply to nothing until their owner (or an editor) confirms them, and then start in watch: counted, not enforced, until someone turns them to nudge, ask or stop (a drafted policy can skip watch with Approve and enforce now). A rule you add yourself is confirmed by you: live at once if it’s Just for me or you’re an editor; a member’s team rule is proposed and runs in watch until an editor confirms it.
Checked at the moment of action
Every write an agent makes, and every Send or Submit a person makes with Claros for Mac, goes through
POST /v1/check first. The answer: stop, ask the owner, nudge with the fix, or let it through.Answers become precedents
An owner’s answer is an approval record bound to the exact action. The same action is never asked twice, past decisions inform new checks, and consistent answers propose a new rule version (Asks & answers). Every check lands in the signed evidence log.
One check for people and agents
- Routing picks the rule sets an action falls under, across teams.
- Tool mapping turns a tool’s arguments into the rule set’s facts, once per tool.
- Precise rules run as predicates; fuzzy ones go to the judge on the server, not back to the agent.
- A person’s agents act on their behalf: an ask from them goes to that person first when they may decide it.