> For the complete documentation index, see [llms.txt](https://being-and-time.gitbook.io/boom-clap-melody-field-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://being-and-time.gitbook.io/boom-clap-melody-field-guide/start-here/what-is-melody.md).

# what is melody

Melody is Boom•Clap's contextual circulation layer. It helps worthwhile campaigns, products, events, creators, services, and causes appear in publisher environments where they can make sense.

Instead of treating every placement as an auction for the broadest possible reach, Melody looks for compatibility among:

* the campaign and its subject;
* the publisher's environment and current context;
* audience interests and location when applicable;
* timing, delivery history, and the balance of the Spin.

The result is a lightweight **intermission**: a brief, skippable discovery moment between a visitor's click and destination. Melody can also support native media from services such as YouTube, SoundCloud, and Instagram when the campaign link is compatible.

## Resonance and Melody

Boom•Clap has two complementary operational layers:

* **Resonance** identifies opportunities near attention that is already active.
* **Melody** circulates compatible opportunities through participating publishers and Spins.

Resonance is about placement and opportunity discovery. Melody is about continued circulation and discovery.

## What Melody is not

Melody is not a general-purpose ad drop box. Campaigns and publishers are reviewed for contextual fit, creative quality, and ecosystem standards. Participation may be limited when a campaign would degrade the surrounding content environment or conflict with Boom•Clap community culture.

Melody also does not guarantee a fixed publisher, volume, click count, or outcome. A campaign's actual circulation depends on available inventory, context, compatibility, geography, budget, and Spin health.

Next: [How Melody Works](broken://pages/7f17da597a357c89e4b4a291abdd24635a763633)


---

# 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://being-and-time.gitbook.io/boom-clap-melody-field-guide/start-here/what-is-melody.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.