Cookie Chat — Product Roadmap

Where the terminal goes next — by theme, not by date

v1.1 · August 2026 · Living document · Companion to the whitepaper

How to read this roadmap

This roadmap is organised by theme, not by date. It describes where Cookie Chat is headed and in what order of priority — not when each item will ship. Like the whitepaper, everything here is forward-looking: direction and intent, not a commitment.

Two anchors orient the rest. The foundation comes first — Cookie Chat's whole argument is that its figures can be trusted, so the work that makes that checkable outranks everything else, including the token. And the mobile app is the flagship expansion: the same engine, in your pocket.

Each item carries two tags:

• Value — expected impact for the user: High · Medium · Low
• Lift — implementation effort: High · Medium · Low

Together they separate quick wins (high value, low lift) from big bets (high value, high lift).

1. Foundation & Trust

Cookie Chat is not a proposal. The terminal is live, it is an official Cookie Chain ecosystem app, and the engine behind it has already been through two generations.

Already shipped

• The terminal, in production — live at cookiechat.net and open to everyone: ask a question, get an answer with live cards, on desktop or a phone. ✅
• Oven 1 — the first deterministic engine: a question matched to a topic and answered from the chain's live data with no model involved. ✅
• Oven 2 — the current default: reads the topic and what is being asked about it, fetches the live data, builds the cards, and selects exactly the verified facts that ask needs. ✅
• Computed facts, written wording — every figure is computed before a model runs, and the reply is then written from those facts and nothing else, so an answer is about the question actually asked rather than about its topic. Stored prose could not do that: it cannot vary with the question. ✅
• Wallet connect, ratings, per-device history — the surrounding product. ✅
• Per-answer source attribution — every answer lists the sources it was built from, collected as it is assembled. "Figures are computed, never generated" is now something a user can check rather than something they have to believe. ✅

Next

• Wider grounding coverage — real production questions are mined from what people actually asked, and the ones the engine could not hand over facts for become ones it can. The measure is how much of an answer rests on computed facts rather than on a model's general knowledge. Value: High · Lift: Low
• Broader drift guard — extend the automated fact audit over more of the written knowledge, so static copy cannot quietly go stale. Value: Medium · Lift: Low

2. Token

$CHAT is the Cookie Chat utility token on Cookie Chain, launched in August 2026 — after the product, not before it. Its supply, allocations and vesting are out of scope here and are covered in full by the tokenomics paper.

Already shipped

• $CHAT, minted on Cookie Chain — one billion, fixed: mint and freeze authority revoked at creation and the metadata immutable, so nothing about the token can be changed later, by anyone. ✅
• Liquidity seeded and permanently locked — the CHAT/COOK pool opened at launch and its LP is locked forever. Nothing that goes in comes back out. ✅
• Team, treasury and future liquidity escrowed on-chain — three Cookie Vault locks, each one public and none of them cancellable, all finishing twelve months after launch. ✅
• The tokenomics paper, published — the full mechanics, with every address in it, live at cookiechat.net/tokenomics. ✅
• The terminal knows its own token — ask it for the contract address, the allocation or an escrow and it answers from the chain and from that paper. ✅

Next

• Access through holding, not billing — Cookie Pro and Cookie Max unlocked by holding $CHAT rather than by a card subscription: higher limits, alerts and premium capability for holders, with the free tier staying genuinely useful underneath it. Value: High · Lift: Medium
• Community waves — the first airdrop ran in August 2026: 100 seats of 100,000 $CHAT to wallets posted under the announcement on X, claimed at cookiechat.net/airdrop. Further waves and seasons after it. Value: High · Lift: Medium
• Tracker listings — visibility and credibility on the major price trackers. Value: Medium · Lift: Low
• Governance for holders — opened once there is a holder base to ask; how a vote is weighted and what it can decide is deliberately not promised in advance. Value: Medium · Lift: High

There is exactly one $CHAT contract, published in the tokenomics paper and returned by the terminal on request. Anything else claiming to be one is not ours.

3. Languages

Cookie Chain's community is not English-only, and as of August 2026 the terminal isn't either.

Already shipped

• Answers in the language you asked in — the question's language is read off the question itself, and the reply comes back in it. The figures are computed first and identically whatever the language, so what changes is the wording, never the number. ✅
• Any language, and forty-two of them by name — an answer comes back in the language it was asked in, whatever that language is. Forty-two are recognised outright; anything else is answered by mirroring the question rather than by naming it, which needs nothing shipped per language. Of the forty-two, eighteen are translated throughout: the prose, the labels beside every figure, the walkthroughs and the links. The other twenty-four keep English card labels — a figure next to "Market cap" reads almost anywhere, and a figure next to a label we cannot vouch for does not. ✅
• A language that sticks — the language belongs to the conversation rather than to each message, so a short follow-up like "cook price" — which carries no language at all — stays in the language you were reading instead of snapping back to English. ✅
• Two ways to change it, neither of them a settings page — write your next question in the language you want, or simply say so ("answer in Spanish"). ✅

This roadmap originally said detection should come with "no setting to find, no flag to pick", and building it produced a flag anyway — because detection can be wrong, and a wrong guess needs somewhere to be corrected. The flag then came back out. Two reasons, both learned by having it on screen. A menu is a claim about where the limit is, and this list is not the limit: an unlisted language is answered by mirroring the question, so a menu of forty-two would have understated what the terminal does. And the correction never needed a control — telling it "answer in Spanish" is faster than finding a flag, works on a phone, and is the one instruction every user already knows how to give a chat terminal.

Next

• Routing cues beyond Polish — a non-English question already reaches the right topic when it names one, because ticker and product names are the same everywhere. Making that reliable rather than lucky means a small table of question words per language. Value: High · Lift: Medium
• The rest of the surface — the walkthroughs, the "where to read more" links under an answer, and the interface around the conversation are still English. Value: Medium · Lift: Medium

4. Cookie MCP & Actions

The qualitative change: from a terminal that answers to one that can act. Cookie MCP is the ecosystem's MCP server, giving agents on-chain access to Cookie Chain — trade, launch, LP, stake, bridge. It runs on its owner's own machine and signs with a key kept there, which is what makes it safe and also what makes it impossible to host behind a public site. So its instruction-building is ported (it is MIT), and the signature moves to the user's browser wallet.

• Swap — "swap 10 COOK for CHAT" ends in a transaction rather than a link. Priced live, built unsigned, signed by the user's own wallet. Shipped as Oven 3, the default engine. ✅
• A stated custody model — how a transaction is prepared, who signs it and what the server can and cannot do, documented in the whitepaper (§8) rather than assumed. ✅
• .cook names — name a .cook name and the terminal reads the registry live: whether it is free, who owns it, what registering it costs, and a button that registers it, signed by your own wallet. Resolution came with it, so a .cook name now works anywhere an address does. ✅
• Staking — "stake 100 COOK" and "unstake 50 bCOOK" both end in a transaction. The pool is read on-chain for the rate and the fees, the estimate is computed from them, and the transaction is simulated before your wallet is ever opened. Instant both ways — the pool pays withdrawals from its reserve, so there is no unbonding queue. ✅
• Bridging, both ways — "bridge 1000 COOK to Solana" dispatches over the Hyperlane warp route and the card then says whether it actually arrived, read from the destination chain rather than assumed. Before anything is signed it checks the two things the source chain cannot see: whether the route can still release that much on the far side, and whether the recipient has an account there to be credited. "unbridge COOK" runs it backwards — signed and dispatched on Solana end to end, which is what made the return leg buildable without mixing two chains in one signature. ✅
• NFTs on Baked Bazaar — name an NFT, by mint or by "Sesamian #4056", and the terminal reads the marketplace and the chain: what it costs, the best standing offer, and whether you hold it. It then offers only what your wallet can actually do — buy, list, cancel, offer, or accept one — each signed by your own wallet. The price you pay is read from the listing at build time, never from the page. ✅ Value: High · Lift: High
• Liquidity stays out of reach — the LP tools depend on three DEX SDKs that will not fit in this app's runtime. For those, Cookie MCP on your own machine remains the answer, and Cookie Chat will point you at it. Value: Medium · Lift: Low
• Simulate before anything moves — every money-moving action previewed, with what it will do stated in plain terms, before it is sent. Registration and staking already work this way: each is simulated against the chain before the wallet is opened, so "someone took that name", "this wallet cannot cover the fee" and "that is more than the pool's reserve can pay out" are answered on the card rather than at a signature prompt. Bridging goes further, because a simulation here cannot see the far side: it reads Solana directly, and refuses the transfers that would succeed on this chain and then hang undelivered. Value: High · Lift: Medium

5. Real-Time & Alerts

Move from request-and-response toward a terminal that watches the chain for you.

• Watchlists — tokens, wallets and collections worth keeping an eye on. Value: High · Lift: Medium
• Price, news and network alerts — threshold-based notifications. Value: High · Lift: High
• Live-updating cards — figures that move while you are looking at them. Value: Medium · Lift: High

6. Platform — API & Widget

Turn the engine into something the rest of the ecosystem can build on. Cookie Chat is an official ecosystem app; the natural next step is to answer other apps' users as well as its own.

• Public API — expose the answer engine so any Cookie Chain app can answer its users' questions with the same computed figures. Value: High · Lift: High
• Embeddable widget — Cookie Chat inside another ecosystem app, in that app's own layout. Value: High · Lift: Medium

7. Accounts & Sync

Optional identity, layered on top of the per-device cookie — never replacing the frictionless default.

• Optional sign-in — built on the existing identity rather than in place of it. Value: Medium · Lift: Medium
• Cross-device history — conversations that follow the user. Value: Medium · Lift: Medium

8. Mobile — flagship

The signature expansion: Cookie Chat in your pocket, on the same engine and the same answer contract.

• Native iOS and Android apps — published on the App Store and Google Play, reusing the engine rather than reimplementing it. Value: High · Lift: High

9. Data Depth

More of the chain, and a time dimension where there currently is none.

• Portfolio value over time — the block exists and renders; it needs a balance-history source behind it, with profit and loss. Value: High · Lift: Medium
• Price history for any token — charts beyond $COOK, across the token universe. Value: Medium · Lift: Medium
• Deeper NFT, marketplace and launchpad data — collections, floors and activity as first-class answers. Value: Medium · Lift: Medium

10. Beyond the Ovens

The engine is not finished at Oven 2, and the work of making it answer more questions — from more computed facts and less general knowledge — continues past everything above.

What comes after the current engine is deliberately not spelled out here. Successive generations of the ovens are planned and in progress, and each will be published once the themes above have landed rather than announced ahead of them.

Value: High · Lift: High

The destination does not change as these themes land: one question, every source — and figures that are computed, not guessed, on every surface Cookie Chat reaches.