Fork quick start

A fork is a vertical: the same core plus a denpa.config.ts and a thin page shell. Culture, sports, fashion, music, film, news — a fork changes configuration, copy, providers, scoring weights and theme. It never rewrites Signal, Market, Identity, Follow, Outcome or Field Record.

Fork Zero — a static-TV skin over the same reads; no backend, MIT.

Standalone (no monorepo) — 60 seconds

git clone https://github.com/bananaemojiii/denpa-fork-zero
cd denpa-fork-zero
cp .env.example .env      # VITE_DENPA_WEB=https://denpa.ai prefilled
npm install
npm run dev               # → http://localhost:5173

Fork Zero is the reference client: a channel is a market. Edit the channel pins and the theme in src/lib/denpa.ts and src/App.tsx.

Inside the monorepo — 10 minutes

pnpm create-app <name> --display "<DISPLAY>" --tagline "<TAGLINE>" --keywords "<a,b,c>"

This copies the working vertical pattern: core packages + denpa.config.ts + a home board + a /broadcast smart-TV clock + /api/health. Then:

1. Open apps/<name>/denpa.config.ts first — the scaffold inherits the template’s market scope until you edit it.
2. pnpm install && pnpm --filter @denpa/<name> build until it compiles clean.
3. Add the service to railway.toml and scripts/railway-build.sh, then railway up --ci --service <name>.

Full walkthrough: Create a vertical.

What a fork owns, and what it does not

Fork owns	Resolves through denpa.ai
brand, theme, copy	identity and sign-in
market scope and providers	stream binding
domain and hosting	receipts and scoring
scoring weights (per vertical)	market context and the program clock

Live forks: cee.news (Kalshi · music/culture), BASETV (Base · Limitless), Fork Zero (IPTV loop), PUND.IT (Kalshi × Robinhood universe).