deploy-prototype

<!-- autoresearch: variation B — sharper output via prototype quality bar + self-check + signal-anchored record --> > **${var}** — What to build and deploy. > - Empty → auto-select from recent signals (articles, logs, memory topics). > - Plain text (e.g. `market heatmap`) → interpret as a build brief. > - Typed form `type:slug description` (e.g. `tool:market-heatmap volume heatmap of top-20 tokens`, `viz:tx-graph`, `api:summarize`, `landing:startup-idea`) → use `type` to bias shape and `slug` as the deployment name. Today is ${today}. Your task is to ship a small, self-contained prototype that someone could actually use in the browser today. ## Steps 1. **Read context.** Read `memory/MEMORY.md` and the most recent entries in `memory/logs/` for active topics. If running as part of a chain, scan injected upstream outputs for a concrete artifact worth making interactive. 2. **Pick what to build (if `${var}` is empty or vague).** Scan these sources, in order, for prototype-worthy signals: - `articles/` — last 7 entries by mtime: any claim, finding, or dataset that would be more useful as an interactive page? - `memory/topics/*.md` — running narratives; pick one with a live data source (prices, feeds, markets) - `memory/logs/${today}.md` and the two prior days — skill outputs flagged as interesting - `memory/MEMORY.md` → "Next Priorities" and "Recent Articles" Score each candidate 1-5 on: - **Leverage** — does an interactive version beat the static w...