Current evidence, integration limits and the gates before real money.
Status date: 11 September 2026 · V7.2. This section distinguishes the Framer website and product previews, working local artifacts and financial services that still need implementation.
| Area | Status | What the evidence means |
|---|
| Website and market journeys | Framer website and browser previews | Open the website; creation, trading, positions and contribution screens use preview funds, not real money |
| Website content editor | Framer | Marketing pages are editable in the Framer project. Interactive previews and documentation use shared code components |
| Prediction economics | Reference-tested | 71 market, reserve/accounting and lifecycle checks; no deployed prediction contracts |
| Early points | Specified and reference-tested | 31 durable-points reference checks; production identity, database and review service still required |
| Basic token-pool DualPool | Implemented and locally tested | Real upstream PoolManager/hook integration with test assets and a funded vault fixture |
| FAFO ERC20 token | Implemented and locally tested | Fixed initial supply parameter, treasury mint and allowance-controlled holder burns; no production deployment or announced economic supply/allocation |
| YES/NO market contracts | Specified; implementation next | The separate token-pool hook is not a completed prediction-market engine |
| Live reserves and monetary pilot | Gated | Requires real capital, operational approval, tested contracts and independent review |
| Documentation | Included in this Framer website | Read the complete guide, organized into six searchable chapters. The underlying Mintlify source is retained; separate Mintlify hosting is optional and not connected |
The Preview uses simulated balances stored in the current browser. It has no production account service, real-money trading or durable points ledger. Local points and contribution drafts are not accepted awards. No production token address or allocation has been announced.
The current Solidity suite passes 41 tests: 7 token, 18 PoolManager integration, 4 accounting and 12 preparation tests. The round-trip fuzz test passes 256 cases. Formatting checks pass. These are separate from the 71 economic/lifecycle and 31 points reference checks.
Local vault interest is funded by a test fixture. It demonstrates accounting behavior, not a live lending rate. Compile success does not establish a target-chain deployment or source/bytecode equality with someone else's deployed contract.
Edit the delivered website
Open the FAFO Framer project in your owner account. Select the page and layer you want to edit. Update copy, links, colors and imagery, then inspect desktop, tablet and mobile layouts. Framer saves your project edits; use its preview to review them and Publish to release the site.
Shared code components supply the interactive previews and documentation. Editing a marketing layer does not change market calculations, points or balances. See documentation publishing for documentation changes.
Before live prediction trading
The release needs verified chain and token identities, actual funding routes, a funded reserve manifest, independent contract/economic review, reliable identity and group access, a paid resolution/review operation and complete test-money journeys. Contract payouts must remain supported when the website is unavailable.
Before the token or token pool launches
Publish the actual token contract and its supply, allocations, vesting and controlling roles. Verify the USDG token, eligible vault and v4 contracts on the chosen chain. Rehearse the treasury bootstrap and withdrawals on a fork. Fund every promised distribution and liquidity position.
The current target is Robinhood Chain with USDG. Targeting that ecosystem does not imply brokerage distribution, endorsement, an existing lender route or an announced partnership.
How to read the roadmap
- Specified: written behavior and acceptance criteria.
- Implemented: source exists.
- Verified locally: scoped tests passed; read their assumptions.
- Released: the actual accessible service or deployment exists.
- Measured: real usage or funded execution has been observed.
Delivery roadmap · Developer onboarding