> For the complete documentation index, see [llms.txt](https://docs.spiral.farm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spiral.farm/dao/governance-process/spiral-integration-request-sir.md).

# Spiral Integration Request (SIR)

**Summary:** Short description of the proposal (1-2 sentences max) 

**Rationale:** Detailed explanation of the proposal and milestones for its execution. 

**Project Presentation:** (After summary) 

* Protocol name 
* LP/vault/etc. requested
* Smart contract address 
* Audit(s) links - Chain requested 
* Relation with the project 
* Twitter/Discord/Telegram links 

**Metrics:** (After project presentation) 

Risk assessment: 

* Smart Contract risk: maturity, transactions, audit, bug bounty, etc. 
* Counterparty risk: holders, smart contract permission, multisig, etc. 
* Market Risk: market cap, yield, etc.

**Means:** Resources needed for this proposal

* Human resources: Special skills required (dev or others)
* Treasury ressources: Proposal cost (in COIL/SPR and in $), % of the treasury required, etc.

**Technical implementation:** Highlight the technical implementations of this proposal if any. 

**Voting options:** Mention the options that will be included on the snapshot vote, including an “Abstain” one.


---

# 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.spiral.farm/dao/governance-process/spiral-integration-request-sir.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.