Full-parity checklist

The scaffold gives a read-only display fork: board + clock + health. To fork the full denpa.ai surface, FEATURES.md maps every feature to one of four paths:

Path	Meaning
IMPORT	a workspace package (@denpa/ui, @denpa/sdk)
CORS	read from denpa.ai in the browser
PROXY	a server-side call to the hub
COPY	vendored, with an exact copy manifest

Build order

1. Market page + signal blocks — /m/[id] + a signal panel. Write path: dk_ key → your own proxy route (app/api/signal/route.ts in your fork) → denpa.ai/api/predictions → denpa receipt.
2. Pop-up windows — vendor FloatingWindow.tsx (react-only).
3. Transmissions — vendor the panel; point its maps at your vertical.
4. Wire / signals / leaderboard views — server-side reads of /api/wire, /api/signals/feed, /api/network/operators (the cee pattern).
5. Tape — CORS-read /api/network/tapes; copy a TapeDeck.
6. HUD / OBS overlay — only if your fork hosts its own operators.

Never fork

Scoring, resolution, receipts, identity, AURA, observations — those resolve through denpa.ai. Sign-in lives in core identity: every fork’s claim flow links to denpa.ai/unlock (X, Sign in with Solana, email), never to a fork-local login.

Known gotchas

• A hand-written layout.tsx (custom webfonts) silently drops ResolutionOverlay — re-mount it from @denpa/ui/fork.
• The hosted clock programs Polymarket categories only; scope a Kalshi fork or it shows TV-static.
• Key rotating market panels by marketId.
• Every player: hls.js first, native HLS second.