The roadmap page was rebuilt on 2026-09-18 from an inventory of the code and the production
tables. This document records what the previous page said, what was found to be true, what was
overstated or stale, and why the new page is arranged as it is. The page itself is /roadmap; its
data is apps/web/src/app/(site)/roadmap/roadmap.ts; the architecture plan it points to is
ARCHITECTURE_SHIPPING_SIGNAL.md.
1. What the previous roadmap said
Four phases — Shipped, Now (Foundation and trust), Next (Research intelligence and discovery), Later (Direction) — with five statuses: Live, Beta, Building, Researching, Planned. Twenty-nine items. No dependency between phases was stated; nothing said what had to hold before the next thing could be built; the direction ended with "a HEY agent on X, Telegram and other channels" and "$HEY utility that follows the product", both without a definition of the signal an agent would carry or an audit of which token utility was actually in use.
2. What was found to be true
Every Shipped item on the old page is running in production and is carried forward as LIVE, with two exceptions noted below. Since that page was written, the following also shipped and were not on it:
- Repository corroboration as three states (declared, context, corroborated), with a borrowed repository's commits never setting a status.
- Verified Builder as a catalogue-written label requiring a corroborated meaningful ship.
- Contract deployers with creation transactions, follow-up deployments, shared-deployer detection and proxy checks.
- The signal engine with twenty kinds, before/after figures and confidence; the Builder Radar with kept inputs; weekly-report finals that regenerate when a rule changes.
- Scout tasks opened from HEY's own gaps and retired when the gap clears.
- The by-contract lookup endpoint, the MCP server with twelve tools, the badge, llms.txt.
- Research bounties with tranches and the holders-first window; bonds; paid research requests; linked wallets, tiers and entitlements; the treasury ledger.
- Contributor counts and day-by-day commits on every weekly commit summary.
3. What was overstated, stale or misleading
| Old claim | Finding | New wording |
|---|---|---|
| "Launchpad factory logs (fifteen launchpads)… 1.35 million screened" | Counts on a roadmap go stale the week they are written; the launchpad number had already drifted from the adapter list. | No counts on the page; live figures are on /pulse and /status. |
| "fifteen kinds of measured change" | Twenty kinds exist; fifteen have fired; five never have, three for lack of history depth. | Kinds are not counted on the page; the never-fired kinds are recorded in the architecture plan. |
| "Public API, MCP server, feeds, badges — Live" | The MCP server runs only from a clone of the repository over stdio; there is no hosted endpoint and no package. | MCP is SHIPPED with that note; a hosted endpoint is PLANNED in Q3 2027. |
| "Watchlist and digests — Beta" | Built, deployed, tested; two watchlists and no confirmed email address in production. "Beta" implied a stage of readiness; the truth is a stage of use. | SHIPPED: "almost nobody uses it, and it does not carry signals yet". |
| "Research economy — Live" | Bounties, bonds, requests, wallets and the ledger are live. The API tiers have one unused key; the monthly vote has never opened a round; early access guards zero research notes; placements are switched off. | Split into ten audited items on the $HEY section, each with its own status. |
| "Integrity audits and status — Live" | Running, but the card-fact reconciler examines a fixed prefix of the projects table and has logged "truncated" daily; it covers about five percent of the published catalogue. | Not a roadmap item; recorded as a repair in the findings report of the same date. |
| "7,957 evidence-less pages returned to indexed" | A repair figure from one week, presented as roadmap progress. | Removed; repairs are logged in the findings reports, not the roadmap. |
| "Alerts on meaningful change — Planned" and "A HEY agent on X, Telegram — Planned" | Neither said what the signal is, what makes it meaningful, or what must be true first. An agent without a defined signal is a chat client. | Q1 defines the signal; Q2 delivers it; each states what it builds on. |
| "$HEY utility that follows the product — Researching" | Five token utilities are live and three are shipped and idle. "Researching" under-reported what exists and hid what is unused. | Audited list: LIVE / SHIPPED / RESEARCH per utility, with what each has actually done. |
| Statuses Live / Beta / Building / Researching / Planned | "Beta" and "Building" carried no rule for when they apply. | LIVE / SHIPPED / IN PROGRESS / PLANNED / RESEARCH, each defined on the page and in the data file. |
4. The new structure, and why
Four quarters, one ladder: Research → Discovery → Verification → Corroboration → Meaningful activity → Signals → Alerts → Agents → Execution. Each quarter states what it builds on and what it unlocks.
- Q4 2026 — Build the research layer. Mostly LIVE. The quarter's real work is the four IN PROGRESS items (contributor time series, post-launch coverage, the reviewer surface, scheduled fork re-checks) and three PLANNED ones (project flags, repository↔contract linkage, fingerprinting). These are the inputs a shipping signal reads, so they come first.
- Q1 2027 — Turn research into signals. The engine, score history and the weekly report are LIVE; the Meaningful Shipping Signal is designed and not built; alerts are alert-only and PLANNED. Nothing here depends on price.
- Q2 2027 — The Shipping Signal Agent. A delivery surface for a signal that already exists. Alert-only is the default and ships first; paper trading second; execution is RESEARCH and waits for a quarter of alert-only results.
- Q3 2027 — The agent and execution network. Hosted MCP, structured feeds, agent watchlists, machine-readable provenance. Reputation and cross-chain are RESEARCH because each is a definition before it is work.
Why quarters rather than Shipped/Now/Next/Later: the old phases were a sort by confidence; the quarters are a sort by dependency. A reader of the old page could not tell that alerts needed a signal, that a signal needed corroboration, or that corroboration was the part still in progress.
5. What is deliberately not on the page
No percentages, no ETAs, no "coming soon", no counts. No wallet analytics, smart-money labels, price predictions, trending lists or purchasable ranking — these are stated as out, not as later. Token utilities that do not fit the product (a token that buys a status, a score, a rank, or a signal's existence) are not proposed.
6. Files changed for this rebuild
apps/web/src/app/(site)/roadmap/roadmap.ts— new; the roadmap as typed data.apps/web/src/app/(site)/roadmap/page.tsx— rewritten to render the data file.apps/web/e2e/roadmap.spec.ts— rewritten: four quarters, ladder order, status set, no invented dates, OG image, 375px.apps/web/src/app/og/surface/[key]/route.tsx— aroadmapshare card.apps/web/src/lib/docs.ts,apps/web/e2e/docs.spec.ts— this document and the architecture plan served under/docs.docs/ARCHITECTURE_SHIPPING_SIGNAL.md,docs/ROADMAP_AUDIT_2026_09_18.md— new.
No migrations, no new tables, no new API contracts were needed for the roadmap itself. The data models and contracts the signal and the agent will need are specified in the architecture plan and are not built.