docs(napkin-math): add methodology doc with assessment-slideshow content#728
Merged
Conversation
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
experiments/napkin_math/docs/methology.mddescribing how the napkin-math Monte Carlo works end-to-end: the 8 pipeline stages, single-run sampling discipline, where bounds come from (with thedatavsassumptionsource label), where thresholds come from (threshold_basisenum), and the worst-gate framing.Includes a slideshow section with two slides intended for insertion before the plan roster in the assessment slideshow — directly addressing reviewer feedback that a skeptical reader will ask "where did the distributions come from?" and "who decided the thresholds?".
The doc is paradigm-agnostic (no LLM/AI references) so it stays accurate as the implementation evolves. Versioning is not hardcoded so the doc can carry forward across future slideshow generations.
Test plan
🤖 Generated with Claude Code