Coding agents, design tools and agent platforms read rules from markdown files: AGENTS.md, DESIGN.md, Figma Guidelines, skills. Export puts a rule set’s rules into those files, each in the owner’s words with who said it, when it applies and what the agent should do. The file is an advisory copy: Claros still checks every action against the live map, so a rule changed in Claros applies at once, and the export catches up the next time you run it.

Formats

Each rule lists:
  • the rule, and the owner’s words (or the written policy’s) it came from
  • when it applies: the kinds of action and record, the map’s apps, the step
  • the condition, in plain words, for a precise rule; “a judgement call” for one Claros judges
  • the response: stop, ask (with who to ask) or nudge (go ahead, mention it)
Rules their owner hasn’t confirmed yet are marked (not yet confirmed). The only ids in the file are the map’s id and version, next to the export date.

Example

Export

The CLI uses the key npx getclaros saved (or --key / CLAROS_KEY). Exit codes: 0 printed, 1 no such map, 2 not signed in or bad usage, 3 Claros unreachable or key rejected. GET /v1/maps/{workflow_id}/export?format=agents|design|skill takes an agent or capture key, returns text/markdown with a Content-Disposition file name, 404 for a map not in your workspace and 422 for another format. On the map page, Export offers the same three files as downloads.