> For the complete documentation index, see [llms.txt](https://whitepaper.after-bell.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.after-bell.uk/oracle-and-resolution/resolution-logic.md). # Resolution Logic Defines how verified market outcomes determine token settlement. Resolution turns an open prediction into a final binary outcome. It begins when the market reaches its stated condition, such as a Friday stock close, an earnings release, or a monthly crypto price condition. ``` Market open → condition reached → obtain prices → compare → resolve or pause → winning outcome → redemption ``` ### Normal and exception paths Chainlink provides the primary price source. The Robinhood REST API provides the cross-check. The system compares the two values. When disagreement is within 5%, the market can continue through the normal resolution path. The verified result determines whether Yes or No wins. The winning outcome becomes redeemable; the losing outcome becomes worthless. When disagreement exceeds 5%, the market pauses. An administrator may resolve using off-chain evidence. The source does not define a separate dispute window, appeal process, fallback source, or formal state machine. ### Resolution is not only a price read For “Will NVDA close above $150 on Friday?”, the resolution condition is Friday 4 PM EST. The process must then establish the relevant price through the proposed verification architecture. For earnings markets, the relevant event is the report’s release. The final result matters because it determines ERC-1155 outcome-token redemption. The process therefore depends on oracle integrity and includes an explicit administrative trust boundary. Smart contracts are not yet audited, and the system should not be treated as production-proven. --- # 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.after-bell.uk/oracle-and-resolution/resolution-logic.md?ask=&goal= ``` `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.