> For the complete documentation index, see [llms.txt](https://docs.takadao.io/takadao-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.takadao.io/takadao-docs/part-b.-takadao-the-daos/06-benefits-payout-protocol/decentralized-benefit-payout-management-dbpm-a-multistage-process/stage-two-irl-verification/stage-two-results.md).

# Stage Two Results

Stage Two verification sources and methods are disclosed to Verifiers on the Verifier Dashboard and results of the verification process are submitted on the same dashboard. As was the case with Stage One, depending on the type of protected event, a simple majority of Verifiers agreeing may be sufficient or a quorum may be imposed in order to reach the necessary evidentiary standard.

**Request Approved**. If evidentiary standard is achieved and the results are positive that the protected event occurred, the payout request is approved and payment is posted for final approval by the Treasury Committee (described in subsequent sections). The amount of the payout is determined by the underwriting algorithm and smart contract and is not decided by Verifiers. 

**Request Denied**. If evidentiary standard is achieved and the results are negative that the protected event occurred, the payout request is denied and the member referred to fraud screening to determine if the request was fraudulent and if the member should be expelled from the DAO. 

**Request Deadlocked**. If no evidentiary standard is achieved and/or the Verifiers are deadlocked on whether the protected event did or did not occur, the request is passed on to Stage Three.

<br>


---

# 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://docs.takadao.io/takadao-docs/part-b.-takadao-the-daos/06-benefits-payout-protocol/decentralized-benefit-payout-management-dbpm-a-multistage-process/stage-two-irl-verification/stage-two-results.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.