Rules live in rule sets: one per kind of work (refunds, deploys, release notes), plus the workspace’s Team rules for rules typed on Home or confirmed from connectors. The API and the check log call a rule set a workflow or map (workflow_id, wf_…). Each rule carries its words (the owner’s, or the document’s sentence), its owner, what happens when it’s broken (stop, ask, nudge or watch), its scope and its source. A rule set recorded by voice also keeps the steps and decisions around each rule, each tied to its redacted screen moment.

​
Coverage

​
Export

A rule set exports as a SKILL.md an agent can load (GET /api/export/{workflow_id}.skill.md), or into AGENTS.md and similar files (Export), and agents read it over the MCP server. The same set is what the guard enforces.

​
Where rule sets come from

  • Documents: drafted from a policy, SOP or runbook, approved by an editor.
  • Connectors: candidate rules mined from your tools, each confirmed by its owner.
  • By voice: an editor records rules over their own screen.
  • Several sources: merged into one set, disagreements asked.
A rule set belongs to one workspace.