How do I turn a style guide into a rule my agents can use?

Start with one concern, not the whole style guide. “A reply promises no date the support team does not control” is a rule. “Be professional” is a topic. A rule is a Markdown file that says what an output must meet, so pick something you could point at in a draft and say: there.

Write it like a brief for a careful reviewer

Vindex does not require a particular structure. The upload check only looks for content that is not empty, valid Markdown, within the size limit, and a name your catalog does not already use. Inside those limits, write what you would tell a careful colleague: what to look for, what counts as a failure, and what counts as a pass.

# Claims need a source

Copy must not state a superlative or a performance figure without a
cited source.

It fails if it:
- calls the product the fastest, the best, or the leading one
- states a percentage or a time saving and names no source

It passes if every such claim is followed by its source, or is removed.

Save it as a draft

You have two ways in, and they end in the same place.

• Ask your agent.Say “make ‘claims need a source’ a rule.” The agent drafts the Markdown, shows it to you, and after you agree uploads it with create_rule.
• Use Agent Rules in your portal. Upload the .md file or paste the Markdown, and fill in the same fields.

Either way you give the rule a name (unique in your catalog, ignoring case), a description that tells agents what it is for, and tags such as brand or email so you can find it and group it later.

What happens next

The rule is saved as a draft. Your agents cannot run a draft, and a rule never changes under them without your say-so. The next step is to test it before it goes active. Once you have a few rules, you can group them into a rule set.

One concern per rule keeps results readable: when a rule fails, you know which standard was broken and who owns it. The rule format page has the fields, versions, and statuses.