> 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/oracle-architecture.md). # Oracle Architecture Describes the data sources and safeguards used during market resolution. If the oracle is wrong, the market can resolve incorrectly. That affects settlement, redemption, and user trust. AFTERBELL therefore proposes a two-source resolution model: **Chainlink Stock Token Feed** as the primary source and the **Robinhood REST API** as an independent cross-check. ``` Resolution condition → Chainlink price + Robinhood API price → comparison ├─ difference ≤5% → normal resolution └─ difference >5% → market pause → manual resolution ``` ### Primary, secondary, and exception paths Chainlink provides the primary on-chain price input. The Robinhood REST API is an off-chain reference, not an oracle network. The system compares the two values before proceeding through the normal resolution path. If the difference exceeds 5%, the circuit breaker pauses the market. An administrator can then resolve using off-chain evidence. The system does not guess between materially conflicting values. ### Trust boundary The architecture combines on-chain and off-chain components. Chainlink integration, smart-contract resolution logic, and settlement are on-chain. The API cross-check, keeper infrastructure, and manual evidence are off-chain. AFTERBELL is therefore not completely trustless. The source describes its approach as **“trust, but verify, twice.”** It is proposed architecture for a project still in development; smart contracts are not yet audited. --- # 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/oracle-architecture.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.