> For the complete documentation index, see [llms.txt](https://whitepaper.getpaid.family/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.getpaid.family/risks-and-invalidation/invalidation-scenarios.md).

# Invalidation Scenarios

Sets out the measurable validation thresholds and decision criteria that can trigger a pivot, pause, simplification, migration, or retirement.

These thresholds define the project's explicit validation and continuation criteria. They are decision conditions for the proposed model, not expected outcomes.

| Scenario                       | Validation trigger                                                                        | Intended response                                                                              |
| ------------------------------ | ----------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Pons V2 delay                  | Pons V2 is cancelled or delayed beyond Q1 2027.                                           | Pivot to other launchpads.                                                                     |
| Robinhood Chain volume decline | Robinhood Chain volume drops more than 70% for seven consecutive days.                    | Pause or move the protocol to another chain.                                                   |
| Limited integration            | Fewer than 10 tokens integrate by day 30.                                                 | Consider the product-market-fit thesis unsuccessful and pivot or retire.                       |
| Day-90 integration threshold   | Fewer than 50 token integrations by day 90.                                               | Retire the concept.                                                                            |
| Staking adoption               | Fewer than 100 stakers by day 90.                                                         | Simplify the model toward burn-only utility.                                                   |
| Native launchpad competition   | Pons launches its own fee-routing system with holder rewards and multi-recipient support. | GetPaid may no longer be necessary on Robinhood Chain and may retire or move to another chain. |
| Regulatory action              | Regulatory action specifically targets fee routing.                                       | Pause, enter a compliance mode, or retire.                                                     |
| High-profile fraud             | A major fraud case damages trust in the social payout mechanism.                          | Pause, improve verification, or retire.                                                        |

### How to read these criteria

The integration thresholds test whether the model can establish sufficient adoption after launch. The Robinhood Chain, Pons, competition, regulatory, and fraud criteria test whether core operating assumptions remain viable.

Retirement conditions remain intentional parts of the roadmap. They provide defined points for ending the concept if validation does not support continued development.


---

# 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://whitepaper.getpaid.family/risks-and-invalidation/invalidation-scenarios.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.