> 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/roadmap/phase-3-compose.md). # Phase 3: Compose Defines the roadmap target for composable protocol capabilities. ### From scale to composability Phase 3 begins in **Week 13+**. It is the roadmap’s composability phase: the prediction-market primitive is intended to connect with options hedging via HoodOptions, cross-chain markets, and structured products. This is a future roadmap direction. None of these additions should be described as live integrations or existing capabilities. ``` Phase 1 — MVP → prove the core product Phase 2 — Scale → expand targets and add programmatic trading Phase 3 — Compose → connect with additional primitives and environments ``` Phase 3 builds on the preceding phases. The roadmap first seeks product validation, then a larger market and participant footprint, then composability. Reaching a numerical target in an earlier phase does not automatically guarantee that later integrations will be successful. ### Quantitative targets | Metric | Phase 2 | Phase 3 | | -------- | --------: | -------: | | Timeline | Week 7–12 | Week 13+ | | Markets | 100 | 500 | | TVL | $1M | $5M | | Traders | 10,000 | 50,000 | The roadmap arithmetic is: ``` 100 → 500 markets = 5× market-count target $1M → $5M TVL = 5× TVL target 10,000 → 50,000 traders = 5× trader target ``` This is a comparison of roadmap targets, not a forecast. It does not establish future market demand, liquidity, revenue, or user behavior. The **500-market** target expands the stated market universe. The **$5M TVL** target expands the stated liquidity and capital target. The **50,000-trader** target expands the stated participation goal. The source does not provide additional targets for volume, retention, revenue, or usage of the new capabilities. {% hint style="info" %} Phase 3 targets begin at Week 13+. They do not report current markets, TVL, traders, or integrations. {% endhint %} ### Options hedging via HoodOptions The roadmap specifies **options hedging via HoodOptions**. At a conceptual level, this describes an intended connection between prediction-market positions and an options-based hedging layer. ``` Prediction-market position + Options hedging via HoodOptions ↓ Phase 3 composability direction ``` The source does not define options contract specifications, strike prices, expiries, Greeks, collateral, margin, settlement mechanics, integration APIs, or HoodOptions contract addresses. This page therefore does not state how the hedging relationship operates or what financial result it produces. The important roadmap point is the planned capability: options hedging via HoodOptions is part of Phase 3. It is not presented as deployed functionality. ### Cross-chain markets Cross-chain markets are another Phase 3 roadmap item. The intent is to move beyond a single-chain market environment. This does not define a bridge, messaging protocol, interoperability layer, supported chains, cross-chain settlement design, or bridge-security model. The whitepaper names the direction, not its implementation. The current architecture is built around Robinhood Chain, chain ID `4663`, as its EVM execution and settlement environment. Cross-chain markets are a future roadmap target and should not be treated as a current change to that architecture. ### Structured products Phase 3 also names **structured products**. This positions structured products as another layer that may be built around the prediction-market primitive. The roadmap does not identify product names, financial structures, payoff definitions, collateral models, or settlement rules. It would be inaccurate to infer covered calls, leveraged notes, vaults, yield products, or other specific structures. The term should remain exactly as the source presents it: structured products are a Phase 3 roadmap direction, not a specified product catalogue. ### Why this phase is called Compose “Compose” describes the intended move from a standalone prediction-market product toward a set of connected capabilities. ``` Prediction markets + Options hedging via HoodOptions + Cross-chain markets + Structured products ↓ Phase 3 composability direction ``` The existing market primitive remains the starting point. Participants trade Yes or No outcome positions, matching occurs through the CLOB path, settlement occurs on-chain, and resolution determines redemption. Phase 3 aims to extend what can connect to that primitive, without changing the roadmap into a claim that those connections already exist. ### Roadmap dependency Phase 3 depends on the earlier roadmap sequence: | Phase | Roadmap purpose | Relationship to Phase 3 | | ---------------- | ------------------------------------------- | ----------------------------------------------------- | | Phase 1: MVP | Prove the core product | Establishes the initial product loop | | Phase 2: Scale | Expand targets and add programmatic trading | Expands the intended market and participant footprint | | Phase 3: Compose | Add named composability directions | Builds on the prior phases | The table describes dependency in the roadmap’s conceptual order. It does not state that attaining 10, 100, or 500 markets guarantees any integration. Options hedging, cross-chain markets, and structured products each remain dependent on future execution. ### What success would demonstrate For Phase 3, success means pursuing the roadmap’s stated Week 13+ direction: ``` 500 markets + $5M TVL + 50,000 traders + options hedging via HoodOptions + cross-chain markets + structured products ``` This would demonstrate the roadmap moving from core prediction markets toward broader composability. It would not establish that every integration is implemented, that liquidity is guaranteed, or that future revenue will be realized. ### Current status and roadmap transition AFTERBELL is still under development. Smart contracts are not yet audited, and an audit is planned before mainnet. Phase 3 is a roadmap target, not production-proven infrastructure. This roadmap is documented in whitepaper **v0.1, September 2026**. Revenue projections are not proven, organic liquidity is not guaranteed, and AFTERBELL does not currently have a token. It is a product, not a token launch. Phase 3 is the final named phase in the current roadmap: ``` Phase 1 — MVP → prove the core product Phase 2 — Scale → expand market, user, and liquidity targets; add programmatic trading Phase 3 — Compose → add options hedging, cross-chain markets, and structured products ``` {% hint style="warning" %} The roadmap contains three phases. It does not define a later phase, additional targets, or implementation details for the Phase 3 integrations. {% endhint %} --- # 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/roadmap/phase-3-compose.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.