> For the complete documentation index, see [llms.txt](https://docs-lunar.earthly.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-lunar.earthly.dev/configuration/lunar-config/initiatives.md).

# initiatives

* `lunar-config.yml -> initiatives`
* Type: `array`
* Form:

  ```yaml
  initiatives:
    - name: <initiative-name>
      description: <initiative-description>
      owner: <initiative-owner>
      on: [<tag>, <tag>, ...]
    - name: <initiative-name>
      description: <initiative-description>
      owner: <initiative-owner>
      on: [<tag>, <tag>, ...]
    ...
  ```

Initiatives are used to group policies together around a specific goal or compliance requirement. They provide a way to organize policies and make them easier to manage and monitor.

Example initiatives definition:

{% code title="lunar-config.yml" %}

```yaml
initiatives:
  - name: security
    description: Security policies for all components
    owner: security-team@example.com
    on: [security, backend, frontend]
  - name: performance
    description: Performance optimization policies
    owner: platform-team@example.com
    on: [backend, api]
  - name: documentation
    description: Documentation compliance policies
    owner: docs-team@example.com
    on: [all]
```

{% endcode %}

## Initiative

* `lunar-config.yml -> initiatives.<initiative-index>`
* Type: `object`
* Form:

  ```yaml
  name: <initiative-name>
  description: <initiative-description>
  owner: <initiative-owner>
  on: [<tag>, <tag>, ...]
  ```

An initiative represents a collection of policies organized around a specific goal or purpose. Initiatives make it easier to manage and track related policies.

### `name`

* `lunar-config.yml -> initiatives.<initiative-index>.name`
* Type: `string`
* Required

The name field is used to specify the unique identifier for the initiative. The name `default` is reserved and cannot be used; a built-in "default" initiative is always created automatically for policies that don't specify an initiative.

### `description`

* `lunar-config.yml -> initiatives.<initiative-index>.description`
* Type: `string`
* Optional

The description field is used to provide a human-readable description of the initiative.

### `owner`

* `lunar-config.yml -> initiatives.<initiative-index>.owner`
* Type: `string`
* Optional

The owner field is used to specify the person or team responsible for the initiative. This is typically an email address.

### `on`

* `lunar-config.yml -> initiatives.<initiative-index>.on`
* Type: `array of strings`
* Optional

The `on` field specifies the tags that the initiative applies to. These tags are used to associate policies with the initiative.

For detailed documentation on tag matching syntax, including domain/component targeting, expressions, and cross-references to other collectors or policies, see [Tag Matching with `on`](/configuration/lunar-config/on.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs-lunar.earthly.dev/configuration/lunar-config/initiatives.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.