# Naming Convention Guidelines

## Core Fiddler Asset Naming Requirements

The following naming convention applies specifically to these core Fiddler platform assets: Projects, Models, Baselines, Webhooks, and Teams. Other elements in the platform may have different naming rules.

### Required Format

* Names must start with a lowercase letter (a-z)
* After the first character, names may contain:
  * Lowercase letters (a-z)
  * Numbers (0-9)
  * Underscores (\_)
  * Hyphens (-) — Team names only
* Names cannot contain uppercase letters, spaces, hyphens (except Team names), or special characters
* Each asset type has specific length requirements:

#### Team Name Format

Team names follow all of the above constraints, but additionally support hyphens (-).

| Fiddler Asset | Minimum Name Length | Maximum Name Length |
| ------------- | ------------------- | ------------------- |
| Baseline      | 3                   | 256                 |
| Model         | 2                   | 30                  |
| Project       | 2                   | 32                  |
| Webhook       | 2                   | 127                 |
| Team          | 2                   | 256                 |

### Examples

#### Valid Names

* `model_1`
* `test_project_2023`
* `prod_env`
* `my_baseline_123`

#### Valid Names (Team names support hyphens)

* `team-name`
* `valid-team-1`
* `dev_team-2024` (underscores and hyphens)

#### Invalid Names

* `Model1` (starts with uppercase)
* `1_model` (starts with a number)
* `my feature` (contains space)
* `project#1` (contains special character)
* `m` (too short for any asset type)
* `_test` (starts with underscore)
* `extremely_long_name_that_exceeds_the_character_limit_for_models_and_projects` (exceeds length limits for Models, Projects, and Webhooks)
* `test-project` (contains hyphen — invalid for Projects, Models, Baselines, and Webhooks; valid for Teams)

*Note: Hyphens are valid for Team names.*

### Best Practices

While following the required format, we recommend these additional best practices:

* Use descriptive names that indicate the purpose or content
* Use underscores to separate words for better readability (or hyphens for Team names)
* Keep names reasonably short while maintaining clarity
* Be consistent with naming patterns across similar items
* Consider using prefixes to group related assets (e.g., `prod_`, `dev_`, `test_`)

### Note on Other Platform Elements

This naming convention applies specifically to core Fiddler assets (Projects, Models, Baselines, Webhooks, and Teams). Other elements in the Fiddler platform may have different naming requirements or restrictions. Consult the specific documentation for those elements if needed.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fiddler.ai/developers/client-library-reference/naming-convention-guidelines.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.