> 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/publishers/spins.md).
# Spins
A Spin is a publisher-owned contextual collection of Melody campaign opportunities. It is closer to a living mixtape than a fixed playlist.
### Create a Spin
1. Open your CanNoli **Account** page.
2. Under **Spins**, select **Make Spin**.
3. Enter a short alias.
4. Add an optional memo.
5. Write the preliminary context.
6. Select **Initialize Spin**.
The preliminary context must describe the mood, perspective, subject, community, or moment the Spin is intended to support. Be specific enough for Melody to understand what belongs.
Examples:
* independent music discovery and late-night listening;
* practical urban gardening for apartment residents;
* local arts, events, and community organizations;
* thoughtful technology and creative-work tools.
The account interface shows your active Spin limit. Limits are account-specific.
### Spin lifecycle
A Spin may appear as:
* **Initializing** while the first composition is prepared;
* **Pending Review** when publisher review is required;
* **Active** when available for delivery;
* **Refreshing** while context or slots are recomputed;
* **Paused** when not delivering;
* **Archived** after it has been destroyed.
Spin visualization
### Composition
The Spin profile displays its current campaign composition. Melody can add, pause, replace, or remove slots as campaigns and context change.
Composition is influenced by:
* the Spin's preliminary context;
* public context pages added by the publisher;
* campaign compatibility and health;
* geography and campaign targeting;
* prior delivery and balance;
* publisher vetoes and donated inventory.
### Context learning
On the managed Spin profile, add public pages where the Spin's Nolis are shared or embedded. Melody uses these pages as evolving placement-context signals.
Only submit pages you control or are authorized to use. Pages should be public and representative of the real environment.
### Vetoes
Publishers can veto a limited number of campaign slots when there is a strong mismatch.
Current controls allow:
* up to three active vetoes per Spin;
* one veto action per 24-hour cooldown period;
* veto expiration after 30 days.
Vetoes are intentionally limited so publishers can reject serious mismatches without turning a balanced Spin into a manually curated ad list.
### Donations
Publishers may dedicate a percentage of windows to an available cause. Donated windows do not generate publisher or CanNoli payment. If a Noli carries donated slots, it will be marked as so.
A donated Slot
### Use the Spin
After the Spin is active, select **Use in a Noli**. Create or update a Melody Noli and choose the Spin. Melody Nolis use a short intermission window and can then be deployed directly or through a CDN kit.
---
# 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/publishers/spins.md?ask=&goal=
```
`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.