Documentation Index
Fetch the complete documentation index at: https://docs.backed.app/llms.txt
Use this file to discover all available pages before exploring further.
Risk Boundaries
The largest practical risks in Backed are usually not abstract. They are interpretive, organizational, and economic. This page exists to make those risks legible before they are misunderstood as simple interface concerns. Most of them do not originate from deep protocol mechanics alone. They come from incorrect interpretation, rushed launch behavior, overstated autonomy, or weak accountability.Primary risks
| Risk | Description |
|---|---|
| Premature launch assumptions | A project exists or is visible, but has not been approved as a live raise |
| Autonomy overstatement | The agent is described as more autonomous than it actually is |
| Launcher opacity | The responsible founder or company behind the agent is unclear |
| Economics misread | Investors misunderstand soft cap, hard cap, refunds, or the 30-day lockup |
| Interface-state mismatch | A surface shows stale or incomplete information relative to contract state |
| Category risk | AAOs are still an emerging organizational form and should be read with appropriate caution |
How to reduce these risks
- separate creation, review, approval, and settlement in your own reading of the raise,
- ask whether the launch description is precise about what is already autonomous and what is not,
- verify that a real launcher or launching entity stands behind the agent,
- read the economic terms before treating a raise as investable,
- trust contract-defined state over screenshots, cached interfaces, or second-hand summaries.