# Rules overview

div
strong
🔨 In Development
 — This section is still being developed and may change.


Rules let you enforce organization-wide guardrails, tone, and compliance requirements across Freddy assistants and responses.

## What are rules?

- Declarative policies that modify assistant behavior (style, prohibited topics, escalation paths).
- Stored centrally in Freddy Hub and referenced by ID in API requests.
- Evaluated alongside prompts to ensure consistent output quality.


## Rule lifecycle

1. Create the rule in Freddy Hub with a clear name and description.
2. Attach the rule ID when creating responses, assistants, or threads.
3. Monitor rule analytics to confirm adoption and adjust messaging.


## Best practices

- Keep rules focused and composable; avoid mega-rules that are hard to maintain.
- Version rules when making breaking changes so clients can migrate gradually.
- Pair rules with tests in staging environments before promoting to production.


## Related resources

- [Create response](/docs/api-reference/responses/create)
- [Rules API](/docs/api-reference/rules/create)
- [Threads core concepts](/docs/documentation/core-concepts/threads)


title: Rules
badge: draft

# Rules

div
strong
🔨 In Development
 — This section is still being developed and may change.


Rules provide additional behavior modifications and can be attached to API responses to customize their behavior.

## Overview

Rules allow you to define custom logic that modifies how responses are processed and returned. Each rule has a unique ID and can be referenced by responses to apply specific modifications.