> 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/manual-resolution.md). # Manual Resolution Covers the administrative process when automated resolution cannot proceed. AFTERBELL does not guess when its oracle sources materially disagree. Manual resolution is the defined exception path when the Chainlink primary source and Robinhood API cross-check differ by more than 5%. ``` Oracle disagreement >5% → market paused → administrative review → off-chain evidence → manual resolution → final outcome → redemption ``` ### Why the manual path exists The automated path can only proceed when its two sources agree within the stated threshold. A difference above 5% means the system has conflicting inputs. Rather than select one value automatically, it pauses the market. An administrator can then resolve the market using off-chain evidence. This is a deliberate safety tradeoff. It aims to avoid silently resolving a binary market against materially conflicting data. ### An explicit trust boundary Manual resolution means not every market outcome is fully autonomous. The system relies on off-chain evidence and administrative judgment in this exception path. Users should understand that before participating. The current source does not define the administrator’s identity, multisig structure, number of signers, voting process, evidence hierarchy, deadline, appeal rights, or governance model. Those details are not assumed by this documentation. The manual path does not make the protocol fully trustless, and it does not claim to eliminate oracle risk. It makes the human intervention point visible: when automated verification cannot safely resolve the market, the market pauses and an administrator resolves it. --- # 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/manual-resolution.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.