Trim customer docs to user-facing proof; relocate production docs to the wiki#16
Conversation
The gh-pages site was publishing ~15 internal asset-production pages (image-gen prompts, storyboards, a visual design system, asset manifests, a playground capture spec, folder rules, asset metadata) in the customer nav. These are developer/operator-oriented, were the source of the private chaos-vault citations, and made the proof PRs brittle (most tests policed internal docs). Customer-facing "Benchmarks & Proof" is now lean: - index.md: tight proof landing (intro + explainability diagram + links). - methodology.md: user-readable (competitor/scenario/size matrices, how each metric is measured, result-field dictionary, no-fabrication policy). - results.md: measured charts + table (unchanged, generated). - ai-rule-safety.md: NEW explainer embedding the 5 carousel slides reframed as "why AI-drafted rules need validation". - All generated SVGs kept; nav trimmed to Overview/Results/Methodology/AI-Rule Safety. Internal production docs were relocated to the private chaos-vault wiki (50-research/neuron-js-proof-assets/) and removed from this repo. Tests: delete playground-capture-contract.test.ts (policed moved files); add customer-docs-surface.test.ts asserting the lean surface (customer pages + SVGs present, internal pages absent, no chaos-vault refs). Verified: lint, test (13 files/68), examples, build, docs:build; dist has no chaos-vault strings and no internal pages built. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
There was a problem hiding this comment.
Code Review
This pull request cleans up the public documentation by removing internal asset-production files, prompts, and storyboards, while introducing a new AI-rule safety page and updating the benchmark index and methodology. It also adds a contract test to ensure only customer-relevant pages and assets are published. The feedback suggests expanding the test's SVG asset list to include all newly referenced diagrams and carousel images, ensuring complete coverage of the customer-facing documentation surface.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Expand customerChartSvgs to every generated SVG referenced by the customer docs (5 benchmark charts, explainability diagram, methodology card, 5 carousel slides) per PR #16 review, instead of a representative subset. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Summary
The gh-pages site was publishing ~15 internal asset-production pages (image-gen prompts, storyboards, a visual design system, asset manifests, a playground capture spec, folder rules, asset metadata) inside the customer-facing "Proof Assets" nav. These are developer/operator-oriented, were the origin of the private chaos-vault citations, and made the earlier proof PRs brittle (most failing tests policed internal docs). This PR makes the customer site serve only user-relevant proof.
Customer-facing "Benchmarks & Proof" (now lean)
docs/benchmarks/index.md— tight proof landing: intro + explainability diagram + links.docs/benchmarks/methodology.md— user-readable: competitor/scenario/input-size matrices, how each metric is measured, a result-field dictionary, and the no-fabrication policy (embeds the methodology card).docs/benchmarks/results.md— measured charts + table (unchanged; generated).docs/benchmarks/ai-rule-safety.md— new explainer embedding the 5 carousel slides, reframed as "why AI-drafted rules need validation".Relocated out of the repo
The internal production docs were moved into the private chaos-vault wiki (
50-research/neuron-js-proof-assets/) and removed here:prompt-kit,visual-proof-system,benchmark-visual-pack, assetprompts/*,storyboard/*,asset-manifest, folderREADMEs, theassets/generated/*.mdmetadata, and the playground capture spec (+ emptydocs/playground/). (That wiki commit is local on the owner's machine; not part of this PR.)Tests
playground-capture-contract.test.ts(it policed the moved playground spec/storyboard/nav entry).customer-docs-surface.test.ts: asserts the customer pages + generated SVGs exist, the internal pages are absent, and customer pages contain nochaos-vaultreferences.benchmark-contract.test.ts/benchmark-results.test.tsunchanged and passing.Validation
yarn lint✅ (50 files) ·yarn test✅ (13 files / 68) ·yarn examples✅ ·yarn build✅ ·yarn docs:build✅disthas nochaos-vaultstrings, and no internal pages built (visual-proof-system,prompt-kit,benchmark-visual-pack,playground/all absent); the 4 customer pages build and the chart/diagram/carousel SVGs ship.Why this also fixes the recurring issues
🤖 Generated with Claude Code