# Concepts

| **Curated Vault**    | A DeFi product built by an independent curator, not a protocol core team, on top of an open and permissionless infrastructure.                                                                  |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Curator**          | An individual or entity that builds, maintains, and handles DeFi vaults. Curators are responsible for allocation design, risk management, and performance upkeep.                               |
| **Structured Vault** | A reward-bearing tokenized position composed of multiple underlying allocations, often blending DeFi-native and institutional assets.                                                           |
| **Shared Security**  | A DeFi primitive that allows multiple protocols to bootstrap security mechanics (often via restaking) from a common pool of stakers. This enables additional yield for securing infrastructure. |
| **Restaking**        | A mechanism that lets staked assets be repurposed and help secure additional protocols or services.                                                                                             |
| **Composability**    | The ability for DeFi building blocks to work together seamlessly. inTokens enable this by bundling multiple yield streams into a standard ERC-4626 format.                                      |
| **Flash-&-Stake**    | A built-in Inception feature that enables instant liquidity exit from inToken positions, bypassing unbonding periods via a shared liquidity pool.                                               |
| **inToken**          | A structured ERC-4626 vault token issued via Inception that can represent multiple reward layers: curated vaults, shared security, and other DeFi strategies.                                   |


---

# Agent Instructions: 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:

```
GET https://docs.inceptionlrt.com/introduction/concepts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.