Dynamic Pages — Reference & Proof Chain

Build all data-driven pages for the anaDocs production site — the reference section (CLI commands, agent templates, skill files, context files) and the proof chain section (explorer with filters/sorting, detail pages for all 89+ proofs). These are the product's signature pages: the proof chain is the "show, don't tell" that no competitor has.

verdict PASSscore 59 / 59findings 12 (0 risk · 4 debt · 8 obs)duration 1h 40mrejection cycles 0shipped May 14, 2026surface website

Pipeline timeline

Intent to proven code in 1h 40m across Think, Plan, and 2 Build→Verify phases.

Think
8m
Plan
25m
Build 1
25m
Verify 1
14m
Build 2
20m
Verify 2
8m

Assertion ledger

59 claims, each independently verified. Showing 8 — show all →

IDSaysMatcher
A001Keyword fallback categorization uses word boundaries so partial matches like 'scannable' don't trigger 'scan'verifiedok
A002Sidebar reference links point to the blueprint route pathsverifiedok
A003Sidebar reference link for agents uses the blueprint routeverifiedok
A004Proof entries include the full assertions array with id, says, and status for each assertionverifiedok
A005Proof entries include the full findings array for downstream componentsverifiedok
A006Proof entries include timing breakdown with think, plan, build, and verify stagesverifiedok
A007Missing timing stages default to zero so components never receive undefinedverifiedok
A008Contract object is normalized to the three common fields regardless of source shapeverifiedok

Findings 12 total

debtwebsite/app/docs/reference/cli/page.tsxclosed
Hardcoded 'Last reviewed · 2026-05-11' in CLI reference page will become stale
obswebsite/scripts/extract-docs-data.tsclosed
Variable shadowing in extractSkillTemplates — inner 'content' (line 584) shadows outer 'content' (line 566), latent confusion risk
obswebsite/app/docs/docs.cssclosed
docs-content-full CSS class added in Phase 1 but only used by Phase 2 explorer — harmless dead code until Phase 2 ships
obswebsite/app/docs/docs.cssclosed
Reference grid responsive collapse only at 660px — no intermediate 2-col→1-col at 880px. Supermock shows collapse at 660px so this matches, but the spec text mentions 1180px and 880px rules
obsclosed
Spec AC2 says transformer URLs match blueprint but contract A002/A003 only check for substring contains — a partial match could satisfy the contract even with a broken URL
+7more findings

Integrity seal

scopesha256:3238bbb4032e0...
contractsha256:00f899ef966a2...
plansha256:4d7933e5b14f3...
spec-1sha256:81aff8aacba07...
spec-2sha256:47e0c85173031...
build-report-1sha256:b41d20076646b...
build-data-1sha256:3a4165dc6f988...
verify-report-1sha256:83154c5bd56a5...
verify-data-1sha256:4a4eb5c0cd25e...
build-report-2sha256:58942d48c4426...
build-data-2sha256:a84886eff6bd5...
verify-report-2sha256:8b2e19fb5af33...
verify-data-2sha256:d8fbc7ea127b4...
audit cmd$ ana proof audit dynamic-pages   → all hashes match