Repository navigation
docs(statistics): approve the v1 method catalogue - #55
Merged
Merged
Conversation
The repository owner approved the bounded method catalogue on 2026-09-22, without amendment, satisfying the requirement in #1 that the catalogue and its supported/unsupported conditions be approved before any method is implemented. Issue #1's remaining criteria are gated on this document, so the approval is recorded here rather than in a comment that can be missed. The record is deliberately explicit about scope. Approval covers the v1 scope (exact descriptive summaries; parametric fits with constraint and convergence reporting; nonparametric permutation/bootstrap), the per-method publication list as the acceptance gate, and the reading that a descriptive summary is the correct default when the information needed for valid inference is missing. It does NOT cover exact statistical tests (tracked in #3), any method outside the list, or the symbolic work (#2), which stays blocked. Approval is of scope and gate, not of method behaviour: each method still publishes its conditions before implementation, and nothing is implemented merely by appearing in the list. The file was method-catalogue-v1-draft.md; the text is the text that was approved and the rename records the decision rather than altering it. The draft name is kept in the record so the approved text can be traced, and numeric-contracts.md's one inbound reference is updated to match. Refs #1
|
Warning Review limit reachedNext included review available in 9 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
14 tasks
hyperpolymath
enabled auto-merge (squash)
September 22, 2026 12:02
hyperpolymath
disabled auto-merge
September 22, 2026 12:02
hyperpolymath
enabled auto-merge (squash)
September 22, 2026 12:02
|
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
1 participant
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.
Refs #1 — the approval the issue requires before any method is implemented.
Issue #1 says the bounded catalogue and its supported/unsupported conditions must be
approved before methods exist. This PR is that decision, recorded in the document itself
rather than in a comment that can be missed.
What changed
docs/statistics/method-catalogue-v1-draft.md→docs/statistics/method-catalogue-v1.md,status APPROVED on 2026-09-22, approved without amendment by the repository
owner (Jonathan D.A. Jewell,
@hyperpolymath).summaries; parametric fits with explicit constraint and convergence reporting;
nonparametric permutation/bootstrap with stated exchangeability and seeds), the
per-method publication list as the acceptance gate, and the reading that a
descriptive summary is the correct default when the information needed for valid
inference is missing.
in feat(analysis): Exact statistics layer — Fisher's exact, exact NB, permutation tests #3), any method not listed, and the symbolic work (BLOCKED: assess a symbolic mathematics engine only after deep statistical validation #2), which stays blocked.
its supported/unsupported conditions before implementation, and nothing is implemented
merely by appearing in the list.
altering it, and the draft name is kept in the record so the approved wording can be
traced.
numeric-contracts.md's single inbound reference is updated.What this unblocks
Item 1 — descriptive summaries at exact precision (counts and proportions as exact
integers/rationals, no inference claimed) — is first, and depends only on
numeric_policy.jl, which is already onmain. Its implementation PR will carry thatmethod's published conditions, known-answer and independent-reference evidence, and its
negative controls, as the catalogue requires.
Paperwork-only: no code changes,
check-formatandcheck-spdxclean.