Docs Infrastructure — Fumadocs MDX Pipeline
Stand up the Fumadocs MDX pipeline inside the existing Next.js 16 website so that one test page renders at `/docs`. This is the foundation for the entire anaDocs production site — 37 routes, 78+ proof pages, 6 guides, 7 concept pages. Nothing renders until this infrastructure works. The old quickstart-style `/docs` page is replaced.
verdict PASSscore 18 / 18findings 6 (0 risk · 2 debt · 4 obs)duration 48mrejection cycles 0shipped May 12, 2026surface website
Pipeline timeline
Intent to proven code in 48m across Think, Plan, Build, and Verify.
Think3m
Plan6m
Build14m
Verify6m
Assertion ledger
18 claims, each independently verified. Showing 8 — show all →
| ID | Says | Matcher | |
|---|---|---|---|
| A001 | The website builds successfully with fumadocs dependencies installed | verified | ok |
| A002 | The docs catch-all route exists in the build output | verified | ok |
| A003 | The test MDX page has required title frontmatter | verified | ok |
| A004 | The test MDX page has required description frontmatter | verified | ok |
| A005 | The docs page resolves MDX content from the content directory | verified | ok |
| A006 | Missing docs pages return a 404 instead of crashing | verified | ok |
| A007 | The Next.js config preserves the view transition experimental flag | verified | ok |
| A008 | The Next.js config preserves security headers | verified | ok |
Findings 6 total
debtwebsite/app/docs/[[...slug]]/page.tsx→ closed
Prose classes used without @tailwindcss/typography installed
obswebsite/lib/source.ts→ closed
Page tree injections for Reference and Proof Chain omitted from source loader
debtwebsite/components/docs/→ closed
Empty components/docs directory left after deleting 4 component files
obswebsite/eslint.config.mjs→ closed
eslint.config.mjs modified to ignore .source — not in spec file_changes
obswebsite/source.config.ts→ closed
Frontmatter schema allows empty strings — z.string() without .min(1)
+1more findings
Integrity seal
scopesha256:a4a983caccd74...
contractsha256:ff1cd775dbc74...
plansha256:b3e68a0862268...
specsha256:894a6081fa393...
build-reportsha256:8484b0557f853...
build-datasha256:c3545977225ff...
verify-reportsha256:9827d129ac0e3...
verify-datasha256:4c3558657797e...
audit cmd$ ana proof audit docs-infrastructure → all hashes match