/how · fuzzywigg.ai
How this hub is built
www.fuzzywigg.ai is a public builder hub: Next.js 16 on Vercel, content driven by JSON under content/, deployed on push to main. The source lives in a private repo — strangers get 404 if you invent a GitHub door. This page documents the live pipeline, not a product launch.
Pipeline verified 2026-08-20
Pipeline
Edit content/*.json, open a PR or push to main; Vercel Git integration deploys. Optional repository_dispatch event_type content-update runs validate-content (see .github/workflows/content-update.yml). The only hub API route is GET /api/interests (live arXiv + Hugging Face papers for the /how ticker, cached ~1h). There is still no content-write API. Aesop publish is not connected.
Allowed captures
Two honest public hub crops only — home hero with LinkedIn visible (two-column constellation) and /now headline + pulse items. No family UI, no login, no stolen X chrome.
Host and cache
- Host: Next.js 16 App Router (next ^16.2.2) on Vercel → https://www.fuzzywigg.ai/. Static HTML for content pages; one read-only interests API for /how.
- Public builder, private repo. Do not link fuzzywigg/fuzzywigg-ai — strangers get 404.
- Updates: edit content/*.json, PR / push to main. Vercel deploys on push. Optional repository_dispatch content-update validates content; there is no hub API route for content writes.
- GET /api/interests aggregates public arXiv + Hugging Face papers for Andrew's topics; empty/error if a source fails — never invent papers. /how/rss.xml is generated from content/how/*.json verified dates.
- Praetor CLI against www (verified 2026-08-16): 15 pass / 0 warn / 0 fail. HSTS is Vercel max-age=63072000 — not a constitution preload flag.
- DNS (DoH verified): GoDaddy nameservers ns15.domaincontrol.com / ns16.domaincontrol.com. Apex A 76.76.21.21. www CNAME cname.vercel-dns.com. Apex https://fuzzywigg.ai/ still HTTP 307 to https://www.fuzzywigg.ai/ (registrar/platform). fuzzywigg.com is a live 301 archived pointer here.
- Featured HOW pages: /how/merom-house, /how/pikoclaw, /how/qfzz, /how/radio. Featured first-screen doors (sites.json): Merom House, PikoClaw methodology, Pappas Farm, QFZZ docs. Radio HOW exists; its door is not featured.
- Aesop publish is not connected — no invented journal posts.
What is live vs static
| Source | Live or static | Card |
|---|---|---|
| Next.js 16 App Router on Vercel | SSG pages + one read API | Hub HTML/CSS/JS; /api/interests live |
| content/*.json | Source of truth (edit → PR/push) | Home, /now, /sites, /about, /how/* , /how/rss.xml |
| GET /api/interests | Live fetch (cached ~1h) | /how interests ticker only |
| Apex fuzzywigg.ai → www | HTTP 307 (registrar/platform) | Not a vercel.json-only toggle |
| Praetor | CLI audit of the live URL | Not a hosted worker on this hub |
| Aesop publish | Not connected | No journal feed invented here |
Public links
- Public hub (www)
Primary door — Next 16 on Vercel
- /how methodology index
Nine feature stories + interests ticker
- /how/rss.xml
RSS of the nine existing HOW pages
- /now pulse
Dated constellation facts
- Doors directory
Public site list from content/sites.json
- About
Hub about copy
- HOW · Merom House
Featured HOW — KPI dashboard honesty
- HOW · PikoClaw
Featured HOW — methodology MkDocs
- HOW · QFZZ
Featured HOW — radio-demo docs
- HOW · Radio / Backlink
HOW exists; Radio door is not featured on first screen
- LinkedIn (professional outbound)
Only professional social contact — not X
Not copied onto this hub page
- No stolen X handle as a contact.
- No Geryon.
- No Skylight family app.
- No Workwife product story.
- No fake metrics / visitor counts.
- No Ads.
- No empty blog / invented Aesop journal posts.
- No private GitHub fuzzywigg/fuzzywigg-ai href — stranger 404; say “private repo” in prose only.
- No invented hub /docs route.
- No worker un-stub / Praetor hosted worker URL.
- No money / SSO UI.