> For the complete documentation index, see [llms.txt](https://docs.firelight.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.firelight.finance/for-stakers/deployments.md).
# Deployments
#### Activation
Deployments activate without waiting for a period boundary. Once the deployment transaction confirms:
1. The vault records the position in a single atomic transaction.
2. The deployment moves through compliance screening.
3. Once screening clears and the deployment becomes active, it is added to the protocol's staked balance and rewards begin streaming.
A deployment made late in a period earns rewards for the remainder of that period once active. There is no waiting for the next boundary to start earning. Slashing exposure begins at the same moment: once a deployment is active, its capital is part of the backing and takes any pro-rata slash from a validated claim, even in its first period.
The diagram shows a stake entering mid-period (Day 45 of Cover Period 1). It begins earning protocol emissions immediately once active, and assumes slashing exposure at the same moment. There is no waiting for the next period boundary.
{% hint style="info" %}
Periods are currently **30 days** long. Period length updated to 30 days when the Feature-Complete Protocol launched on October 6, 2026.
{% endhint %}
#### What counts toward coverage capacity
Although deployments activate immediately for base rate emissions, they count toward coverage capacity at the next period boundary, when the matching engine recomputes capacity for the following period. In practice a mid-period deployments starts earning base rate emissions right away, while its contribution to new coverage allocation shows up in the next period's capacity calculation. This is a consequence of deterministic period settlement: each period settles based on its starting state, so mid-period flows take effect in the next period.
#### Steps
The deployment flow follows the same pattern Firelight launched with in Phase 1 against the Launch Vault: approve the vault to spend stXRP, call deployment, and receive the vault position. Stakers who used the original flow will find no interface changes for the basic deployments.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.firelight.finance/for-stakers/deployments.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
