> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rheon.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Proposals - overview

> A menu of design patterns from leading products, for the team to choose from.

<Info>
  **This tab is a proposal, not the live spec.** The **Documentation** tab always reflects
  what exists today. This **Proposals** tab collects patterns from how leading payments and
  crypto products (Stripe, Transak, Li.Fi, Plaid, Svix, Circle) handle each area - as a
  starting point for the team to review and decide what Rheon adopts.
</Info>

## Why this tab exists

When we build the API, webhooks, and sandbox, we will want them to match the bar set by
the best in the space. Rather than invent the design, we studied how the leaders do it
and collected concrete, copyable patterns here. Each page below is "how it could work",
with the source it came from.

## What's inside

<CardGroup cols={2}>
  <Card title="Integration & embedding" icon="layer-group" href="/proposals/integration">
    Embed options, secure widget URL, declarative chain/token filtering, lifecycle events.
  </Card>

  <Card title="Transaction statuses" icon="list-check" href="/proposals/transaction-statuses">
    The deposit state machine and tracking channels.
  </Card>

  <Card title="Webhooks" icon="bell" href="/proposals/webhooks">
    Event catalog, signature verification, retries, idempotency, testing.
  </Card>

  <Card title="Sandbox" icon="flask" href="/proposals/sandbox">
    Test credentials, simulating outcomes, simulating time.
  </Card>

  <Card title="API reference" icon="code" href="/proposals/api-reference">
    OpenAPI as source of truth, endpoint groups, page anatomy.
  </Card>
</CardGroup>

## How to read it

Each page is structured the same way: the pattern, why it works, and which product we
took it from. Treat it as a menu - the team picks what fits Rheon, not a commitment.