Upload
In the web app: Work maps → Paste a policy: paste the text, or a Markdown, text, PDF or Word file up to 1 MB. Or the API (raw file as the body):workflow_id (wf_ + lowercase letters, digits, _) and app (repeatable). The answer has the draft map, its workflow_id and a report (rules, precise, judged, notes on what was dropped).
What Claros checks before you see it
- Every rule quotes the document. The quote must be the document’s own sentence, attributed to the file and section (“In the written policy (change-policy.md § 2)”), never to a person. A rule that can’t be grounded is dropped.
- Predicates only when the document says so. A precise rule is kept only if every number and value in it is written in that section. Otherwise the rule stays fuzzy and goes to the judge.
- Owners are the roles the document names.
Approve
A draft isn’t enforced: routing and the tool mapper skip it. Read it on Rules, fix what’s wrong (duplicates, a permission read as a rule, a wrong field), then approve:{"enforce": true}:
Documents and voice together
A draft for a workflow that already has rules recorded by voice is merged with them, the document counting as one more source. Where the written policy and what people do differ, Claros asks. See When owners disagree.Expect to edit drafts. In our runs on four policies, editors made 11 edits across 41 drafted rules before approving. See Evaluation.