> For the complete documentation index, see [llms.txt](https://bubblegum-reality.gitbook.io/bubblegum-reality-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bubblegum-reality.gitbook.io/bubblegum-reality-docs/operations/roadmap.md).

# Roadmap

## Phase 1 — shipped

One complete path, end to end: land → connect wallet on Robinhood Chain → pick a stock token → see reference value vs executable liquidity → get a real 0x quote → approve the exact amount → sign and track a swap.

* CRT/bubblegum design system, cinematic landing, skippable boot sequence
* Chain 4663 config, wagmi/viem wallet connection, wrong-network recovery
* Server functions: assets, prices, corporate actions, chain status, 0x price/quote
* Decimal-safe pricing with multiplier adjustment
* Deterministic Reality Score with every input displayed
* Non-custodial swap execution with exact-amount approvals
* Eligibility gate, client-persisted and server-enforced
* `/markets` over live data; `/about` disclosures
* 73 Vitest cases; clean typecheck, lint, and production build

## Phase 2 — shipped so far

| Area                     | State                                                                                                          |
| ------------------------ | -------------------------------------------------------------------------------------------------------------- |
| Cloud backend            | Full schema, RLS and grants on every public table; no Edge Functions — typed RPC only                          |
| Account server functions | Profile, wallet linking, watchlists, alert rules, trade history — all behind `requireSupabaseAuth`             |
| Reality Check AI         | Live in the terminal, verdicts cached in `ai_insights` with a 10-minute TTL                                    |
| Markets                  | Full registry with search, batched live quotes, condition chips, session badge                                 |
| Portfolio                | Real batched balance reads, valuation, HHI and concentration bands                                             |
| Security pass            | Nonce and AI-cache tables locked to server-only; role helper out of the public API schema; append-only history |

Every `CREATE TABLE` in `public` shipped with explicit `GRANT`s in the same migration — RLS alone does not grant Data API access. Roles live in a **separate** `user_roles` table read through a `SECURITY DEFINER` `has_role()` function: never on a profile row, never checked from client storage.

## Still open

| Area             | Scope                                                                       |
| ---------------- | --------------------------------------------------------------------------- |
| Auth UI          | `/auth` page (email + Google) — every account-scoped table is waiting on it |
| Compliance flow  | Risk-disclosure and tokenized-debt acknowledgement written to `profiles`    |
| Alerts           | Rule builder UI plus an evaluator writing `alert_events`                    |
| Trade history    | Writing signed swaps into `transaction_records` and a history view          |
| Watchlists UI    | Server functions exist; no surface yet                                      |
| Portfolio extras | CSV export                                                                  |
| Legal pages      | Terms and Privacy                                                           |

## Explicit non-goals

* Custody of user funds or keys
* Investment advice, recommendations, or price targets
* Mock or fallback data when an upstream fails
* Any claim of affiliation with Robinhood


---

# 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://bubblegum-reality.gitbook.io/bubblegum-reality-docs/operations/roadmap.md?ask=<question>&goal=<endgoal>
```

`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.